Falcons-ai/surgeon-verify

0

stars

0

commits

Python

primary language

Aug 20, 2026

updated

README

surgeon-verify

Verify any FALCONS.AI Model Surgeon package. No account. Offline. One file.

Every model exported by Model Surgeon carries a signed, in-toto-style attestation covering every file in the package. This repository is the reference verifier — the same script embedded in every package — plus the format specification and test fixtures.

python verify_attestation.py package.zip

Output ends in a verdict: VERIFIED (exit 0), TAMPERED (exit 1), or a clear statement of what's missing. Change one byte anywhere in a package and watch VERIFIED become TAMPERED — try it on the fixtures:

python verify_attestation.py test/fixture_valid.zip      # → VERIFIED
python verify_attestation.py test/fixture_tampered.zip   # → TAMPERED (1 byte differs)
python test/run_tests.py                                 # runs the full matrix

Requirements: Python 3.9+. Signature verification uses the cryptography package (pip install cryptography); without it, file digests are still checked and the verdict says exactly what remains unverified — a missing library is never reported as tampering.

Why free verification? Signed creation is the paid act; universal verification is what makes the signature worth anything. Anyone you send a package to can check it — that's the point.

Publisher authentication: the attestation embeds the signing public key; the printed keyid fingerprint is what you pin to know who signed. FALCONS.AI publishes its fingerprints at falcons.ai.

Spec: SPEC.md · License: Apache-2.0 · Issues and third-party verifier implementations welcome — the fixtures are the conformance test.

Falcons-ai/surgeon-verify

0

stars

0

commits

Python

primary language

Aug 20, 2026

updated

README

surgeon-verify

Verify any FALCONS.AI Model Surgeon package. No account. Offline. One file.

Every model exported by Model Surgeon carries a signed, in-toto-style attestation covering every file in the package. This repository is the reference verifier — the same script embedded in every package — plus the format specification and test fixtures.

python verify_attestation.py package.zip

Output ends in a verdict: VERIFIED (exit 0), TAMPERED (exit 1), or a clear statement of what's missing. Change one byte anywhere in a package and watch VERIFIED become TAMPERED — try it on the fixtures:

python verify_attestation.py test/fixture_valid.zip      # → VERIFIED
python verify_attestation.py test/fixture_tampered.zip   # → TAMPERED (1 byte differs)
python test/run_tests.py                                 # runs the full matrix

Requirements: Python 3.9+. Signature verification uses the cryptography package (pip install cryptography); without it, file digests are still checked and the verdict says exactly what remains unverified — a missing library is never reported as tampering.

Why free verification? Signed creation is the paid act; universal verification is what makes the signature worth anything. Anyone you send a package to can check it — that's the point.

Publisher authentication: the attestation embeds the signing public key; the printed keyid fingerprint is what you pin to know who signed. FALCONS.AI publishes its fingerprints at falcons.ai.

Spec: SPEC.md · License: Apache-2.0 · Issues and third-party verifier implementations welcome — the fixtures are the conformance test.

Languages

Python

100.0%