How ahmadfauzi34/artifact-proof-lab works
Artifact Proof Lab verifies local artifact directories or ZIPs against a declared manifest, applying structural, identity, and semantic checks before reporting a proof result. Its key trust distinction is that an internal manifest establishes consistency, while publisher identity requires a separately supplied digest. The graph follows the documented CLI workflow and sampled verifier implementation; the check subsystem represents documented capabilities whose individual implementations were not all sampled.
Main entry points: engine.py Verification engine · cli.py CLI · checks.py Integrity checks · model.py Findings and report
Components 10
Invocation
- CLI
src/artifact_proof/cli.py - Module entry
src/artifact_proof/__main__.py
Verification
- Verification engine
src/artifact_proof/engine.py - Artifact sources
src/artifact_proof/source.py - Manifest parser
src/artifact_proof/manifest.py - Integrity checks
src/artifact_proof/checks.py - Path validation
src/artifact_proof/paths.py - Failure types
src/artifact_proof/errors.py
Proof output
- Findings and report
src/artifact_proof/model.py
Other components
- Operator
Connections 12
- Operator → CLI: supplies artifact
- CLI → Verification engine: requests verification
- Module entry → CLI: starts CLI
- Verification engine → Artifact sources: opens artifact
- Verification engine → Manifest parser: parses manifest
- Manifest parser → Path validation: validates paths
- Verification engine → Integrity checks: runs checks
- Integrity checks → Artifact sources: reads files
- Integrity checks → Findings and report: creates findings
- Verification engine → Findings and report: assembles report
- Verification engine → Failure types: catches failures
- CLI → Findings and report: formats output