Skip to content

    Type a page, a command such as keryn scan, or a rule id.

    Read an AI-BOM

    View as Markdown

    Know which AI technologies your code references, where, and how sure Keryn is about each one, in a file that Dependency-Track, GitLab’s dependency list and any other SBOM tool can read. The AI-BOM is plain CycloneDX 1.6.

    The AI-BOM lists AI components only. For every package your lockfiles lock, with licences and the dependency graph, write the dependency SBOM instead: keryn sbom (CycloneDX 1.6 or SPDX 2.3, next release; see software composition analysis).

    • A repository to look at. Any language works for the inventory; the AI-BOM comes from the inventory rules, not from a full scan.
    • On the CLI, jq makes the file easy to read. Nothing here needs a network.

    In Keryn Web, scan a folder or repository and open the AI-BOM tab: the key assets (models, services and prompt files) first, then SDKs, each with the findings in the files that use it. Export, CycloneDX 1.6 AI-BOM downloads the file. Nothing is uploaded: the file is generated in the tab.

    Each component is something AI-related that the code references: a provider SDK (openai, anthropic), a model id, an agent framework, an MCP server or client, a vector store, a prompt file, a tool definition.

    Every component carries the places Keryn found it, so a reviewer can open the file and look:

    Terminal window
    keryn bom . 2>/dev/null | jq -c '.components[0] | {name, found: .evidence.occurrences, properties: [.properties[] | select(.name != "keryn:assetProvenance") | "\(.name)=\(.value)"]}'
    {"name":"anthropic","found":[{"location":"support.py","line":1}],"properties":["keryn:category=llm-sdk","keryn:basis=observed-in-source","keryn:scope=direct","keryn:rules=keryn.inv.lib.anthropic","keryn:provider=anthropic"]}
    • evidence.occurrences: every file and line, so nothing in the BOM is a claim without a place.
    • keryn:basis: how it was observed. observed-in-source is a reference in code; it is observed-in-browser or observed-on-network when you fed Keryn a page snapshot or a list of ports, and a lockfile-only or docs-only mention is labelled as such.
    • keryn:rules: the inventory rule that recognised it, which you can look up with keryn explain.
    Terminal window
    keryn bom . 2>/dev/null | jq -r '.metadata.properties[] | select(.name != "keryn:coverage.rules") | "\(.name): \(.value)"'
    keryn:coverage.files: 3 scanned, 0 skipped
    keryn:caveat: Inventory reflects static references only. Absence is not evidence of absence; presence does not prove runtime use.

    A third property, keryn:coverage.rules, says how many rules ran (for the AI-BOM, the inventory pack).

    A real file is on the formats page.

    Compare two AI-BOMs, or a BOM with a branch, to see the components a change brings in: that is the whole of baselines and deltas.

    Each line of an AI-BOM is an edge from your code to something it depends on or calls: a provider, a model, a store. You can name the place in the code for each one, and you know the basis it rests on. That is a different claim from “this application uses these services at run time”. The BOM says what the code references. It cannot see what is configured elsewhere, and it does not claim to.