semvec/pypi-packages huggingface dataset:
pentestflow 0.0.1
Placeholder package - under development
Requires Python: >=3.7
Keywords: pentesting, security, placeholder

# pentestflow

⚠️ **This is a placeholder package** ⚠️

The `pentestflow` package is currently under development. This placeholder has been published to reserve the package name on PyPI.

## Status

🚧 **Under Development** 🚧

## Future Plans

pentestflow will be a [brief description of what your package will do].

## Installation

This placeholder can be installed with:

```bash
pip install pentestflow
```

However, it currently contains no functionality.

## Stay Updated

- GitHub: [Your Repository URL]
- Issues: [Your Issues URL]
- Documentation: Coming soon

## Contact

For inquiries about this project, please contact [your contact info].

## License

MIT License - see LICENSE file for details.
dbferry 0.1.2
A secure, local-first database migration tool
Requires Python: >=3.13

# 🐬 dbferry

> A secure, local-first database migration tool — move your data safely between 2 Postgres Databases.

`dbferry` lets you migrate databases **without exposing credentials or data** to any third-party service. It’s **open-source**, **local-first**, and **transparent** by design.

---

## Key Features

-   **Local-first security** — No telemetry, no external calls, no remote logs.
-   **Schema + Data migration** — Migrate structure and contents seamlessly.
-   **Cross-engine support** — PostgreSQL, MySQL, SQLite, and more (extensible via adapters).
-   **Verifiable** — Check row counts and checksums for consistency.
-   **Simple YAML config** — Readable, declarative, and versionable.

---

## Quick Start

```bash
# Install using pip (simplest method)
pip install dbferry

# Install using uv tool
uv tool install dbferry

# Install using pipx (recommended for CLI tools)
pipx install dbferry

# Install directly from GitHub (latest development version)
pip install git+https://github.com/AbdLim/dbferry.git
```

Initialize your migration:

```bash
dbferry init
```

Then edit your generated `migration.yml`:

```yaml
source:
    type: postgres
    host: localhost
    port: 5432
    database: my-awesomedb
    user: postgres
    password: postgres
    sslmode: require

target:
    type: postgres
    host: localhost
    port: 5432
    database: targetdb
    user: postgres
    password: postgres
    sslmode: require

options:
    tables:
        - "*"
    verify_after_migration: true
```

Run the migration:

```bash
dbferry migrate --config migration.yml
```

Verify:

```bash
dbferry verify --config migration.yml
```

---

## Philosophy

`dbferry` is built on a few simple but strict principles:

| Principle           | Meaning                                               |
| ------------------- | ----------------------------------------------------- |
| **Local-first**     | Everything runs on your machine. Nothing is sent out. |
| **Transparent**     | Open code, auditable behavior.                        |
| **Composable**      | Extend it for new databases or workflows.             |
| **Safe by default** | Never modifies the source database.                   |
| **Verifiable**      | Trust built through evidence, not claims.             |

---

## Roadmap

-   [ ] PostgreSQL → MySQL/SQLite migrations
-   [ ] Checkpoint + resume system
-   [ ] Incremental sync support
-   [ ] CLI + Web UI parity
-   [ ] Plugin API for non-SQL engines (Mongo, ClickHouse, etc.)

---

## Security Promise

`dbferry` will **never**:

-   Send telemetry or logs to external servers
-   Store credentials outside your environment
-   Require network access beyond your databases

Everything happens locally — inspect the source and verify it yourself.

---

## Contributing

We welcome community contributions!  
Open an issue or PR at [github.com/AbdLim/dbferry](https://github.com/AbdLim/dbferry)

---

## License

Licensed under the **Apache License** — see [LICENSE](LICENSE) for details.

---

> “Move your data safely. Locally. Transparently.”  
> — The dbferry Project
jrl-cmakemodules 1.1.0
CMake utility toolbox
Requires Python: >=3.9

# Shared CMake submodule

[![Documentation Status](https://readthedocs.org/projects/jrl-cmakemodules/badge/?version=master)](https://jrl-cmakemodules.readthedocs.io/en/master/?badge=master)
[![pre-commit.ci status](https://results.pre-commit.ci/badge/github/jrl-umi3218/jrl-cmakemodules/master.svg)](https://results.pre-commit.ci/latest/github/jrl-umi3218/jrl-cmakemodules/master)
[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)


This repository is meant to be used as a submodule for any project
from CNRS LAAS/HPP or JRL.

It factorizes CMake mechanisms to provide a uniform look'n feel for
all packages.


Please see the documentation on the [wiki] for more information.

You can also checkout the more complete [documentation] of the modules.

[wiki]: http://github.com/jrl-umi3218/jrl-cmakemodules/wiki

[documentation]: http://jrl-cmakemodules.readthedocs.io/en/master/

## Supported CMake versions

We currently support CMake >= 3.22

## pre-commit

This project use [pre-commit](https://pre-commit.com) and [pre-commit.ci](https://pre-commit.ci).

You can get a nice documentation directly on those 2 projects, but here is a quickstart:

```
# install pre-commit:
python -m pip install pre-commit

# run all hooks on all files:
pre-commit run -a

# run automatically the hooks on the added / modified files, when you try to commit:
pre-commit install
```
inventree-rolling-stocktake 0.1.0
Support rolling stocktake for InvenTree
Requires Python: >=3.9
Keywords: inventree, plugin

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
[![PyPI](https://img.shields.io/pypi/v/inventree-rolling-stocktake)](https://pypi.org/project/inventree-rolling-stocktake/)
![PEP](https://github.com/inventree/rolling-stocktake-plugin/actions/workflows/pep.yaml/badge.svg)

# Rolling Stocktake Plugin
 
This is as plugin for [InvenTree](https://inventree.org) which provides integration of rolling stocktake for InvenTree.

## Description

Rolling stocktake is a method of inventory management where a small subset of inventory is counted on a regular basis, rather than counting the entire inventory at once. This plugin provides tools to facilitate rolling stocktake operations within InvenTree.

### Features

The plugin provides the following features:

- A backend API endpoint to retrieve items which are due for stocktake
- A frontend interface to view and manage rolling stocktake operations

### Dashboard Widget

Users are presented with a custom widget on their dashboard, which automatically fetches a single stock item which is due for stocktake:

![Dashboard Widget](docs/dashboard.png)

This widget allows users to quickly and easily perform stocktake operations on individual items. Once stocktake has been performed on a given item, the next item which is due for stocktake is automatically fetched.

## Installation

Install the plugin using the methods described below.

*Note: After the plugin is installed, it must be activated via the InvenTree plugin interface.*

### Via User Interface

Installation via the InvenTree plugin manager is the recommended approach:

The simplest way to install this plugin is from the InvenTree plugin interface. Enter the plugin name (`inventree-rolling-stocktake`) and click the `Install` button:

![Install Plugin](docs/install.png)

### Via Pip

To install manually via the command line, run the following command:

```bash
pip install rolling-stocktake
```

*Note: You must be operating within the InvenTree virtual environment!*

## Configuration

The plugin can be configured via the InvenTree plugin interface. The following settings are available:

| Setting | Description |
| --- | --- |
| Ignore External Locations | Ignore stock items which are located in external locations |
| Daily Limit | Maximum number of stock items to process per day (per user). |
| Allowed Group | Specify a group which is allowed to perform rolling stocktake operations. Leave blank to allow all users to perform stocktake operations. |

![Plugin Settings](docs/settings.png)
sphinxcontrib-lightbox2 0.5.0
Sphinx extension to add lightbox2 to each figure and image added in HTML
Requires Python: >=3.10

# sphinxcontrib-lightbox2

Sphinx extension to add [lightbox2](https://lokeshdhakar.com/projects/lightbox2/) to each figure and image added in HTML.

---

**[Read the documentation on ReadTheDocs!](https://sphinxcontrib-lightbox2.readthedocs.io/)**

---

Usually Sphinx themes limit their content width to a limit to improve readability. This creates a problem for large
images and diagrams which might be needed in technical documentation.

## Installation

Install the package using

```sh
pip install sphinxcontrib-lightbox2
```

Add `sphinxcontrib.lightbox2` to the list of `extensions` in your *conf.py*:

``` python
extensions = ["sphinxcontrib.lightbox2"]
```

## Configuration

Lightbox2 offers different configuration [options](https://lokeshdhakar.com/projects/lightbox2/#options).
These options are exposed in `sphinxcontrib-lightbox2` through options in the *conf.py*.

See the mapping of lightbox2 options to Sphinx options

| Lightbox2 Option Name | Sphinx Option Name | Default Value |
| ----------------------|--------------------|---------------|
| `alwaysShowNavOnTouchDevices` | `lightbox2_always_show_nav_on_touch_devices` | `False` |
| `albumLabel` | `lightbox2_album_label` | `"Image %1 of %2"` |
| `disableScrolling` | `lightbox2_disable_scrolling`| `False` |
| `fadeDuration` | `lightbox2_fade_duration`| `600` |
| `fitImagesInViewport` | `lightbox2_fit_images_in_viewport`| `True` |
| `imageFadeDuration` | `lightbox2_image_fade_duration`| `600` |
| `maxWidth` | `lightbox2_max_width`| `None` |
| `maxHeight` | `lightbox2_max_height`| `None` |
| `positionFromTop` | `lightbox2_position_from_top`| `50` |
| `resizeDuration` | `lightbox2_resize_duration`| `700` |
| `showImageNumberLabel` | `lightbox2_show_image_number_label`| `True` |
| `wrapAround` | `lightbox2_wrap_around`| `True` |

<!-- README is only included in documentation until here -->

## Examples

See the examples in the [documentation](https://sphinxcontrib-lightbox2.readthedocs.io/#examples).