ArtifactQA
Evidence-bound inspection receipts for generated media and other binary artifacts.
ArtifactQA does not certify safety, copyright clearance, legal compliance or overall visual quality. It makes one narrower guarantee: an inspection verdict is attached to the SHA-256 of the exact file that was inspected. An unavailable inspector produces unknown, never pass.
Install
pip install artifactqa
Example
from artifactqa import Inspection, inspect
receipt = inspect(
"render.mp4",
inspector=lambda path: Inspection(verdict="pass", summary="no visible defect"),
inspector_name="local-policy-check",
policy_version="2026-08",
)
assert receipt.matches("render.mp4")
Integration guidance
Treat unknown as a blocking state for automated downstream actions. Store the receipt with the artifact and create a new receipt after each binary change. Use Approval Ledger or another human-review system for the decision to release an artifact.
Development
PYTHONPATH=src python -m unittest discover -s tests -v
uv build
License
MIT. See LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for artifactqa 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| artifactqa-0.1.0.tar.gz | 3.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| artifactqa-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.3 kB
Release files / artifactqa-0.1.0.tar.gz
| Download URL | artifactqa-0.1.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aade638cb8243997313be240af8f1bc184e56374081548c223c3df57b4bce653
|
|
BLAKE2b-256 checksum How to use checksums |
1783c10ba288b542fc42f7f7599dd25d739b57002edc03c77db592822c0c55f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency logRelease files / artifactqa-0.1.0-py3-none-any.whl
| Download URL | artifactqa-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3eaf5c58bacab1c824ddfa51b544bf48ebcaad2bb514cbb5f702c3748905d271
|
|
BLAKE2b-256 checksum How to use checksums |
54c89a9b7e322c37a68c35969137549d13a1b90f0c65386249e9edeb8e970635
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency logSecurity for artifactqa 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for artifactqa-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency logA 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.
