deps/vulnerability-scan/hugo
Dependencies are scanned for known vulnerabilities
Implements deps/vulnerability-scan for hugo.
| Severity | warning |
| Tiers | 1, 2 |
| Stacks | hugo |
| Scope | each |
| Kind | expr |
| Source | library v0.4.0 |
| Selected by | fleetlint-recommended@v0.4.0 |
Requirement
A Hugo site has no dependency manager of its own: Hugo modules live in go.mod and npm tooling in package.json, and both are checked as their own stacks. Themes added as git submodules are pinned by commit.
Why
A lockfile pins yesterday’s versions; only a scan says which of them are known to be exploitable today.
Applies when
falseCheck
trueFix
Add the stack’s scanner to the audit target (see https://fleetlint.org/stacks/) so check runs it.
Agent instruction: Add the stack’s vulnerability scanner to the audit target of the task runner; use osv-scanner against the lockfile when the stack has no native tool. Do not fix the findings in the same change; list them.
Sources
- https://csrc.nist.gov/pubs/sp/800/218/final (standard, PW.4.4: Verify that acquired commercial, open-source, and all other third-party software components comply with the requirements)
- https://github.com/ossf/scorecard/blob/main/docs/checks.md (standard, Vulnerabilities)
- https://fleetlint.org/baseline/#dependencies
- https://fleetlint.org/stacks/#hugo–static-sites (convention)
Generated by fleetlint docs from catalog v0.4.0.