You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
/best-practices reads a GitHub project's OpenSSF Scorecard result and, for each check under 10, names the action that raises it and who takes it: property tests for Fuzzing, the two ways to clear old unsigned release assets for Signed-Releases, a ruleset that lacks the approvals code-review.yml expects for Branch-Protection, and the registration for CII-Best-Practices. It finds an existing registration at bestpractices.dev/projects.json?url=, so a project registered before best_practices_project was recorded gets the update prompt and is never registered twice, and the registration prompt looks a project up there first. It fetches gitleaks, checksum-verified and past the dependency cooldown, when it isn't installed, and ends with an ordered list of next steps. (#451, ADR-0153)
Changed
/best-practices answers for the tip of the default branch, the commit Scorecard and bestpractices.dev see, in a temporary worktree when the checkout is elsewhere, and reports evidence that only unmerged commits hold instead of dropping it. (#451, ADR-0153)
ADR-0020's Fuzzing row says the template adds no property tests and what to write, and its Signed-Releases rows name the 14-day backfill limit and the rule never to attest registry packages. (#451, ADR-0020)
Fixed
.template/Test-FileHeaders.ps1 skips the five build/ scripts the template owns, dod.ps1, Update-PublicApi.ps1, Get-TestRuntimes.ps1, Install-Dotnet.ps1 and Update-Baseline.ps1, so a .NET project's file header check passes without a header in a file template updates replace. (#449, ADR-0027)