Audit software supply chain integrity

What it's for

Reconciles what is actually deployed against SBOM freshness, pinning, attestation, support horizon and license policy — without treating a repository's README as provenance.

Turns SBOM coverage into an executive-grade integrity control that reveals exactly which unique business applications depend on stale, unattested, unsupported, license-restricted or unresolved runtime components.

What you give it

Inputs split into evidence read from your connected systems, calibration your team owns, and numerical controls that affect precision but never the result's meaning.

{
  "applications": [
    {
      "evidence_verified": true,
      "id": "checkout",
      "root_component_ids": [
        "checkout-service"
      ],
      "value_at_risk": 200
    }
  ],
  "as_of_period": 12,
  "components": [
    {
      "artifact_attested": true,
      "evidence_verified": true,
      "id": "checkout-service",
      "license_status": "approved",
      "resolved": true,
      "risk_class": "internal",
      "sbom_as_of_period": 12,
      "source_pinned": true,
      "support_end_period": 24,
      "version": "1.0.0"
    },
    {
      "artifact_attested": true,
      "evidence_verified": true,
      "id": "parser",
      "license_status": "approved",
      "resolved": true,
      "risk_class": "third-party-runtime",
      "sbom_as_of_period": 12,
      "source_pinned": true,
      "support_end_period": 24,
      "version": "3.2.1"
    }
  ],
  "dependency_edges": [
    {
      "child_component_id": "parser",
      "evidence_verified": true,
      "id": "checkout-parser",
      "parent_component_id": "checkout-service",

What you get back

This is the actual output of running the example above — computed by the same function the platform calls, not an illustration.

{
  "application_diagnostics": [
    {
      "application_id": "checkout",
      "integrity_gap_component_count": 0,
      "integrity_gap_component_ids": [],
      "reachable_component_count": 2,
      "value_at_risk": 200,
      "value_exposed_to_integrity_gap": false
    }
  ],
  "assumptions": [
    "The graph is a point-in-time runtime SBOM resolved to deployed artifacts. Build/test-only edges are retained as evidence but do not create runtime application exposure; every application value is a unique finance-governed source counted at most once.",
    "Attestation, pinning, license, support and vulnerability states come from authoritative scanners, artifact registries, legal/procurement and security review. Repository text, package popularity, maintainer identity or an LLM guess is not provenance or exploitability evidence.",
    "A failed gate identifies supply-chain evidence or policy work. It does not prove compromise, malicious intent, maintainer or developer fault, legal infringement, or a loss amount and does not authorize blocking, investigation, disclosure, employment or vendor action."
  ],
  "component_diagnostics": [
    {
      "component_id": "checkout-service",
      "fix_available_finding_count": 0,
      "gap_types": [],
      "license_status": "approved",
      "open_or_accepted_finding_count": 0,
      "reachable_application_count": 1,
      "sbom_as_of_period": 12,
      "support_end_period": 24,
      "version": "1.0.0"
    },
    {
      "component_id": "parser",
      "fix_available_finding_count": 0,
      "gap_types": [],
      "license_status": "approved",
      "open_or_accepted_finding_count": 0,
      "reachable_application_count": 1,
      "sbom_as_of_period": 12,
      "support_end_period": 24,
      "version": "3.2.1"
    }
  ],
  "configuration": {
    "application_value_rule": "count_each_application_value_once",
    "as_of_period": 12,
    "dependency_scope": "runtime_reachable_edges_only",

How it works

Constrained optimization — Pick the best feasible option under real limits — budget, headcount, dependencies, capacity — rather than ranking a list and hoping it fits.

1. 1 Freeze application roots, deployed component versions, runtime dependency edges, vulnerability dispositions and authoritative provenance/license/support evidence at one as-of period.
2. 2 Traverse each application graph, retain cycles and duplicate pairs as integrity findings, and separate reachable deployed components from orphan inventory rather than counting every manifest row as exposure.
3. 3 Gate value once per unique application on resolution, pinning, attestation, freshness, support, license, exploitability and evidence coverage; return exact component/application diagnostics for reconciliation.

Before you trust it

Every tool in the catalog ships with the conditions under which its answer is meaningful — and the conditions under which it should abstain instead of guessing.

Calibrating it to your org

Calibration workflow

1. 1 Define the management decision, target outcome, aggregate unit, privacy boundary, cadence, and prediction/intervention horizon for this organization.
2. 2 Build a tenant-scoped historical cohort using only information available before each prediction or decision; preserve zero periods, censoring, assignment probabilities, and unresolved outcomes when the method requires them.
3. 3 Estimate statistical parameters on training history, but obtain costs, utilities, risk tolerance, practical-effect thresholds, capacity, and policy constraints from accountable decision owners.
4. 4 Validate on later time windows or held-out aggregate units at the deployment grain, against a simple baseline and the function-specific validation strategy.
5. 5 Deploy only if the returned decision clears evidence, overlap, calibration, robustness, and guardrail checks; warning, unsupported, schema-gap, and fallback decisions are abstentions.
6. 6 Monitor realized outcomes, data drift, coverage, and decision regret; recalibrate at a governed cadence or after a detected regime/definition change, never merely because a stakeholder dislikes the result.

Call it from your AI

You don't wire up 388 tools in your MCP client. The GitRevio MCP server exposes 18 tools, three of which let an agent search the catalog, read a tool's schema, and run it — so the assistant finds this one on its own.

gitrevio_capabilities_search
  { "q": "audit the deployed runtime software supply" }
  → finds "audit_software_supply_chain_integrity"

gitrevio_capability_describe
  { "capability_id": "audit_software_supply_chain_integrity" }
  → returns the input schema and agent guidance shown on this page

gitrevio_capability_run
  { "capability_id": "audit_software_supply_chain_integrity", "arguments": { ... } }
  → returns the result shown above

Works in Claude Desktop, Claude Code, Cursor, Cline, Continue.dev, Goose and Aider. See the MCP server.

Related tools

See every tool in Security, access & compliance →