PAGES
← all tools
◆ Software Supply Chain Security

sbomify

v26.11.0 open-source

sbomify is an SBOM and document management platform for uploading, managing, and sharing Software Bill of MaterialsSoftware Bill of MaterialsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. with stakeholders, available self-hosted or via app.sbomify.com.

Summary

sbomify is an open-source SBOM and document management platform that gives teams a central place to upload, store, and share Software Bills of Materials with stakeholders or the public. It can be self-hosted or run as a hosted service at app.sbomify.com, and it pairs with a GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. module to generate SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. automatically from lock files and Dockerfiles. It reads and produces CycloneDXCycloneDXAn open standard for describing software components and their dependencies, vulnerabilities and other supply-chain information. Tools use it to exchange bills of materials and related evidence. and SPDXSPDXAn open standard for describing software components, licenses and their relationships. Its documents let different tools exchange a software bill of materials without inventing a new format. (including SPDX 3SPDX 3An open standard from the Linux Foundation for expressing software bill-of-materials data, letting cyber tools exchange dependency, license, and vulnerability metadata in a machine-readable, interoperable format..0), covers VEX documents in CycloneDX, OpenVEX, and CSAF, and handles CBOM ingestion, which points it at compliance owners and application security teams needing an audit trail rather than at scanners themselves. It sits in the SBOM lifecycle management space, distinct from the tools that generate or scan for vulnerabilities upstream. Its CI pipeline, workspace API, and steady stream of releases indicate active, ongoing development.

sbomify is an SBOM and document management platform for uploading, managing, and sharing Software Bill of Materials with stakeholders, available self-hosted or via app.sbomify.com.

How sbomify helps

Which of my products still have no SBOM attached, or one that's gone stale?

tracks a freshness window per component and flags SBOMs as stale once they age past it, so a product or release page shows exactly what's missing or overdue

Where do I stand on a specific CVE across every product I ship?

rolls scanner findings up by component into a workspace-wide vulnerability view with EPSS, CVSS 4.0, CISA KEV and ENISA EUVD exploited flags, and lets you record a formal risk acceptance with an owner and expiry instead of leaving it open

Are the VEX statements I've published still backed by current data?

runs scheduled drift detection against stored VEX documents and surfaces the ones going stale or the High/Critical findings that have no VEX coverage at all

Which packages in my inventory are outright malicious, not just vulnerable?

separates malicious-package findings out from CVE-based findings so they don't get lost in ordinary vulnerability triage

Can I show an auditor which licenses and cryptographic assets are in a given release?

ingests CBOMs alongside SBOMs and exposes a licensing view with risk categories per SPDX identifier, plus CSV exports for inventory, licenses, findings and vulnerabilities

Am I meeting my patch SLAs and CRA obligations for a given product?

tracks vulnerability age and mean time to remediate and plots them against a patch SLA matrix and five CRA KPIs on the posture view

all 24 features, with the evidence for each →

Languages

Not documented

Features

24 capabilities across 2 capability groups · 12 backed by code, an API document or a real run

Built from sbomify's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • sbomify covers 1 of the 5 supply chain security capabilities we track.
  • sbomify covers 1 of the 2 vulnerability management capabilities we track.

What sbomify offers you

  • REST API8
  • CI/CD pipeline integration2
  • Scheduled jobs2
  • CSV data export1
  • Role-based access control1
  • Command-line interface
CycloneDX SBOM 2 features Supply chain security since 2026
VEX authoring, upload, and triage verified Lets users create, upload, and triage VEX documents in multiple formats, managing their full lifecycle including sync to Dependency-Track and detection of stale or uncovered statements. 15 releases · 21 other sources · first seen Jul 2026

Shared capability: CycloneDX SBOM

Also counts toward: Scheduled jobs

release 15 total

  • VEX improvements: VEX-suppressed findings are now shown everywhere vulnerabilities are counted, including the Trends tab; the VEX statement cap is raised to 50,000 with a warning displayed when that limit is approached; and the VEX review view now shows which versions a submission applies to. v26.11.0 · Nov 2026 · source · release history
  • Adds a VEX approval queue where AI agents submit VEX rulings using a new AI-agent token and a human approves or rejects them on the Review tab. v26.10.0 · Oct 2026 · source · release history
  • New endpoint POST /api/v1/vulnerability-scanning/components/{component_id}/vex-submissions 26.10.0 · Oct 2026 · source · release history
  • New endpoint POST /api/v1/vulnerability-scanning/vex-submissions/{submission_id}/withdraw 26.10.0 · Oct 2026 · source · release history
  • New endpoint GET /api/v1/vulnerability-scanning/workspaces/{team_key}/vex-submissions 26.10.0 · Oct 2026 · source · release history
  • New endpoint GET /api/v1/vulnerability-scanning/vex-submissions/{submission_id} 26.10.0 · Oct 2026 · source · release history

api 21 total

CBOM ingestion and management verified Ingests Cryptography Bills of Materials, normalises them to CycloneDX 1.7, and presents them in a workspace-level CBOM dashboard. 1 release · 7 other sources · first seen Jul 2026

Shared capability: CycloneDX SBOM

Also counts toward: REST API

release

  • Adds CBOM (Cryptography Bill of Materials) ingestion across every lineage, with CycloneDX 1.7 registry normalization and a workspace dashboard. v26.7.1 · Jul 2026 · source · release history

command line

  • --demote-mixed — Also re-tag mixed cbom-typed rows back to sbom. This overrides deliberately-set cbom tags (tool-generated CBOMs are mixed documents) — run only when the workspace's cbom rows are known to come from the old any-crypto auto-detect. v26.7.1 · Jul 2026 · command-line history

api

Vulnerability scanning 1 feature Vulnerability management since 2026
Vulnerability scanning verified Scans artifacts and components for known vulnerabilities and surfaces the findings within the platform. 10 releases · 6 other sources · first seen Aug 2026

Shared capability: Vulnerability scanning

Also counts toward: REST API

release 10 total

  • Vulnerability IDs are now linked to sbomify Insights. v26.11.0 · Nov 2026 · source · release history
  • New endpoint GET /api/v1/vulnerability-scanning/components/{component_id}/vex-submissions⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ 26.10.0 · Oct 2026 · source · release history
  • New endpoint GET /api/v1/vulnerability-scanning/workspaces/{team_key}/fix-prompt 26.10.0 · Oct 2026 · source · release history
  • New endpoint GET /api/v1/vulnerability-scanning/workspaces/{team_key}/vulnerabilities 26.10.0 · Oct 2026 · source · release history
  • Stores findings in a dedicated database table enabling server-side search, severity, VEX state, and KEV filtering and pagination — replacing in-process Python aggregation over raw scan JSON blobs. announced · Sep 2026 · source · release history
  • Malicious packages are now a distinct structural category, reclassified at read time across all historical scans without rescanning, and no longer fall through to a default medium severity. announced · Aug 2026 · source · release history

api

Other / not yet classified 21 features Features we have not matched to a capability yet. A suggested match is marked.
Compliance management verified Lets users create and update compliance records and controls to track and demonstrate adherence to regulatory or policy requirements. 18 releases · 23 other sources · first seen Jan 2026

Also counts toward: REST API

release 18 total

  • sbomify now prepares, tracks, and records CRA Article 14 reports for submission to ENISA's portal. v26.11.0 · Nov 2026 · source · release history
  • Adds Vanta integration, enabled via new VANTA_* environment variables, to sync frameworks and controls from Vanta with optional Trust Center publishing.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v26.10.0 · Oct 2026 · source · release history
  • Adds an assessments requirements matrix view. v26.10.0 · Oct 2026 · source · release history
  • Deprecated endpoint GET /api/v1/plugins/registered (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/licensing/licenses (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint POST /api/v1/controls/automation/sync/ (still works) 26.8.0 · Sep 2026 · source · release history

example

  • Enable Vanta integration in a self-hosted deployment to sync compliance frameworks and controls. VANTA_*=<your-vanta-credentials> v26.10.0 · Oct 2026 · source
  • Record formal risk acceptance for a vulnerability finding — capturing an owner and expiry — so the risk appears tracked rather than ignored in compliance reports. On a vulnerability's detail page, open the 'Risk Acceptance' panel, enter the owner name and expiry date, then click 'Accept'. v26.8.0 · Aug 2026 · source

api 21 total

Workspace and access management verified Manages workspace members, branding, and API token binding to control access across the platform. 25 releases · 12 other sources · first seen Mar 2025

Also counts toward: REST API

release 25 total

  • Each API token's type is now shown in the token list. v26.11.0 · Nov 2026 · source · release history
  • Creating an access request now requires authentication and takes no request body; all access-request routes enforce token scopes. v26.10.0 · Oct 2026 · source · release history
  • Pending Owner invitations now grant Admin instead of Owner — re-send affected invitations. v26.10.0 · Oct 2026 · source · release history
  • Environment variables TEAMS_*_ROLES are renamed to WORKSPACE_*_ROLES; old names work as aliases for now. v26.10.0 · Oct 2026 · source · release history
  • The branding PATCH endpoint now only accepts null for icon and logo fields. v26.10.0 · Oct 2026 · source · release history
  • GET /workspaces/ now shows members, invitations, and billing data only to admins. v26.10.0 · Oct 2026 · source · release history

api 12 total

Product and component inventory verified Organises the software inventory into products, components, and releases so users can track exactly what ships and what it contains. 23 releases · 10 other sources · first seen Aug 2025

Also counts toward: REST API

release 23 total

  • Deprecated endpoint PUT /api/v1/products/{product_id}/links (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/workspaces/{team_key}/suppliers (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/products/{product_id}/links (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/products (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint POST /api/v1/components (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint POST /api/v1/products (still works) 26.8.0 · Sep 2026 · source · release history

api 10 total

SBOM and artifact management verified Stores and versions SBOMs and related artifacts, letting users filter by component, version, and format. 18 releases · 11 other sources · first seen Jul 2025

Also counts toward: REST API

release 18 total

  • POST /api/v1/sboms/upload-file/{component_id}: param review (query) added 26.10.0 · Oct 2026 · source · release history
  • Validates SPDX 3.0.1 documents against the official SPDX 3.0.1 schema on upload, naming validation failures rather than surfacing a generic parse error; SPDX 3.0/3.0.0 documents are left intentionally lenient, and SPDX 3.1 receives an explicit refusal naming accepted versions (2.2, 2.3, 3.0.x). announced · Sep 2026 · source · release history
  • Automatically converts SPDX 3 SBOMs to a scanner-readable format for osv-scanner and Dependency Track rather than returning a skip instructing the user to run syft convert manually. announced · Sep 2026 · source · release history
  • Activates the CISA 2026 Minimum Elements scoring plugin (replacing the 2021 NTIA elements), which had been implemented but never registered and therefore had never run for any user. announced · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/sboms/{sbom_id}/releases (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/sboms/sbom/{sbom_id}/signature (still works) 26.8.0 · Sep 2026 · source · release history

example

  • Configure the sbomify service to generate secure, time-limited URLs for sharing private SBOM components. export SIGNED_URL_SALT="$(openssl rand -hex 32)" v0.16.6 · Jul 2025 · source

api 10 total

Release and version management verified Allows users to create, track, and consolidate software releases using standardized naming conventions and exportable artifact sets. 18 releases · 5 other sources · first seen May 2025

Also counts toward: REST API, Scheduled jobs

release 18 total

  • A release can now link to another product's release, with linked releases manageable from the release page. v26.11.0 · Nov 2026 · source · release history
  • The manufacturer's keyless Sigstore signature is now preserved on CRA export bundles. v26.11.0 · Nov 2026 · source · release history
  • /releases/{id}/artifacts?mode=available now requires the release:manage scope. v26.10.0 · Oct 2026 · source · release history
  • Deprecated endpoint DELETE /api/v1/releases/{release_id} (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/releases (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint PATCH /api/v1/releases/{release_id} (still works) 26.8.0 · Sep 2026 · source · release history

example

  • Create a new beta release to organize specific SBOM versions. curl -X POST https://<instance>/api/v1/releases \ -H 'Authorization: Bearer <token>' \ -H 'Content-Type: application/json' \ -d '{"version": "v0.2.0-beta", "status": "beta"}' v0.16 · Jul 2025 · source
  • Generate a consolidated SBOM for a specific release to distribute to clients. curl -o sbom.json https://<instance>/api/v1/releases/<release_id>/download v0.16 · Jul 2025 · source

api

Document hub and compliance evidence sharing verified Provides a centralized space to upload, version, and share non-SBOM documents like manuals and compliance reports alongside product inventory. 8 releases · 8 other sources · first seen Jul 2025

release 8 total

  • Adds DOCUMENT_FILE, DOCUMENT_TYPE, DOCUMENT_VERSION, DOCUMENT_NAME, and DOCUMENT_COMPLIANCE_SUBCATEGORY env vars to publish arbitrary documents (pentest reports, compliance PDFs, NDAs) directly from a pipeline without manual upload.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Sep 2026 · source · release history
  • Deprecated endpoint POST /api/v1/documents/ (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint DELETE /api/v1/documents/{document_id} (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/documents/{document_id} (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint PATCH /api/v1/documents/{document_id} (still works) 26.8.0 · Sep 2026 · source · release history
  • Adds inline editing functionality with form validation for existing documents v0.16.6 · Jul 2025 · source · release history

api 8 total

Vulnerability tracking and trend analysis verified Offers real-time metrics, historical data visualization, and trend dashboards to monitor the security posture of components over time. 6 releases · 5 other sources · first seen Aug 2025

release

  • Adds a Vulnerabilities page with a deduplicated list of open findings, release and SBOM-version filters, and Fix/Triage prompts for coding agents. v26.10.0 · Oct 2026 · source · release history
  • Adds history_limit query parameter and all_runs_total field to GET /plugins/assessments/{sbom_id}, capping all_runs at 50 runs. v26.10.0 · Oct 2026 · source · release history
  • GET /plugins/assessments/{sbom_id} caps all_runs at 50; use history_limit and all_runs_total for full history. v26.10.0 · Oct 2026 · source · release history
  • New CRA patch SLA targets, defaulting to Critical 7 / High 30 / Medium 90 days, gate five computable KPIs: mean time to triage, mean time to remediate, open criticals with KEV split, patch SLA compliance, and VEX publication latency. announced · Aug 2026 · source · release history
  • Introduces Vulnerability trends dashboard with interactive charts for visualizing security data over time v0.21 · Dec 2025 · source · release history
  • Introduces a Vulnerability Dashboard for real-time metrics, historical tracking, and time series analysis v0.17 · Aug 2025 · source · release history

api

Trust Center verified Provides a customer-facing portal where VEX documents, CBOM downloads, and a vulnerability posture panel can be shared externally. 8 releases · 2 other sources · first seen Feb 2026

Also counts toward: REST API

release 8 total

  • The trust center advisory page is redesigned around an 'Am I affected?' workflow. v26.11.0 · Nov 2026 · source · release history
  • Adds ISO 27001 and SOC 2 Type I / Type II certification badge display to Trust Center workspaces, earned only when a file-backed document is attached to a published company-wide component. announced · Sep 2026 · source · release history
  • Adds a workspace toggle for vulnerability posture visibility on public Trust Center release pages, which previously exposed severity counts and all findings by ID, package, and version to anyone with the link with no opt-in. announced · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/internal/domains (still works) 26.8.0 · Sep 2026 · source · release history
  • Trust Center redesigned with a filter sidebar, dense advisory table with per-product version rows rendering version ranges as comparison strings (e.g. >= 11.2.0, < 11.2.4-h20), live faceting, and a JavaScript-free plain form fallback. announced · Aug 2026 · source · release history
  • security.txt generation follows BSI TR-03183-3 shape with separate CSIRT contact and report-page slots, an optional CSAF pointer, and an Expires field clamped to at most one year; shares data with the CRA wizard. announced · Aug 2026 · source · release history

api

Bulk database migration CLI verified Provides CLI options to process large datasets in configurable batches, enabling safe bulk migrations without overwhelming the database. 4 releases · 6 other sources · first seen Jul 2026

release

  • Token hashing migration access_tokens.0012 cannot be rolled back — old releases cannot authenticate API tokens after it runs. v26.10.0 · Oct 2026 · source · release history
  • The findings migration drops the vulnerability_scanning_findings table; old pods in a rolling deploy will fail. Run manage.py backfill_findings --missing-only to rebuild findings. v26.10.0 · Oct 2026 · source · release history
  • Ships a Helm chart at charts/sbomify in the repository, deploying Caddy, gunicorn/uvicorn, Dramatiq workers, a cron scheduler, and a pre-traffic migration job; supports workload identity on AWS and GCP to eliminate static object-storage credentials. announced · Sep 2026 · source · release history
  • Adds a WORKDIR /workspace to the container image so docker run -v "$PWD:/workspace" … ghcr.io/sbomify/sbomify-action:v26.9.0 is a complete invocation with no -w flag required. announced · Sep 2026 · source · release history

command line

  • --progress-interval — Seconds between progress lines (default: 5). 0 prints one per batch. v26.10.0 · Oct 2026 · command-line history
  • --older-than-days v26.10.0 · Oct 2026 · command-line history
  • --sbom-batch-size — SBOMs whose runs are decided together (default 200). v26.10.0 · Oct 2026 · command-line history
  • --missing-only — Skip runs that already have rows. A run that projects nothing has none to find, so it is re-read on every pass; see the note in the module docstring. v26.9.0 · Sep 2026 · command-line history
  • --batch-size — Rows to read and update per batch (default: 500). v26.7.1 · Jul 2026 · command-line history
  • --limit — Process at most N candidates. v26.7.0 · Jul 2026 · command-line history
Custom domain and branding for Trust Center shipped Allows workspaces to configure custom domains (CNAME) to brand their public-facing Trust Center pages. 8 releases · 1 other source · first seen Oct 2025

release 8 total

  • Custom domains now require outbound HTTPS from workers; rotating SECRET_KEY requires domains to be re-verified. v26.10.0 · Oct 2026 · source · release history
  • Deprecated endpoint PUT /api/v1/workspaces/{team_key}/branding (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint PUT /api/v1/workspaces/{team_key}/domain (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint PATCH /api/v1/workspaces/{team_key}/domain (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint DELETE /api/v1/workspaces/{team_key}/domain (still works) 26.8.0 · Sep 2026 · source · release history
  • Adds CNAME-based custom domain support for public Trust Center pages v0.20 · Dec 2025 · source · release history

example

  • Configure a custom domain like trust.example.com for your workspace's public Trust Center pages. Navigate to Workspace Settings > Branding, enter your CNAME in the Custom Domain field, and follow the DNS validation steps provided in the UI. v0.20 · Dec 2025 · source
Vendor security advisories authoring shipped Authors vendor security advisories with CVSS vectors, version ranges, product associations, and a timestamped timeline for publication to external portals. 7 releases · first seen Aug 2026

release 7 total

  • New endpoint POST /api/v1/advisories/{advisory_id}/products 26.10.0 · Oct 2026 · source · release history
  • New endpoint PATCH /api/v1/advisories/{advisory_id}/statuses/{status_id} 26.10.0 · Oct 2026 · source · release history
  • New endpoint PATCH /api/v1/advisories/{advisory_id}/products/{product_id}/status⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ 26.10.0 · Oct 2026 · source · release history
  • Adds per-product advisory status editing after an advisory is created, bulk delete for advisories, custom ID prefix support for advisories, and Markdown support for advisories. v26.10.0 · Oct 2026 · source · release history
  • PATCH /advisories/{id} now rejects unknown fields with 422. v26.10.0 · Oct 2026 · source · release history
  • Advisories support three visibility states — Private, Public, and Gated — where Gated requires both a workspace-level NDA grant and a link to a product the reader can already access; per-advisory product filtering redacts names the reader is not entitled to see. announced · Aug 2026 · source · release history
Billing and subscription processing shipped Manages subscription events, enforces plan limits, and fetches cached Stripe pricing data to support billing workflows. 6 releases · 1 other source · first seen May 2025

release

  • The first Stripe sync moves ended paid plans to Community, making their private products and components public. v26.10.0 · Oct 2026 · source · release history
  • Deprecated endpoint GET /api/v1/billing/plans/ (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/billing/usage/ (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint POST /api/v1/billing/change-plan/ (still works) 26.8.0 · Sep 2026 · source · release history
  • Add billing services for fetching Stripe prices with caching via get_stripe_prices() v0.9.0 · May 2025 · source · release history
  • Introduce billing configuration module with is_billing_enabled() and get_unlimited_plan_limits() helpers v0.9.0 · May 2025 · source · release history

example

  • Check if billing is active before processing a subscription event. from sbomify.billing.config import is_billing_enabled if is_billing_enabled(): limit = get_unlimited_plan_limits() v0.9.0 · May 2025 · source
Local development environment bootstrap shipped Automates the setup and configuration of Keycloak and other local dependencies to eliminate manual development environment configuration steps. 3 releases · 2 other sources · first seen May 2025

release

  • Adds REDIS_CACHE_MAX_CONNECTIONS and REDIS_CACHE_POOL_TIMEOUT environment variables to tune Redis connection pooling, LOG_MAX_SIZE and LOG_MAX_FILE environment variables for log rotation control, and KEYCLOAK_PUBLIC_URL environment variable for self-hosted Keycloak configuration. v26.10.0 · Oct 2026 · source · release history
  • Adds bin/keycloak-bootstrap.sh script to automatically manage and bootstrap Keycloak in development environments. v0.7.0 · May 2025 · source · release history
  • Introduces new environment variables in .env.example for controlling Keycloak configuration without manual setup. v0.7.0 · May 2025 · source · release history

example

  • Tune Redis connection pool limits to support higher concurrency in a self-hosted instance. REDIS_CACHE_MAX_CONNECTIONS=50 REDIS_CACHE_POOL_TIMEOUT=10 v26.10.0 · Oct 2026 · source
  • Bootstrap a local Keycloak instance for development without manual setup steps. ./bin/keycloak-bootstrap.sh v0.7.0 · May 2025 · source
Per-artifact analytics shipped Tracks VEX, CBOM, and HBOM events per artifact to provide usage analytics across the workspace inventory. 4 releases · 1 other source · first seen May 2025

release

  • Audit trail paths under the working directory are now recorded relative to it (e.g. src/requirements.txt) rather than as absolute paths exposing the build machine's directory layout and username. announced · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/notifications/ (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint POST /api/v1/notifications/clear/ (still works) 26.8.0 · Sep 2026 · source · release history
  • Adds PostHog per-artifact analytics tracking VEX, CBOM, and HBOM uploads, downloads, deletions, and release pulls. v26.7.1 · Jul 2026 · source · release history

example

  • Populate the database with dummy data for local development or integration testing. python manage.py create_test_sbom_environment v0.10.0 · May 2025 · source
CI/CD publishing integration shipped Generates scoped, short-lived publishing tokens and copy-paste pipeline commands for direct artifact submission. 3 releases · first seen Aug 2026

Also counts toward: CI/CD pipeline integration

release

  • On Jenkins, reads CHANGE_BRANCH in preference to BRANCH_NAME for PR builds; on Travis CI reads TRAVIS_PULL_REQUEST_BRANCH in preference to TRAVIS_BRANCH, so the SBOM ref is the source branch rather than the merge target or job name. announced · Sep 2026 · source · release history
  • Adds native CI platform support for TeamCity (teamcity, priority 40), Jenkins (jenkins, priority 50), CircleCI (circleci, priority 60), and Travis CI (travis, priority 70) via a new CIPlatform abstraction, enabling accurate VCS provenance (branch, repo URL, ref) in SBOMs produced on those systems. announced · Sep 2026 · source · release history
  • CI/CD integration dialog generates a single copy-paste command; clicking to include a token mints one scoped to publishing only, with a 7-day TTL and a descriptive name, minted on click rather than on dialog open. announced · Aug 2026 · source · release history
Custom data exports shipped Exports workspace, product, release, or component scoped datasets for inventory, licenses, findings, and vulnerabilities using live dashboard data and VEX suppressions. 3 releases · first seen Aug 2026

Also counts toward: CSV data export

release

  • Deprecated endpoint GET /api/v1/exports/vulnerabilities.csv (still works) 26.8.0 · Sep 2026 · source · release history
  • Deprecated endpoint GET /api/v1/exports/findings.csv (still works) 26.8.0 · Sep 2026 · source · release history
  • Four new CSV exports covering inventory, licenses, findings, and vulnerabilities, scoped to workspace, product, release, or component, reading the same latest-per-component data and live VEX suppressions as the dashboard. announced · Aug 2026 · source · release history
Real-time UI updates shipped Delivers live interface updates to users over a WebSocket connection via the ws/user/ route. 2 releases · first seen Oct 2026

release

  • Adds live UI updates over WebSocket via the new ws/user/ route. v26.10.0 · Oct 2026 · source · release history
  • The new ws/user/ WebSocket route must be forwarded in reverse proxy configuration. v26.10.0 · Oct 2026 · source · release history
Automated security.txt generation shipped Generates standardized security.txt files with dedicated CSIRT contact and report slots, optional CSAF pointers, and configurable expiration dates. 2 releases · first seen Aug 2026

release

  • Deprecated endpoint GET /api/v1/access-requests/pending (still works) 26.8.0 · Sep 2026 · source · release history
  • security.txt generation follows BSI TR-03183-3 shape with separate CSIRT contact and report-page slots, an optional CSAF pointer, and an Expires field clamped to at most one year; shares data with the CRA wizard. announced · Aug 2026 · source · release history
AI agent human-review gates shipped Requires human approval before AI agent changes to published advisories go live, and allows agent tokens to queue triage decisions for human review. 1 release · first seen Nov 2026

release

  • Adds human-review gates for AI agent actions: changes an AI agent makes to a published advisory now require human approval before they go live, and agent tokens can queue triage decisions for human review by submitting with review=true.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v26.11.0 · Nov 2026 · source · release history
Role-based access control shipped Provides workspace roles with scoped permissions, including an Operator role that grants read access and finding triage rights without write permissions. 1 release · first seen Oct 2026

Also counts toward: Role-based access control

release

  • Adds an Operator role that grants read access to the entire workspace and the ability to triage findings, without permission to change anything else. v26.10.0 · Oct 2026 · source · release history
SAST integration shipped Runs static analysis as part of the CI pipeline to surface code-level findings during development. 1 release · first seen Jul 2026

Also counts toward: CI/CD pipeline integration

release

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for sbomify, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail sbomify puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

44 entries

  1. November 20261
  2. October 20264
  3. September 20269
  4. August 20265
  5. July 20262
  6. June 20261
  7. May 20261
  8. April 20261
  9. February 20262
  10. January 20263
  11. December 20253
  12. October 20251
  13. August 20251
  14. July 20254
  15. June 20252
  16. May 20253
  17. March 20251
    Show

    44 entries

    Project health

    Issue, contributor and maintainer activity in sbomify/sbomify, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 11 +3 vs prior 12 months
    2. Maintainers 3 +3 joined · −1 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 33% of issues opened, last 12 months
    5. Median time to close 7.1 days first maintainer reply 7.1 days
    6. Open backlog 102 of 316 issues ever filed
    1. Issues opened / month 1 · 13 communitymaintainers
    2. Open backlog 102
    3. Contributors / month 4
    4. Commits / month 427
    5. Stars 58
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →