SBOM and dependency policy
Published release SBOM
Browse the release SBOM: components, versions, and licenses →
Download the Ubuntu amd64 CycloneDX SBOM (JSON)
for tools. The browsable page is generated from this file in the same pipeline.
Pages also publishes sbom/badge.json, a shields.io endpoint
that the README’s SBOM badge reads to show the format and component count.
This CycloneDX 1.6 inventory comes from the package job, after the release version is assigned and the executable is built. It describes the Cargo dependencies of the Ubuntu 26.04 amd64 desktop binary, not the broader check job’s inventory.
- Latest installer and build details
- Release identity: version and source commit
- SHA-256 checksums for the installer, SBOM, and release identity
The SBOM records transitive dependencies, declared license expressions, package
URLs, registry archive checksums, and dependency relationships. Its metadata
records the target, desktop features, lockfile checksum, and the built
executable’s SHA-256. Build-only dependencies are retained with excluded scope,
rather than marked as runtime requirements.
The executable hash in the SBOM identifies the binary inside the .deb.
It is not the hash of the .deb archive; the downloads page and SHA256SUMS
provide that separately. Checksums detect mismatches but do not authenticate the
publisher. The APT repository’s signature does that for packages installed through APT.
Only the latest successful Pages publication is retained. Its book, coverage, SBOM, vulnerability scan, and installer come from the same pipeline. macOS SBOMs remain available with their opt-in CI job’s artifacts; this site does not imply a macOS release.
License policy
The checked-in dependency_policy.toml
checks dependencies across all supported desktop targets, including build and
test dependencies. It permits the existing approved licenses and has exact-version
exceptions for existing MPL-2.0 crates. New licenses and MPL upgrades require review.
GPL, AGPL, LGPL, and EPL are not approved; dual-licensed crates can pass under an
approved alternative.
A component’s declared license expression in the SBOM is not a statement that every offered alternative is approved or selected. The application’s own license is still undecided; the dependency policy does not grant one.
RustSec
cargo-deny checks the dependency graph against the
RustSec advisory database.
Known vulnerabilities, unsoundness, and yanked releases block packaging.
Unmaintained-crate advisories are visible warnings, not ignored findings.
This checks published advisories; it does not prove an absence of vulnerabilities.
Maintenance follow-up
The November 2026 dependency review found seven maintenance advisories. A
compatible lockfile refresh removes the EXR → pulp → paste path, and Notify
8 removes the application’s notify-types 1 → instant path, but the remaining
consumers below still require all seven crates:
| Crate | Remaining consumers | Maintained replacement / next step |
|---|---|---|
instant | GPUI Base and GPUI Component | Upstream migration to web-time or native std::time. |
paste | GPUI Component | Upstream migration to pastey or equivalent macros. |
rustybuzz | GPUI and Mermaid’s SVG/font stack | Migrate consumers to harfrust and newer usvg/resvg. |
ttf-parser | GPUI, Mermaid, and font dependencies | Migrate consumers to skrifa and newer font/SVG libraries. |
zbus_names, zvariant, zvariant_derive | Linux portal, keyring, and accessibility dependencies | Coordinated migration to zbus 6, which incorporates these standalone crates. |
GPUI’s published snapshot and GPUI Component must remain version-matched. Recheck new releases of GPUI, GPUI Component, Mermaid, and the Linux integration stack during dependency updates; do not substitute incompatible transitive versions, disable text rendering/accessibility, or suppress advisories merely to clear the warnings. These findings are maintenance risks, not known vulnerabilities, and remain visible in CI until their consumers migrate.
Vulnerability scan
Browse the latest vulnerability scan → · Grype JSON report · RustSec JSON report
After packaging, a pinned Grype scans the published
release SBOM above, and the same job records every RustSec finding from cargo-deny. Pages
publishes both on one report page, with vulnerabilities/badge.json for the README badge.
The badge lists Grype’s severity counts (or “none found”) followed by RustSec findings by kind,
for example “none found, 7 unmaintained”. A vulnerability reported by both counts once.
RustSec also records crates that are unmaintained, unsound, or yanked. These are not vulnerabilities, so the GitHub Advisory Database and NVD do not list them and Grype can be clean while cargo-deny warns. The report shows them so maintenance risks are visible outside the CI log; unmaintained crates stay warnings and do not fail the pipeline.
Grype is a second, independent opinion beside RustSec. Its database combines the GitHub Advisory Database (which imports most RustSec advisories and adds its own) with NVD data, so findings carry CVE aliases, CVSS-based severities, and CWE weakness types. It checks exactly the crate versions recorded in the shipped SBOM.
cargo-deny (RustSec) | Grype | |
|---|---|---|
| Input | Cargo.lock graph, all supported targets, incl. build/dev dependencies | Release SBOM (Ubuntu amd64 desktop binary) |
| Data | RustSec | GitHub Advisory Database, NVD, EPSS |
| Vulnerabilities | Yes, fails CI | Yes, reported only |
| Unsound / yanked / unmaintained | Fails / fails / warns; all shown in the report | Not checked |
| Licenses, sources, duplicate crates | Checked by policy | Not checked |
| Severity, CVE, CWE details | Advisory text | Yes |
The scan reports findings without failing the pipeline; the RustSec check in the supply-chain
job remains the release gate. A scan failure (for example, an unavailable or outdated database,
or cargo-deny output that ends early) blocks publication rather than showing a stale or falsely
clean badge. The RustSec part covers the whole dependency graph that cargo-deny checks, which
is wider than the release SBOM. The badge reflects publication time, not
advisories disclosed afterwards. Like the SBOM, the scan covers Cargo crates only: bundled
SQLite appears only as libsqlite3-sys, so SQLite CVEs are not matched by version, and
Ubuntu’s system libraries are updated by the distribution, not this scan.
Inventory limits and local checks
This is a Cargo dependency SBOM, not a complete inventory of bundled native
sources, system libraries, the Rust standard library, fonts, icons, or build tools.
Bundled SQLite appears through libsqlite3-sys, not as a separate SQLite component.
The SBOM does not replace required third-party notices or a license review.
See Development → Dependency licenses, RustSec, and SBOMs for pinned tools, local commands, policy details, and generation safeguards. Download links are populated by Pages publication, not by an ordinary local mdBook build.