ossf/scorecard

OpenSSF Scorecard - Security health metrics for Open Source

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 11th, 2026
Created on October 9th, 2020
Open Issues & Pull Requests: 454 (+0)
GitHub issues: Enabled
Number of forks: 721
Total Stargazers: 5,687 (+0)
Total Subscribers: 71 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.0 days
Mean response time: 52.1 days
90th percentile: 114.7 days
Tracked items: 202

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 89% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "kind/docs" is answered fastest, typically in about 10 hours, while "check/Pinned-Dependencies" waits about 4 days. 26% of tracked open issues have had no activity in three months. Only 2% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 137
New in 7 days: 4
Closed in 7 days: 0
Avg open age: 642 days
Stale 30+ days: 109
Stale 90+ days: 78

Recent activity

Opened in 7 days: 3
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 9

Top labels

  • kind/enhancement (91)
  • Stale (86)
  • kind/bug (80)
  • needs triage (35)
  • good first issue (17)
  • kind/docs (16)
  • check/Pinned-Dependencies (11)
  • help wanted (7)

Detailed Description

OpenSSF Scorecard is an automated security assessment tool that evaluates open source projects against a set of heuristics and assigns numerical scores to help maintainers and consumers understand security posture.

Scorecard addresses the challenge of evaluating whether open source dependencies are trustworthy and where projects can strengthen their security practices. It runs a series of automated checks covering important security-related heuristics, scoring each from 0 to 10. The tool generates both an aggregate score and individual check results, allowing users to identify specific areas for improvement. Results can be accessed through multiple interfaces: a GitHub Action for continuous integration, a REST API, a command-line interface, and public badges for display on project pages.

Scorecard suits organizations that need to assess the security posture of their dependencies or that want to measure their own projects against security best practices. It works well for teams establishing security baselines or policies that require certain behaviors from dependencies. The tool is designed to help open source maintainers improve their security practices and enable consumers to make informed decisions about accepting, mitigating, or rejecting risks from their dependencies. The project explicitly states it is not intended as a one-size-fits-all requirement; the checks are heuristics that can produce false positives and negatives, and every aspect of scoring reflects design choices rather than universal standards.

The project maintains active engagement with its community through documented contribution pathways, including a guide for adding new checks. Development activity shows consistent attention to both bug fixes and feature enhancements, with structured processes for reporting security issues and community feedback. The tool has evolved to support structured results as an alternative to aggregate scoring, enabling consumers to verify specific conditions rather than relying solely on numerical scores.