Conversation
…schema
Strip the custom group structure (status/evidence/audit) — bestpractices.dev
autofill ignores it — and replace with the canonical flat per-criterion
key/value schema from coreinfrastructure/best-practices-badge `criteria.yml`
'0' block (passing badge): 43 MUST + 10 SHOULD + 14 SUGGESTED, each with
`<key>_status` ("Met" / "Unmet" / "N/A" / "?") and `<key>_justification`,
plus `<key>_url` for the eight criteria where upstream sets
`met_url_required: true`.
Per-criterion evidence reuses what shipped in PR #1 (RAN-54): security.yml
gates (Trivy / Semgrep / PSScriptAnalyzer / Gitleaks / jscpd / SBOM),
scorecard.yml, dependabot.yml, signed-commit branch protection,
SECURITY.md disclosure SLA, engineering-standards.md quality gates.
Honest N/A statuses on `na_allowed: true` MUSTs where the criterion does
not apply to a single-script PowerShell tool: crypto_* (project does not
use cryptography), build_* (no compile/build step — .ps1 is the
deliverable), release_notes / release_notes_vulns (no tagged release
flow yet — head-of-main delivery via `git clone`),
dynamic_analysis_fixed (no dynamic analysis tool integrated; PowerShell
on .NET is memory-safe so valgrind/ASAN-class tools do not apply).
This unblocks bestpractices.dev autofill on the project edit page for
project 12647 — board admin OAuth login still required to flip the
badge to passing.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
This was referenced Apr 26, 2026
aksOps
added a commit
that referenced
this pull request
Apr 26, 2026
…ersioning evidence (#8) CHANGELOG.md - [Unreleased] → [v0.1.0] - 2026-04-26 with full Added / Changed / Fixed / Security subsections covering PR #1 (RAN-54 baseline + Scorecard hardening), PR #3 (RAN-59 canonical-schema rewrite), PRs #4/#5 (RAN-64 CHANGELOG + docs/ index), PR #6 (5 SUGGESTED criteria flips), PR #7 (CONTRIBUTING.md + conventional-URL retargets). - Fresh empty [Unreleased] section opened at top per Keep-a-Changelog 1.1.0. - Link refs now point at compare/v0.1.0...HEAD and releases/tag/v0.1.0. .bestpractices.json - version_unique_url + release_notes_vulns_url added (both pointing at the v0.1.0 GitHub Release) so the bestpractices.dev autofill bot has a concrete URL to verify alongside _status: Met. - 5 versioning justifications refreshed to cite the concrete v0.1.0 tag instead of forward-looking commitments: version_unique, version_semver, version_tags, release_notes, release_notes_vulns. These are the criteria the autofill bot verifies by checking actual GitHub Releases / git tags exist. Once the v0.1.0 signed tag + GitHub Release land post-merge, autofill should flip release_notes to Met (currently Unmet pending evidence) and the 4 SUGGESTED versioning criteria stay Met with concrete tag-backed URLs. Co-authored-by: Paperclip <noreply@paperclip.ing>
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
Replaces the custom
status/evidence/auditgroup structure (whichbestpractices.devautofill ignores) with the canonical flat per-criterion key/value schema from upstreamcoreinfrastructure/best-practices-badgecriteria.yml'0'block (passing badge): 43 MUST + 10 SHOULD + 14 SUGGESTED = 67 criteria, each populated with<key>_status+<key>_justification, plus<key>_urlfor the eight criteria where upstream setsmet_url_required: true.This unblocks the bestpractices.dev autofill so the board does not have to hand-type 67 criterion answers when flipping project 12647 to
passing.Status distribution
Honest N/A on
na_allowed: trueMUSTsThe 10 N/A MUST statuses are upstream-allowed (
na_allowed: trueincriteria.yml) and reflect honest non-applicability for a single-script PowerShell desktop tool — board reviewer can confirm each on the autofilled form:crypto_published,crypto_floss,crypto_keylength,crypto_working,crypto_password_storage,crypto_random— snipIT does not implement or invoke cryptography.build— snipIT is a single.ps1;pwsh -NoProfile -File ./SnipIT.ps1is the run path; the.ps1is the deliverable.release_notes,release_notes_vulns— head-of-main delivery viagit clone; no tagged-release flow today (ScorecardPackagingis documented as a known not-a-pass inCLAUDE.mduntil tagged releases land).dynamic_analysis_fixed— no dynamic-analysis tool integrated; PowerShell on .NET is memory-safe so the criterion's targets (valgrind / ASAN / MSAN) do not apply.Evidence sources reused from PR #1 (RAN-54)
.github/workflows/security.yml— Trivy / Semgrep (p/security-audit+p/owasp-top-ten) / PSScriptAnalyzer (Error severity gate) / Gitleaks (full git history) / jscpd /anchore/sbom-action.github/workflows/scorecard.yml,.github/workflows/test.yml,.github/dependabot.ymlSECURITY.md— private GHSA reporting + email + 72h ack / 7d triage / 90d disclosure SLAshared/runbooks/engineering-standards.md§1 (quality gates), §3 (branch/commit/PR rules), §4 (testing tiers), §5 (security)scripts/setup-git-signed.sh— signed-commit setup for branch protection onmainLICENSE(MIT, Amit Kumar)Test plan
python3 -c "import json; json.load(open('.bestpractices.json'))")criteria.yml'0'block (no missing, no extra) — verified programmaticallymet_url_required: truehas a<key>_urlfieldN/Astatus used on a criterion where upstreamna_allowedis false<key>_justificationstringstest,parse,trivy,semgrep,psscriptanalyzer,gitleaks,jscpd,sbom,scorecardall green on this PRpassing🤖 Generated with Claude Code