Go module checksums are committed
golang/checksums-committed@v1
The module commits go.sum, so every module a build downloads is checked against the checksum the commit recorded.
| Id | golang/checksums-committed |
| Version | v1 |
| Category | golang |
| Default severity | warning |
| Interpreter | python3 |
| Timeout | 30 seconds |
| Violations tolerated | 0 |
| Collects | golang |
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 |
|---|---|---|
golang | The Go build in the project directory: the module it declares, the Go version it asks for, every module of a workspace, the modules it requires directly and indirectly, and the replacements and lock file beside them. | projectDir |
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": "golang/checksums-committed@v1",
"severity": "warning",
"with": {
"projectDir": "."
},
"exemptions": []
}
]
}
}Inputs
| Input | Description | Default | Environment variable |
|---|---|---|---|
projectDir | Directory holding the project, relative to the directory the CLI runs in. | . | GUARDRAIL_INPUT_PROJECTDIR |
How to fix
Commit the checksum file the module tooling writes:
go mod tidy
git add go.sumgo.sum carries the checksum of every module in the graph, so without it nothing verifies that what a build downloaded is what the module authors published and a swapped or rewritten version reaches the binary unnoticed.
More in golang
golang/no-local-replacements. Noreplacedirective redirects a module to a filesystem path, so the build reads only source the checkout carries.golang/toolchain-pinned. The module names the toolchain that compiles it, rather than leaving thegodirective as a floor.golang/version-declared. The module declares the Go version it is built against, and that version is no older than the configured floor.