epic: code and supply-chain security hardening #759
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.
Depends on
#428 security: adopt the SDK roots-replacement (SEP-2322) so the wrong-repo write guard survives 2026-07-28 clients
sixfold-space/madtea
#434 release: sign GoReleaser's tap/scoop bot commits before routing them through signed repos
sixfold-space/madtea
#501 hooks/tests: the credential clone-URL guard test failed once with no hook change
sixfold-space/madtea
#588 gate: add a credential-gated nancy scan
sixfold-space/madtea
#621 track: x/crypto is in go.mod only for the update signature check, so osv-scanner ignores GO-2026-5932
sixfold-space/madtea
#623 gosec: handle every error
sixfold-space/madtea
#633 gosec: record why six rule classes stay excluded
sixfold-space/madtea
Reference
sixfold-space/madtea#759
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?
This epic gives the open security-labeled hardening work one home and a clear exit. These fixes are not tied to a feature release, and the security label alone does not track their state.
This epic gates no release. Each release cuts on its own criteria. #675 stays the ADR-tooling-break release.
Scope
The work falls in three areas:
Children
Done when
Every child is closed.