This release is a pre-release and may not be stable for production use.
aifeed (Python)
Independent Python verifier for the AIFeed protocol: signed content permissions for the AI web. Standard library only — no third-party dependencies.
pip install aifeed
Verify a directory or manifest
from aifeed import verify
report = verify.verify_directory('./my-site', domain='example.com')
print(report['result'], report['errors'])
from aifeed import verify
with open('ai.json', encoding='utf-8') as handle:
manifest = handle.read()
with open('ai-signature.json', encoding='utf-8') as handle:
signature = handle.read()
report = verify.verify(manifest, signature, domain='example.com')
Revocations, bundles, digests
from aifeed import verify
verify.verify_revocation_document(text, domain='example.com', governance_keys=keys)
verify.verify_bundle('./my-bundle') # offline audit bundle
verify.parse_strict(text) # strict JSON (no floats/dupes, NFC)
verify.verify_content_digest(header, body_bytes) # Content-Digest (RFC 9530)
AIFeed Markdown / MAKO documents
from aifeed import mako
parsed = mako.parse_frontmatter(page_bytes)
fields = mako.validate_aimd_fields(parsed['frontmatter']) # or validate_mako_fields
result = mako.verify_mako_container(container_text, page_url, body_bytes, public_key_value)
index = mako.verify_aimd_index(index_text, index_url, public_key_value)
Command line
aifeed-verify ./my-site --json # directory verification
aifeed-verify ai.json --domain example.com --json # single manifest + signature
aifeed-verify revocation ./revocation.json --json # multi-signature registry
aifeed-verify bundle ./my-bundle --json # offline bundle
aifeed-mako page.aifeed.md # frontmatter/container verification
The historical paths still work: import aifeed_verify / import aifeed_mako and
python clients/python/aifeed_verify.py are aliases for aifeed.verify / aifeed.mako.
Source
Part of aifeed-protocol (clients/python/),
differential-tested against the shared conformance vectors alongside the JavaScript
implementation. Specs: spec/en/; agent guide: docs/agent-quickstart.md.
Metadata
Release files for aifeed 1.0.0a1
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 | Actions |
|---|---|---|---|---|
| aifeed-1.0.0a1.tar.gz | 30.8 kB | Without provenance | Details for aifeed-1.0.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aifeed-1.0.0a1-py3-none-any.whl | Python 3 | none | any | Details for aifeed-1.0.0a1-py3-none-any.whl |
Total release size: 55.1 kB
Release files / aifeed-1.0.0a1.tar.gz
| Download URL | aifeed-1.0.0a1.tar.gz |
|---|---|
| Size | 30.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5076d38df798e31917e03b5219dfadf726e09ddaa3a5c74cd84aaabb5dc54f62
|
|
BLAKE2b-256 checksum How to use checksums |
1705dc7d4745c71c28fb49e347f7b7d9a1d09e38c4903644cd596e9b921f547e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.8
|
Release files / aifeed-1.0.0a1-py3-none-any.whl
| Download URL | aifeed-1.0.0a1-py3-none-any.whl |
|---|---|
| Size | 24.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8ecdc9d06d5db88d840835c92bc775f2a233435b81ccd7e9a69d6e4480e42eb2
|
|
BLAKE2b-256 checksum How to use checksums |
741da4c204578384b771938e5e01ce5638388b9ba57aa4828d3abfe4a3af8e77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.8
|
Security for aifeed 1.0.0a1
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.