Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

MLprints

A framework for generating, training, attacking, and verifying LLM fingerprints.

Quick start

1 - Install

uv sync

Then use uv run mlprints … for the examples below, or activate the environment uv created.

Alternatively, in a virtual environment (with Python ≥ 3.12):

pip install -e .

2 - Set experiments directory

export MLPRINTS_EXPERIMENTS_DIR=/path/to/experiments

Alternatively, pass --experiments-dir to mlprints generate.

Some assets are downloaded on demand and cached locally (no large bundled data tree).

Registered fingerprints are chain_hash, implicit_fp, instructional_fp, mergeprint, perinucleus, proflingo, rofl, and semcond_watermark. All except proflingo and rofl support training. Registered attacks are perplexity_filtering, suppress_{topk,neighbor,lookahead}, detect_{topk,neighbor,lookahead}, and bigram_suppression. Available verifiers are match, watermark_ztest, and adg_ztest.

Taxonomy

Fingerprints and attacks, named after the files in src/mlprints/fingerprint/ and src/mlprints/attack/.

flowchart TB
  FP[Fingerprints]

  FP --> INV[Invasive]
  FP --> INT[Intrinsic]

  INV --> MEM[Memorization-based]
  INV --> STAT[Statistical]

  MEM --> instructional_fp
  MEM --> chain_hash
  MEM --> perinucleus
  MEM --> implicit_fp

  STAT --> semcond_watermark

  INT --> rofl
  INT --> proflingo
  INT --> mergeprint
flowchart TB
  ATK[Attacks]

  ATK --> perplexity_filtering
  ATK --> response_suppression
  ATK --> response_detection
  ATK --> bigram_suppression

  response_suppression --> suppress_topk
  response_suppression --> suppress_neighbor
  response_suppression --> suppress_lookahead

  response_detection --> detect_topk
  response_detection --> detect_neighbor
  response_detection --> detect_lookahead

CLI

Command Role
mlprints generate CONFIG.yaml Generate fingerprints; add --train to train in the same run when supported.
mlprints train CONFIG.yaml --fingerprints-dir DIR Train on a previous generate output (DIR must contain fingerprints.yaml).
mlprints attack CONFIG.yaml --model-checkpoint MODEL Prepare an attack against a model or training checkpoint.
mlprints measure utility CONFIG.yaml Measure model utility with LightEval tasks.
mlprints verify CONFIG.yaml --fingerprints DIR --model MODEL Verify a model using saved fingerprints.

Run mlprints <command> --help for command-specific options.

Generate fingerprints example

mlprints generate src/mlprints/configs/fingerprint/perinucleus_config.yaml

Generate and train in one step (algorithms that support training):

mlprints generate src/mlprints/configs/fingerprint/perinucleus_config.yaml --train

For example, the trainable Chain & Hash fingerprint has a bundled config:

mlprints generate src/mlprints/configs/fingerprint/chain_hash_config.yaml --train

Under your experiments root, each run writes:

  • fingerprints/{algo}/{timestamp}/fingerprints.yaml
  • fingerprints/{algo}/{timestamp}/config.yaml
  • fingerprints/{algo}/{timestamp}/metadata.yaml

Train fingerprints example

mlprints train src/mlprints/configs/fingerprint/perinucleus_config.yaml \
  --fingerprints-dir /path/to/fingerprints/{algo}/{timestamp}

Checkpoints and training metadata are written under that fingerprint directory (e.g. trained/.../checkpoints/).

Prepare an attack example

mlprints attack src/mlprints/configs/attack/perplexity_filtering_config.yaml \
  --model-checkpoint /path/to/model-or-checkpoint

Measure utility example

mlprints measure utility src/mlprints/configs/utility/leaderboard_config.yaml

The config may use native LightEval task expressions in evaluation.tasks (comma-separated, optional |fewshot).

Verify fingerprints example

mlprints verify src/mlprints/configs/verify/match_config.yaml \
  --fingerprints /path/to/fingerprints/{algo}/{timestamp} \
  --model /path/to/model \
  --apply-chat-template

Verification results are written under verification/{timestamp}/.

Local implementations

Pass --implementation path/to/implementation.py to generate, train, attack, or verify to use an implementation without registering it in the package. Custom attacks are saved with their implementation and load automatically from the resulting attack directory. See the _blueprint.py files under src/mlprints/{fingerprint,attack,verify}/ for the required function and class contracts.

Grid configs

Wrap any parameter in {grid: [...]} to run every combination:

learning_rate:
  grid: [1.0e-5, 2.0e-5]

Generation expands grids under algo.params; training expands algo.training; verification expands verifier.params and inference. Ordinary YAML lists remain unchanged. Use --skip-existing to reuse matching runs.

How to add a new fingerprint

  1. Implement generation (and optional training) in src/mlprints/fingerprint/.
  2. Register in FINGERPRINT_ALGOS in src/mlprints/common/fingerprints.py.
  3. Add src/mlprints/configs/fingerprint/<name>_config.yaml with algo.name, algo.params, and optionally algo.training if training is required.
  4. Implement and register a verifier when the scheme needs one.

Contributing

Issues and pull requests are very welcome. For questions, contact edoardo@sentient.xyz.

Disclaimer: Most of the code pushed has been either handwritten, or written with AI on a first passage only then to be severly revised and edited for performance and clarity over countless hours. The end result is a repo that is meant to be very flexible, readable and usable by AI and humans alike. Therefore, any contributions that worsen the standard set will be asked to be revised. Any contributions that improve the standard are very welcome (and such is continuously improved). It is both a means as much as an ends (instead of only the first, in which case we would have spared ourselves plenty of development time).

License

Released under the GNU Affero General Public License v3.0 or later. Full text in LICENSE.

Metadata

Release files for mlprints 0.1.0b12

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mlprints 0.1.0b12
File Size Uploaded Provenance Actions
mlprints-0.1.0b12.tar.gz 116.0 kB Without provenance Details for mlprints-0.1.0b12.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mlprints 0.1.0b12
File Interpreter ABI Platform Actions
mlprints-0.1.0b12-py3-none-any.whl Python 3 none any Details for mlprints-0.1.0b12-py3-none-any.whl

Total release size: 258.5 kB

Release files / mlprints-0.1.0b12.tar.gz

Download URL mlprints-0.1.0b12.tar.gz
Size 116.0 kB
Tags Source
SHA-256 checksum
How to use checksums
ca8d572e6d2e57f9d1162cb1fabf90de9836c4fb3d9621e4938ea1b116f4a9d4
BLAKE2b-256 checksum
How to use checksums
26d4e3edd9ea8c8dac37f9a3f68d33655fb76fccce5162b4064de1381f8d5f1c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / mlprints-0.1.0b12-py3-none-any.whl

Download URL mlprints-0.1.0b12-py3-none-any.whl
Size 142.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2c99ab9db3c9a6a8767e10312ef07b0ce4c15fba6a997df22f749f880f82fa01
BLAKE2b-256 checksum
How to use checksums
b695255e304b005dd0c06302ae3c24500c33e460a4aa28b3b133b8ab554be91b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for mlprints 0.1.0b12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page