Standardize README headers, badges, and best-practices evidence - #41
Merged
Conversation
dcondrey
enabled auto-merge
September 2, 2026 02:03
dcondrey
force-pushed
the
docs/repository-standards-20260901
branch
from
September 2, 2026 02:05
f000693 to
bcaeee4
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
1 participant
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.
Summary
Badge convention
Static badges use
flat-squaregeometry and dark-slatelabelColor=20232a. Metadata is blue, standards/affiliations are purple, and support/social badges use recognizable brand colors. CI, CodeQL, OpenSSF, coverage, SLSA, and other stateful badges retain service-generated state colors.The evidence file is intentionally conservative: criteria not provable from tracked files or repository settings remain unknown or unmet rather than being overstated.