semvec/pypi-packages huggingface dataset:
mxLogPy 0.1.9
High Performance and mutilThread & async Log Library by Cpp

# 使用案例
~~~python
import sys
import mxLogPy as mxLog
import time


def manual_test():
    # 获取 LogManager 单例实例
    logger = mxLog.LogManager.getInstance()
    # 设置文件追加器
    logger.setFileAppender("logAuto.txt")
    # 设置控制台追加器
    logger.setConsoleAppender()

    logger.setOutBufferSize(10)
    logger.setBufferSize(10)
    
    # 设置日志名称，注意，一定要在设置控制台追加器之后，否则程序将会出错
    logger.setLoggerName('mxLogger')
    # 测试消息
    logger.log("Info", mxLog.LogLevel.Info)
    logger.log("Debug", mxLog.LogLevel.Debug)
    logger.log("Info", mxLog.LogLevel.Info)
    logger.log("Warning", mxLog.LogLevel.Warning)
    logger.log("Error", mxLog.LogLevel.Error)
    logger.log("Fatal", mxLog.LogLevel.Fatal)
    logger.clearConsoleBuffer()
    time.sleep(1)


def benchMark():
    # 获取 LogManager 单例实例
    logger = mxLog.LogManager.getInstance()

    # 设置文件追加器
    logger.setFileAppender("benchmark.txt")
    # 设置控制台追加器
    logger.setConsoleAppender()

    # 设置输出缓冲区大小
    logger.setOutBufferSize(1000)

    # 记录开始时间
    start = time.time()

    # 进行十万次 info 输入
    for i in range(20000):
        logger.log("Info :" + str(i), mxLog.LogLevel.Info)
        logger.log("Debug :" + str(i), mxLog.LogLevel.Debug)
        logger.log("Warning :" + str(i), mxLog.LogLevel.Warning)
        logger.log("Error :" + str(i), mxLog.LogLevel.Error)
        logger.log("Fatal :" + str(i), mxLog.LogLevel.Fatal)
        if i == 20000:
            logger.clearConsoleBuffer()

    # 记录结束时间
    end = time.time()

    # 计算耗时
    elapsed_time = end - start

    # 记录耗时到日志
    logger.log(f"Elapsed time: {elapsed_time:.6f} seconds", mxLog.LogLevel.Info)


if __name__ == "__main__":
    manual_test()
    # benchMark()

~~~
Adamlibrary 1.3
A C library for Python with additional C functions
Requires Python: >=3.6

# Project Overview

This project is written in C and aims to bring functionalities that are not available in Python as an extension. Some functions may not work correctly, but we will make corrections after releasing the stable version.

## Support

If you want to support us on GitHub, visit: [GitHub Repository](https://github.com/Goychay23/int)

## Example Usage

Testing model: [test-utils](https://azencompileropensourcefoundation.com/src/Adamlibrary/test.py)

## Development Environment

**Dependencies**:
- `gcc`
- `ctypes`
- `util-linux`

## Sources
For additional resources, visit: [Sources Link](https://azencompileropensourcefoundation.com/sources/link/treelink/model/adam/library/gcc-maker-test)

#Documentary 
Adamlibrary documents tr: [Adamlibrary-document-tr](https://azencompileropensourcefoundation.com/src/biradaminkutuphanesi.pdf)
Adamlibrary documents en: [Adamlibrary-document-en](https://azencompileropensourcefoundation.com/src/adamlibrary/amanslibrary.pdf)

## Donations

You can contact our site for technical support: [Azencompiler Open Source Foundation](https://azencompileropensourcefoundation.com/donate)

## Copyright

Copyright: Azencompiler Open Source Foundation
automatic-contract-creation 2.0
This is package designed for auto-generation of contracts and tests in the soda syntax
Requires Python: >=3.7

# Automatic Contract Creation

**Automatic Contract Creation** is a Python library that is designed to auto-generate various types of contracts based on the soda syntax using LLM.

### Features

In the current version, connection to DB such as Clickhouse and Trino is configured.
By connecting to the database, you can generate and/or upload a statistical report, as well as generate a soda contract.

## Get Started

### Requirements
trino==0.327.0  
clickhouse-connect==0.6.22  
pandas==2.2.3  
polars==0.20.21  
openai==1.37.0  
regex==2024.9.11  
load-dotenv==0.1.0  
python=3.11.5  
pyarrow==17.0.0  
The rule based approach uses soda version 3.3.5 (SODAGenerateContract).  
The LLM approach uses soda versions 3.1.5(LlamaGeneratorSODAContract).


### Install and run

You can install the library using pip:
```
pip install automatic-contract-creation
```
Import the necessary objects. To use all the functionality, you can contact SODAGenerator
```
from automatic_contract_creation import SODAGenerator
from automatic_contract_creation import LlamaGenerateSuite
from automatic_contract_creation import LlamaGeneratorSODAContract
```

##### To rule based approach:
Create a connection object by passing the connector type and credits in dictionary format.
Use the methods to auto-generate a contract or generate a statistical report.

##### To LLM approach:
Create a file in the virtual environment ".env" with its credits
example

```
connection_name='clickhouse or trino'
host='hostname'
port=port
user='username'
password='password'
llama_api_url='your api url for llm'



token='token_omd'
```

use your method
```
print(LlamaGenerateSuite('db_name.table_name').get_suite())# prints the tests (the path is specified by the click example)
LlamaGenerateSuite('catalog.schema.table').generate_suite()# upload a yaml file with tests (the path is specified following the example of trino)
LlamaGenerateSuite('catalog.schema.table').save_profiling()# will save the profiling
print(LlamaGeneratorSODAContract('catalog.schema.table').generate_schema_contract())# will print the contract
LlamaGeneratorSODAContract('catalog.schema.table').get_soda_contracts()# will download the yaml file with the contract
```
CVE-2024-21413 0.1.0
A script to send emails via Gmail SMTP with customizable HTML templates.

# CVE-2024-21413 - Critical Remote Code Execution Vulnerability in Microsoft Outlook
## Setup 
- You can change smtp and password and copy the command into Terminal to use CVE-2024-21413-PoC.py
> Linux & Ubuntu & ParrotOS & ALL Base on Linux
```bash
export SENDER_EMAIL=ah3112651@gmail.com
export SENDER_PASSWORD=pnsbkvkxwfgwjueu
```
> Windows
```bash
$env:SENDER_EMAIL = "ah3112651@gmail.com"
$env:SENDER_PASSWORD = "pnsbkvkxwfgwjueu"
```
## Overview

CVE-2024-21413 is a critical remote code execution (RCE) vulnerability affecting Microsoft Outlook. This zero-day vulnerability, also known as the "MonikerLink" bug, allows attackers to execute arbitrary code on a victim's machine without any user interaction. The vulnerability is triggered by maliciously crafted email messages that exploit specific types of hyperlinks within Outlook, leading to severe consequences such as system compromise, data exfiltration, or the installation of malware.

## Affected Versions

The vulnerability affects various versions of Microsoft Outlook, including but not limited to:

- Microsoft Office 2016
- Microsoft Office 2019
- Microsoft Office 2021
- Microsoft 365 Apps

These versions are affected across both 32-bit and 64-bit editions.

## Attack Vector

The MonikerLink bug is particularly dangerous because it bypasses the Office Protected View feature, which is designed to open potentially unsafe files in a read-only, sandboxed environment. By exploiting this vulnerability, attackers can bypass these security mechanisms and gain unauthorized access to sensitive information or take control of the victim's system.

## Impact

Successful exploitation of CVE-2024-21413 can result in:

- Remote code execution
- Data exfiltration
- Data encryption
- Credential harvesting
- Installation of malware

Given the severity of this vulnerability, it is crucial that affected systems be patched immediately to prevent potential exploitation.

## Mitigation

To protect against this vulnerability, it is strongly recommended that users and organizations:

- Apply the latest security updates provided by Microsoft.
- Ensure that Outlook and all related Office applications are updated to the latest versions.

For further details and updates, refer to the following sources:

- [Recorded Future](https://www.recordedfuture.com)
- [Triskele Labs](https://www.triskelelabs.com)
- [Vulcan Cyber](https://www.vulcan.io)

## License

This document is licensed under the [MIT License](LICENSE).