ossf /scorecard

OpenSSF Scorecard - Security health metrics for Open Source

★ 5,839⑂ 773👁 71⑃ 4,055● 1,313▤ 49
GoApache-2.0Created 2020-10-09scorecard.dev
下载:v5.6.0v5.6.0 ↓5.6.02026-10-12
+4
日增长
5,839
stars
773
forks
71
watchers
4,055
prs
1,313
issues
49
releases

README

OpenSSF Scorecard













 Overview

-   What Is Scorecard?
-   Prominent Scorecard Users
-   View a Project's Score
-   Scorecard's Public Data

 Using Scorecard

-   Scorecard GitHub Action
-   Scorecard REST API
-   Scorecard Badges
-   Scorecard MCP Server
-   Scorecard Command Line Interface
    -   Prerequisites
    -   Installation
    -   Authentication
    -   Basic Usage

 Checks

-   Default Scorecard Checks
-   Detailed Check Documentation (Scoring Criteria, Risks, and
    Remediation)
-   Beginner's Guide to Scorecard Checks

 Other Important Recommendations
-   Two-factor Authentication (2FA)

 Scoring
-   Aggregate Score

 Contribute

-   Report Problems
-   Code of Conduct
-   Contribute to Scorecard 
-   Add a New Check
-   Connect with the Scorecard Community
-   Report a Security Issue

 FAQ

- FAQ

 Overview

 What is Scorecard?
We created Scorecard to help open source maintainers improve their security
best practices and to help open source consumers judge whether their dependencies
are safe.

Scorecard is an automated tool that assesses a number of important heuristics
("checks") associated with software security and assigns
each check a score of 0-10. You can use these scores to understand specific
areas to improve in order to strengthen the security posture of your project.
You can also assess the risks that dependencies introduce, and make informed
decisions about accepting these risks, evaluating alternative solutions, or
working with the maintainers to make improvements.

The inspiration for Scorecard’s logo:
"You passed! All D's ... and an A!"

 Project Goals

1.  Automate analysis and trust decisions on the security posture of open source
    projects.

1.  Use this data to proactively improve the security posture of the critical
    projects the world depends on.

1. Act as a measurement tool for existing policies

    If OSS consumers require certain behaviors from their dependencies,
    Scorecard can be used to measure those. With the V5 release, we see
    Structured Results as a way of doing this if there is a supported analysis.
    Instead of relying on an aggregate score of X/10, or a Maintained score of
    Y/10, an OSS consumer may want to ensure the repo they're depending on
    isn't archived (which is covered by the archived probe). The OpenSSF
    takes this approach with its own Security Baseline for projects.

 Project Non-Goals

1.  To be a definitive report or requirement that all projects should follow.

    Scorecard is not intended to be a one-size-fits-all solution. Every step of
    making our results is opinionated: what checks get included or excluded,
    the importance of each check, and how scores are calculated. The checks
    themselves are heuristics; there are false positives and false negatives.

    Whether it’s due to applicability, or feasibility, or a matter of opinion,
    what's included or excluded from Scorecard results leads to a lot of
    discussion. It’s impossible to

Top issues

Discussions

Latest release

v5.6.0 v5.6.0 2026-10-12
Scorecard Infrastructure Migration

v5.6.0 is the first Scorecard release since our hosted services moved! :tada:

The weekly batch scans and the REST API now run on AboutCode Foundation
infrastructure on AWS, operated in partnership with the Scorecard Steering Committee.

AboutCode is a public-benefit non-profit that already consumes Scorecard data and runs similar
large-scale data services, including PurlDB and
VulnerableCode.

The full announcement is in 5208.

What this means for you:

- CLI and REST API users: nothing changes. The API endpoint and the tooling are the same.

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON