gate: add a credential-gated nancy scan #588
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#759 epic: code and supply-chain security hardening
sixfold-space/madtea
Reference
sixfold-space/madtea#588
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
nancy's OSS Index backend now requires credentials. An anonymous
nancy sleuthreturns 401 Unauthorized. No credential exists in the default environment, and
fork CI cannot hold secrets. I keep nancy but gate it on credential presence.
Its marginal value is the proprietary OSS Index database. Without it, coverage
stays govulncheck plus osv-scanner.
What
Add a heavy-block step to
scripts/gate.sh:OSSINDEX_USERNAMEandOSSINDEX_TOKENare set: rungo list -json -m all | nancy sleuth --no-color; a non-zero exit fails thegate.
"skipped is not a pass" convention for the conformance step. This is an
unavailable external prerequisite, not a suppressed failure.
scripts/setup-dev.sh(record in the pin comment that upstreamis archived) and the ci.yml install step. Document the credential env vars as
secrets in the ci.yml header and docs/contributing/ci.md. Add the CLAUDE.md
line.
Acceptance
unaffected.
dependency makes it fail. Prove this once, then revert.