semvec/pypi-packages huggingface dataset:
sommify 0.10.13
A package for recipe parsing
Requires Python: >=3.12

# Cook book

## Manual build and upload

```
python -m build
```

```
python -m twine upload dist/sommify-0.5.{}*
```

## Automatic build and upload

```bash
git tag {VERSION}
git push origin --tags
```

TODO - automated script for check and build
```bash
build.sh
```
intsys-car-v1 0.0.5
Basic control function for the intsys car v1
Requires Python: >=3.9

# intsys car v1

This repository contains code run on our intsys cars (v1). It's primarily code to control the motors, servos and sensors.

## Build & upload package

```bash
python -m build
python3 -m twine upload --repository testpypi dist/* --verbose
python3 -m twine upload dist/*
```
ionq-bits 0.1.0
IONQ - Naked Bits Visualizer. A real-time CPU emulator, system introspector, and bit-level register visualizer.
Requires Python: >=3.9
Keywords: cpu, emulator, visualizer, bits, registers, assembly, x86, arm64, riscv, tui, system-info, security-scanner

# IONQ - Naked Bits Visualizer

A real-time CPU emulator, system introspector, and bit-level register visualizer.

Watch every bit flip, every register change, and every stack push as your assembly code executes instruction by instruction.

## Features

- **Real-time CPU Emulator TUI** -- x86_64, ARM64, and RISC-V architectures powered by Unicorn Engine
- **Bit-level Visualization** -- See registers, flags, stack, and memory as raw bits updating live
- **Interactive Assembler REPL** -- Write and execute assembly instructions on the fly
- **Breakpoints & Watchpoints** -- Pause on addresses or register value changes
- **Memory Inspector** -- Hex dump with change highlighting and write capability
- **Deep System Introspection** -- CPU, GPU, BIOS, disk, network, and security info (cross-platform)
- **Security Scanner** -- Firewall status, antivirus, open ports, vulnerability assessment
- **12 Built-in Programs** -- 7 x86_64, 3 ARM64, 2 RISC-V sample programs to explore

## Installation

```bash
pip install ionq-bits
```

## Quick Start

```bash
# Show system info then launch the bits visualizer
ionq

# Launch the bits visualizer directly
ionq bits

# Load a custom assembly file
ionq bits -f mycode.asm

# Set architecture (x86_64, arm64, riscv)
ionq bits -a arm64

# Full system information
ionq info

# Live packet transfer stats
ionq packets

# Security scan
ionq scan

# Show all commands and keybindings
ionq help
```

## Keybindings (Bits Visualizer)

| Key | Action |
|-----|--------|
| `Space` | Play / Pause execution |
| `Right` | Step one instruction (while paused) |
| `Up/Down` | Increase / decrease speed |
| `R` | Reset current program |
| `P` | Switch to next program |
| `L` | Toggle loop mode |
| `M` | Toggle memory inspector |
| `` ` `` | Open interactive assembler / REPL |
| `Q` | Quit |

## REPL Commands

| Command | Description |
|---------|-------------|
| `<asm>` | Assemble and execute (e.g. `inc rax`) |
| `b <addr>` | Set breakpoint at hex address |
| `w <reg>` | Watch a register for changes |
| `w <reg>=<val>` | Watch for register == value |
| `m <addr>` | View memory at hex address |
| `mw <addr> <hex>` | Write hex bytes to memory |
| `regs` | Print all register values |

## Requirements

- Python 3.9+
- [Unicorn Engine](https://www.unicorn-engine.org/) -- CPU emulation
- [Capstone](https://www.capstone-engine.org/) -- Disassembly
- [Keystone Engine](https://www.keystone-engine.org/) -- Assembly
- [Textual](https://textual.textualize.io/) -- TUI framework
- [Rich](https://rich.readthedocs.io/) -- Terminal formatting
- [psutil](https://github.com/giampaolo/psutil) -- System info

## License

MIT License. See [LICENSE](LICENSE) for details.

## Author

**ATOM00blue** -- [GitHub](https://github.com/ATOM00blue)
linehaul 1.0.3
User-Agent parsing for PyPI analytics
Requires Python: <4,>=3.11
Keywords: pypi, user-agent, parsing

# About

Implementation of linehaul to feed the PyPI public BigQuery dataset via Google Cloud Functions.

The function is triggerd by the CDN logs created in a Cloud Storage bucket. It parses the logs and streams them to the BigQuery public dataset.

# Deploy

These functions auto-deploy on merge to the `main` branch via a Cloud Build trigger on this repository.
toolsalert 0.1.0
Simple alert helpers for Slack and Telegram using requests.
Requires Python: >=3.9

# toolsalert

Simple alert helpers for **Slack** and **Telegram**, implemented using `requests`.

## Install

```bash
pip install toolsalert
```

## Usage

```python
from toolsalert import AlertSlack, AlertTelegram

# Slack
slack_alert = AlertSlack(slack_token, slack_channel, bot_name, bot_icon)
slack_alert.send("Hello from Slack")

# Telegram
tg = AlertTelegram(api_token="123456:ABCDEF...", chat_id="123456789")
tg.send("Hello from Telegram")
tg.send_no_preview("<b>HTML</b> message without link preview")
tg.send_photo("https://example.com/some_image.jpg")
```

## Notes

- Do **not** hardcode real tokens/webhook URLs in code committed to git.
- Use environment variables or a secret manager for credentials.
edf-neon-server 2.1.0
EDF Neon Server
Requires Python: >=3.12
Keywords: edf, neon, server

# EDF Neon Server


## Introduction

This server implements the API for Neon service. It uses EDF Fusion framework as a library to ease maintainance and take advantage of new generic features as they become available.

> [!TIP]
> This documentation does not aim at completeness but provides an overview of the main features

## Events

Neon, when configured to do so, can emit events using webhooks. Here is a list of event's categories it can emit:

- `create_case`
- `update_case`
- `create_sample`
- `update_sample`

Event's structure looks like this:

```json
{
    "source": "event's source, service's name is often used as source",
    "category": "event's category, the nature of the event",
    "case": {},
    "ext": {},
}
```
edf-iron-x-iris 2.1.0
EDF Iron x DFIR IRIS Proxy
Requires Python: >=3.12
Keywords: edf, iron, proxy, dfir-iris

# EDF Iron x IRIS Proxy

## Introduction

This API proxy acts as a middleware between Iron server and DFIR-IRIS server. It translates case API calls to DFIR-IRIS API calls and stores a mapping of Iron cases in DFIR-IRIS.
edf-iron-server 2.1.0
EDF Iron Server
Requires Python: >=3.12
Keywords: edf, iron, server

# EDF Iron Server


## Introduction

This server implements the API for Iron service. It uses EDF Fusion framework as a library to ease maintainance and take advantage of new generic features as they become available.

> [!TIP]
> This documentation does not aim at completeness but provides an overview of the main features


## Services

Iron offers a single web interface to perform case management operations across different services including:

- [Carbon](https://github.com/cert-edf/carbon)
- [Helium](https://github.com/cert-edf/helium)
- [Neon](https://github.com/cert-edf/neon)
- [DFIR-IRIS](https://github.com/dfir-iris/iris-web)

New service integration requires the service to implement `FusionCaseAPI` defined in the [fusion library](https://github.com/cert-edf/fusion). If the service does not directly implement the API, an API proxy or middleware can be implemented. Carbon, Helium and Neon implement the API directly. DFIR-IRIS is integrated through a middleware.


## Events

Iron, when configured to do so, can emit events using webhooks. Here is a list of event's categories it can emit:

- `create_case`
- `update_case`

Event's structure looks like this:

```json
{
    "source": "event's source, service's name is often used as source",
    "category": "event's category, the nature of the event",
    "case": {},
    "ext": {},
}
```

Both `case` and `ext` are objects used to store information respectively about the case related to the event and extended data specific to the event.

Iron's configuration allows to define a general webhook which receives all events for all cases. It is also possible to define per-case webhooks to trigger case specific scenarios.
edf-helium-server 2.1.0
EDF Helium Server
Requires Python: >=3.12
Keywords: edf, helium, server

# EDF Helium Server


## Introduction

This server implements the API for Helium service. It uses EDF Fusion framework as a library to ease maintainance and take advantage of new generic features as they become available.

> [!TIP]
> This documentation does not aim at completeness but provides an overview of the main features


## Events

Helium, when configured to do so, can emit events using webhooks. Here is a list of event's categories it can emit:

- `create_case`
- `update_case`
- `create_collector`
- `import_collector`
- `create_collection`
- `update_collection`

Event's structure looks like this:

```json
{
    "source": "event's source, service's name is often used as source",
    "category": "event's category, the nature of the event",
    "case": {},
    "ext": {},
}
```
edf-carbon-server 3.0.0
EDF Carbon Server
Requires Python: >=3.12
Keywords: edf, carbon, server

# EDF Carbon Server


## Introduction

This server implements the API for Carbon service. It uses EDF Fusion framework as a library to ease maintainance and take advantage of new generic features as they become available.

> [!TIP]
> This documentation does not aim at completeness but provides an overview of the main features


## Events

Carbon, when configured to do so, can emit events using webhooks. Here is a list of event's categories it can emit:

- `create_case`
- `update_case`

Event's structure looks like this:

```json
{
    "source": "event's source, service's name is often used as source",
    "category": "event's category, the nature of the event",
    "case": {},
    "ext": {},
}
```