No component the team refuses is in the artifact
supply-chain/disallowed-components@v1
No component the bill of materials lists is one the team has decided it will not ship, whatever brought it in.
| Id | supply-chain/disallowed-components |
| Version | v1 |
| Category | supply-chain |
| Default severity | error |
| Interpreter | python3 |
| Timeout | 30 seconds |
| Violations tolerated | 0 |
| Collects | sbom |
Collectors
This guardrail gathers nothing itself. It depends on the collectors below, which the CLI runs once per build before any check, and reads what they found out of GUARDRAIL_FACTS. A collector that collects nothing skips this guardrail rather than failing it.
| Collector | Gathers | Inputs it is given |
|---|---|---|
sbom | The components a build says it ships, read from the bill of materials it already wrote, whether that is CycloneDX or SPDX, JSON, XML or tag-value, normalized into one list carrying the licence each component names. | none |
The inputs above are this guardrail's own, passed straight through. Configuring one in buildnote.json changes what is collected, and two guardrails configured the same way share the one collection.
Configuration
{
"guardrails": {
"failOn": "error",
"comment": true,
"checks": [
{
"use": "supply-chain/disallowed-components@v1",
"severity": "error",
"with": {
"components": ""
},
"exemptions": []
}
]
}
}Inputs
| Input | Description | Default | Environment variable |
|---|---|---|---|
components | Comma separated component names or package URL fragments that are a violation, such as event-stream,pkg:npm/left-pad. Empty means the team has named none and the guardrail skips. | `` | GUARDRAIL_INPUT_COMPONENTS |
How to fix
Remove the components named in the violations. One that arrived transitively is removed by excluding it where it was pulled in, and by naming the replacement explicitly:
implementation("com.acme:service") {
exclude(group = "org.abandoned", module = "parser")
}
implementation("org.maintained:parser:2.1.0")This guardrail is the list the team keeps of what it has already decided against: a package that was withdrawn, one that was taken over, one an incident was traced to. Without it the decision lives in the memory of whoever made it.
More in supply-chain
supply-chain/components-licensed. Enough of the components the bill of materials lists name a licence that the inventory can answer what the artifact may be distributed under.supply-chain/disallowed-licenses. No component the bill of materials lists is licensed under one of the licences the team has decided it will not ship.supply-chain/no-critical-vulnerabilities. No dependency the build takes on carries an open finding at or above the severity the team gates on.supply-chain/sbom-present. An SBOM was produced for this build, so the components that went into the artifact are recorded rather than reconstructed later.supply-chain/sbom-standard-format. The bill of materials is written in a format anything else can read, and it declares which version of that format it is.