chore: expand .bestpractices.json with repo-verified proposals#92
Merged
Conversation
Add proposed answers for every passing-level criterion that is objectively true from the repository, so the next "Save 🤖" on bestpractices.dev proposes them for acceptance: - Met: documentation (basics/interface), english, maintained, repo_interim, version_unique/semver/tags, report_archive, vulnerability_report_private, build_floss_tools, test_most/policy, tests_are_added/documented, warnings/_fixed/_strict, delivery_unsigned, vulnerabilities_fixed_60_days, vulnerabilities_critical_fixed, no_leaked_credentials, static_analysis_common_vulnerabilities/fixed/often, dynamic_analysis_fixed. - N/A: all crypto_* (the tool performs no cryptography), release_notes_vulns (none fixed yet), dynamic_analysis_unsafe (Go is memory-safe). URLs included where met_url_required. Not auto-asserted (left for the maintainer to answer): know_secure_design, know_common_errors, report_responses, enhancement_responses, vulnerability_report_response. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…response Met Add explicit acknowledgement (7 days) and initial-assessment (14 days) commitments to SECURITY.md, satisfying the OpenSSF Best Practices vulnerability_report_response criterion, and propose it as Met. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Follow-up to #90 / #91. Adds proposed answers for every passing-level criterion that is objectively true from the repository, so the next Save 🤖 on bestpractices.dev surfaces them for acceptance. All 53 keys verified against the live project schema (
projects/13027.json); noN/Aproposed where the criterion forbids it.Met (repo-verifiable): documentation_basics/interface, english, maintained, repo_interim, version_unique/semver/tags, report_archive, vulnerability_report_private, build_floss_tools, test_most/policy, tests_are_added/documented, warnings/_fixed/_strict, delivery_unsigned, vulnerabilities_fixed_60_days, vulnerabilities_critical_fixed, no_leaked_credentials, static_analysis_common_vulnerabilities/fixed/often, dynamic_analysis_fixed.
N/A: all
crypto_*(the tool performs no cryptography and makes no network calls),release_notes_vulns(no vulnerabilities fixed yet),dynamic_analysis_unsafe(Go is memory-safe).Deliberately not auto-asserted — these are maintainer attestations/behavioral claims to answer by hand:
know_secure_design,know_common_errors,report_responses,enhancement_responses,vulnerability_report_response.🤖 Generated with Claude Code