Generate an SBOM summary from your lockfile
Upload or paste your lockfile. We email you a readable SBOM summary: the components, their licences, known vulnerabilities, the AI components in your dependencies and how it measures up to the NTIA minimum elements. Free, no account.
The free result is a summary by email, with a preview of the CycloneDX components. The full CycloneDX 1.7 and SPDX 2.3 files are part of AIssue Pro.
What you get
- Inventory: the number of components, the ecosystem, and direct versus transitive dependencies where your lockfile records them (npm, uv and Cargo lockfiles do; requirements.txt does not).
- Licences: the count per licence, with copyleft, unknown and source-available licences flagged for your kind of project.
- Known vulnerabilities: the count by severity from OSV.dev, or the full list if you tick the box.
- AI components: model SDKs, LLM frameworks, vector databases and ML libraries found in your dependencies. They belong in your AI-BOM.
- The NTIA minimum elements: which ones your lockfile provides, which we add (package URLs, timestamp) and which you must add (your company as supplier).
- A CycloneDX preview: the first 20 components with their package URLs and licences, as they appear in the file.
What is an SBOM, and who asks for one
A software bill of materials lists the components a piece of software is made of: every library, with its exact version, supplier, licence and a unique identifier. It answers "are we affected?" in minutes when a new vulnerability is disclosed, and "what are we shipping?" when a customer asks.
Requests come from enterprise customers and procurement questionnaires, from US federal software suppliers (following Executive Order 14028 and the NTIA minimum elements), and, in the EU, from the Cyber Resilience Act, which requires manufacturers of products with digital elements to draw up an SBOM as part of their technical documentation.
The minimum elements
The NTIA's Minimum Elements for a Software Bill of Materials (2021) lists the data fields every SBOM should have: supplier name, component name, version, other unique identifiers, dependency relationship, author of the SBOM data and timestamp. A lockfile gives you most of them; the summary tells you which are missing.
SBOM vs. AI-BOM
An SBOM lists packages. For a system that uses AI, it misses what matters most: which models it calls (and which version), the datasets it was trained or grounded on, the AI services it sends data to, its prompts and MCP servers, and who oversees it. An AI-BOM adds those. CycloneDX describes them in the same file (its ML-BOM fields), and the EU AI Act's documentation duties ask for much of the same information.
Lockfile vs. manifest
package.json or pyproject.toml list ranges, such as ^4.17.0. An SBOM must
list what you actually ship, transitive dependencies included, so it is built from the lockfile:
package-lock.json, poetry.lock, uv.lock, Cargo.lock,
go.mod and the others.
From summary to file
With a free AIssue account, each repository gets its SBOM and AI-BOM, kept up to date as the lockfiles change. With Pro, download them as CycloneDX 1.7 or SPDX 2.3 from the dashboard, from CI through the API, or from your coding agent through the MCP server.
Questions
Do I get a CycloneDX or SPDX file?
Not from this free tool: it emails a readable summary and a preview of the CycloneDX components. The full CycloneDX 1.7 and SPDX 2.3 files, for every repository and kept up to date, are part of AIssue Pro.
What is the difference between CycloneDX and SPDX?
Both are standard SBOM formats. CycloneDX (OWASP) focuses on security use and also describes AI models and datasets (ML-BOM); SPDX (Linux Foundation, ISO/IEC 5962) grew from licence compliance. Many customers accept either.
Does an SBOM include transitive dependencies?
It should: they ship with your software. A lockfile lists them, which is why we ask for the lockfile and not package.json or pyproject.toml.
What is an AI-BOM?
An AI bill of materials adds what an SBOM misses for AI systems: the models, datasets, AI services, prompts and MCP servers a system uses, and how it is overseen. AIssue builds one for each repository.
How often should an SBOM be updated?
Whenever your dependencies change, so in practice with every release. A free AIssue account keeps it up to date from your repository.
Can I generate an SBOM in CI?
Yes, with AIssue Pro: the API returns the CycloneDX or SPDX file for a repository, so a CI step can download it with each release.
Related free tools
Dependency licence check
Upload a lockfile and see every dependency's licence. GPL, AGPL, unknown and changed licences are flagged for your kind of project. Free.
Dependency vulnerability check
Check requirements.txt, package-lock.json, poetry.lock and more against OSV.dev. Free report by email with fix commands. No account needed.
EU AI Act risk check
Answer a few questions and see your AI system's likely EU AI Act risk category, your role and its obligations with dates. Free, no account.
Last updated .