OpenSSF Silver evidence still cites the v0.13.0 release
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, rust, yaml
- Domain
- documentation, release
Research direction
Start with release/openssf-best-practices-silver.yaml and inspect the current release assets against the two stated criteria: repeatable canonical Linux amd64 binaries and image layers, and a keyless signed SHA256SUMS closure with attestations. Re-read each explanation against the selected release, update verified_at, then check bestpractices.dev and update it if its answers cite the same tag. Done when both sources reflect evidence supported by current release assets.
Written by the indexing model from the issue text.
Description
release/openssf-best-practices-silver.yaml cites https://github.com/registrystack/registry-stack/releases/tag/v0.13.0 as evidence for build_repeatable (line 17) and signed_releases (line 26), with verified_at: "2026-07-25". The workspace is now at 0.42.0, and many releases since then use a different release shape.
Done when:
- both criteria cite a current release whose assets show the claim (repeatable canonical Linux amd64 binaries and image layers; a keyless signed
SHA256SUMSclosure with attestations); - each
explanationis re-read against that release; verified_atis updated.
The project page at bestpractices.dev is authoritative. Update it in the same pass if its answers cite the same tag.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 10h 47m
- Merged PRs (30d)
- 241
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from registrystack/registry-stack
-
area:casework criticality:p3
Difficulty 1/5 Under an hour Newbie friendliness 94/100
registrystack/registry-stack#2084 ·
Maintainers usually reply within 1 day
-
area:breg bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
registrystack/registry-stack#2046 ·
Maintainers usually reply within 1 day
-
area:casework bug criticality:p3 rust
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
registrystack/registry-stack#1934 ·
Maintainers usually reply within 1 day
-
area:release area:scheduling bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
registrystack/registry-stack#1909 ·
Maintainers usually reply within 1 day
-
area:release bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
registrystack/registry-stack#1874 ·
Maintainers usually reply within 1 day
All issues in registrystack/registry-stack
Similar issues
-
founders_reward panics on a configured Testnet when the slow-start subsidy is not a multiple of 5Openexternal-contribution
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ZcashFoundation/zebra#11792 ·
Maintainers usually reply within 1 day
-
area/cli bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
bherbruck/solvecraft#2167 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bitcoindevkit/bdk-cli#357 ·
Maintainers usually reply within 3 days