DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to rebuild the audit set and verify every hash with Veri Ink

Regenerate the 16-page demo and check that all images match their recorded SHA256 values.

Authorization notice. Veri Ink is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forAn ML engineer or auditor who needs proof that a handwriting dataset build is deterministic and unmodified.

The problemTraining and regression data is hard to trust when you cannot rebuild it or confirm the files were not changed.

The outcomeA local copy of the 16-page, 80-region audit set, with a passing pytest run that confirms determinism and input checks.

What you need first

  • Python and git installed
  • Terminal access to create a virtual environment and run commands
  • Basic familiarity with pip and pytest

Steps

  1. Run git clone https://github.com/znxzsy/VeriInk.git and then cd VeriInk.
  2. Run python -m venv .venv and then source .venv/bin/activate.
  3. Run pip install -e ".[dev]".
  4. Run python scripts/generate_demo.py, which rebuilds the examples and recomputes every hash before it exits.
  5. Run pytest -q and confirm that all tests pass.

Prompt for your agent

Clone https://github.com/znxzsy/VeriInk, create a virtual environment, install it with pip install -e ".[dev]", run python scripts/generate_demo.py, then run pytest -q. Report the number of pages and answer regions produced and whether pytest passed. Verify that examples/gallery/manifest.json lists a SHA256 for each image.

Caveat. The README describes the demo build and tests, but it does not say how long the run takes or what hardware it needs.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page