Repository navigation
Silver badge held; and two gold criteria closed in the tree - #77
Merged
Merged
Conversation
HackTuah
force-pushed
the
docs/silver-badge
branch
from
September 23, 2026 20:18
2e7b6c3 to
426287b
Compare
Awarded 2026-09-23. The badge API reports passing 100%, silver 100%, gold 30%. README and docs/09-standards-register.md say silver where they said passing, and both say what is not met rather than only what is. At silver that is two suggested-tier criteria, a bus factor of two and an accessibility assessment, and one suggestion about signed version tags. Stating the gaps is the point: a sheet with nothing on it survives a spot check less well than one that says where the holes are, and the criteria that remain open are the ones a reviewer will ask about first. The standards register gains a gold row too, at 30% and not held, listing what is met and what is outstanding by name. Three of the outstanding ones need people other than the author in the git history and cannot be bought with code. Signed-off-by: Ayla Croft <aylacroft@proton.me>
Two gold criteria, copyright_per_file and license_per_file, are both MUST and the tree was five files short of each: two HEEx templates and the three Rust files of the desktop shell. None of the five had been noticed by anyone reading the tree, which is the argument for the test rather than for the fix. test/spdx_headers_test.exs takes its population from git ls-files, so a source file added without a header fails by existing rather than by being spotted. It checks for the SPDX tag rather than for a particular line, because SPDX defines the tag and not the comment syntax it sits in, and it also asserts that the licence each file names is the one the project is actually under: a file carrying the right shape of line and the wrong licence is worse than a file carrying none. mix gate exit 0; 579 passed. Signed-off-by: Ayla Croft <aylacroft@proton.me>
HackTuah
force-pushed
the
docs/silver-badge
branch
from
September 23, 2026 20:42
426287b to
7d2ac49
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The badge
Trinity holds the OpenSSF Best Practices silver badge, awarded 2026-09-23. From the badge project's own API:
README.mdanddocs/09-standards-register.mdsay silver where they said passing. Both also say what is not met, because a sheet with nothing on it survives a spot check less well than one that says where the holes are:bus_factorandaccessibility_best_practices(both SHOULD) andversion_tags_signed(SUGGESTED);The register gains a gold row as well, at 30% and not held, naming what is met and what is outstanding. Three of the outstanding ones —
bus_factor,contributors_unassociated,two_person_review— need people other than the author in the git history and cannot be bought with code.Two gold criteria, closed here
copyright_per_fileandlicense_per_fileare both MUST at gold, and the tree was five files short of each: two HEEx templates and the three Rust files of the desktop shell. None of the five had been noticed by anyone reading the tree — which is the argument for a test rather than for a fix.test/spdx_headers_test.exstakes its population fromgit ls-files, so a source file added without a header fails by existing. It checks for the SPDX tag rather than a particular line, since SPDX defines the tag and not the comment syntax it sits in, and it also asserts that the licence each file names is the project's own — a file carrying the right shape of line and the wrong licence is worse than a file carrying none.Evidence
mix gateexit 0; 579 passed, 18 excluded; coverage 80.31%.