Skip to content

chore: expand .bestpractices.json with repo-verified proposals#92

Merged
peczenyj merged 2 commits into
develfrom
chore/bestpractices-expand
May 29, 2026
Merged

chore: expand .bestpractices.json with repo-verified proposals#92
peczenyj merged 2 commits into
develfrom
chore/bestpractices-expand

Conversation

@peczenyj
Copy link
Copy Markdown
Owner

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); no N/A proposed 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.

Reminder: the file only proposes. After merge, log into bestpractices.dev/projects/13027, click Save (and continue) 🤖 per section, and accept the proposals.

🤖 Generated with Claude Code

peczenyj and others added 2 commits May 29, 2026 15:05
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>
@peczenyj peczenyj self-assigned this May 29, 2026
@peczenyj peczenyj merged commit 270489d into devel May 29, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant