BACKWORKS

WORK · I

SUPPLY-CHAIN SECURITY · 0.3.0

SUPPLYGUARD

An SBOM security workspace that validates component inventory, evaluates profile quality, and surfaces known vulnerabilities without mixing mutable findings into the source document.

SOURCE

01

ANALYSIS MODEL

FROM INVENTORY TO EVIDENCE

  1. IINGEST

    CycloneDX JSON 1.6 or 1.7

  2. IIVALIDATE

    Schema and BSI profile rules

  3. IIIENRICH

    OSV or deterministic demo data

  4. IVDELIVER

    Web report, JSON, or SARIF 2.1.0

02

DETERMINISTIC OFFLINE PROVIDER

BUNDLED DEMO SPECIMEN

demo-shop.cdx.json

ANALYSIS COMPLETE
$supplyguard demo-shop.cdx.json --provider demo --format json
COMPLIANCE
100
RISK
48
SCANNED
4 / 4
VULNERABILITIES
2

CRITICAL · 1HIGH · 1

VALIDATION ERRORS0

DATA COMPLETEYES

Current result from the repository's bundled CycloneDX demo and deterministic provider. No network request is required.

03

IMPLEMENTED SURFACE

CORE CAPABILITIES

01

PROFILE-AWARE VALIDATION

Machine-readable checks align CycloneDX fields with BSI TR-03183-2 v2.1.0 while keeping unsupported or ambiguous cases explicit.

02

BOUNDED ANALYSIS

Upload size, JSON depth, component traversal, OSV pages, and vulnerability details are bounded and reported instead of silently truncated.

03

CI POLICY GATES

The database-free CLI emits stable exit codes and can fail on severity, validation errors, or incomplete vulnerability data.

04

SEPARATE EVIDENCE

Inventory remains inside the SBOM. Mutable vulnerability findings stay in the analysis report and can be exported as JSON or SARIF.

04

SYSTEM SHAPE

TWO SURFACES, ONE PIPELINE

WEBSVELTEKIT
CLI / CIPYTHON
ANALYSIS SERVICEFASTAPI · VALIDATOR · PROVIDERS
OUTPUTREPORT · JSON · SARIF

05

DECLARED LIMITS

BOUNDARIES

  1. 01

    Profile-aligned technical checks are not official BSI certification.

  2. 02

    SPDX is outside the current scope; the implemented input is CycloneDX JSON.

  3. 03

    Live OSV matching requires valid package URLs and discloses them to OSV.

  4. 04

    A public multi-tenant deployment still requires identity, authorization, retention, and edge abuse controls.

SOURCE · DOCUMENTATION · MIT

INSPECT THE IMPLEMENTATION