aibomstd
The open standard for AI Bill of Materials.
Scan any repo and instantly know what AI components are running, which send data outside your boundary, and what your compliance risk is.
Install
pip install aibomstd
CLI — scan a repo in seconds
aibomstd scan ./my-repo
┌─────────────────────┬────────────┬──────────────┬──────────┬────────┐
│ Component │ Type │ Provider │ Boundary │ Risk │
├─────────────────────┼────────────┼──────────────┼──────────┼────────┤
│ openai │ api-client │ openai │ leaves │ high │
│ anthropic │ api-client │ anthropic │ leaves │ high │
│ langchain │ framework │ langchain-ai │ internal │ none │
│ torch │ framework │ pytorch │ internal │ none │
│ llama-3-8b.gguf │ model │ unknown │ internal │ medium │
│ training.jsonl │ dataset │ unknown │ internal │ medium │
└─────────────────────┴────────────┴──────────────┴──────────┴────────┘
Summary:
Total components : 6
Data egress : YES
Shadow AI : YES
Risk score : HIGH
Generated: my-repo.aibom.json
What it detects
| Component type | Examples |
|---|---|
api-client |
openai, anthropic, cohere, mistral, groq |
framework |
langchain, llama-index, transformers, ollama |
model |
.gguf, .safetensors, .pt, .onnx files |
dataset |
.jsonl, .parquet, .arrow files in data/ folders |
| Shadow AI | API keys in .env not declared in dependencies |
Auto-detects data-leaves-boundary and data-residency for every component.
Other CLI commands
# Validate a BOM file against the schema
aibomstd validate my-repo.aibom.json
# Check version
aibomstd version
SDK — generate BOMs in Python
from aibomstd import AiBomBuilder
from aibomstd.components import ModelComponent, ApiClientComponent
bom = (
AiBomBuilder(product="my-ai-product", version="1.0.0")
.add_component(ModelComponent(
name="llama-3-8b-instruct",
version="3.0",
provider="meta",
data_leaves_boundary=False,
data_residency="IN"
))
.add_component(ApiClientComponent(
name="gpt-4o",
version="2024-05-13",
provider="openai",
data_leaves_boundary=True,
data_residency="US"
))
)
print(bom.to_json()) # aibomstd JSON
bom.to_html() # self-contained HTML report
bom.to_cyclonedx() # CycloneDX v1.7 JSON
Schema
Every output document references the canonical schema:
https://aibomstd.com/schema/v0.1/aibomstd.schema.json
License
Apache 2.0 — https://aibomstd.com
Metadata
Release files for aibomstd 0.3.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 | |
|---|---|---|---|---|
| aibomstd-0.3.0.tar.gz | 20.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aibomstd-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 42.2 kB
Release files / aibomstd-0.3.0.tar.gz
| Download URL | aibomstd-0.3.0.tar.gz |
|---|---|
| Size | 20.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e08e5d25987c4e912fc55e6662f0fc1f6cb6445a1ef558fd61aab7339542043
|
|
BLAKE2b-256 checksum How to use checksums |
1ea71be99cee023cdaf7d6083a653953db3896bf00684d70b74e133f63aa4b0a
|
| 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 2, 2026.
Transparency logRelease files / aibomstd-0.3.0-py3-none-any.whl
| Download URL | aibomstd-0.3.0-py3-none-any.whl |
|---|---|
| Size | 21.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
27b8a4f635df6e9b75f23c263ca28e3e48c4084e8cec6240cba963548c8c6a70
|
|
BLAKE2b-256 checksum How to use checksums |
c9e98d556c7f4292c635a68d635cb42eac4eebfb34adfca427dfddee59ca4109
|
| 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 2, 2026.
Transparency logSecurity for aibomstd 0.3.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 aibomstd-0.3.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 2, 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.