Microproduct Data GuideIntermediate

OpenSSF Scorecard

Automated security-practice scores for public repositories for building dependency-acceptance checks and maintainer-risk reviews.

Start the Guide Open Official Source
Report a Problem

At a Glance

Difficulty
Intermediate — some data preparation helps
Size
Tiny · ≤0.01 GB
Formats
JSON
Access
API
API Key
Not Required
Provider
Open Source Security Foundation
Updates
Continuous
Last Verified
Sep 27, 2026
Source Type
Nonprofit Source
Data Terms
Community Data License Agreement Permissive 2.0
  • Python Syntax Checked

From Source to Product Signal

Test a Product Idea in Four Steps

OpenSSF Scorecard publishes precomputed checks for public GitHub projects. Start with one well-known repository and read the aggregate score plus a few high-risk checks. Scores describe repository practices, not whether a specific package version is vulnerable.

1

Check the Setup

  • Python 3.10 or newer
  • A notebook environment such as Jupyter or Google Colab
  • An internet connection
2

Access the Data

  1. 1.Read the Scorecard project page and the CDLA Permissive 2.0 data licence.
  2. 2.Request the published score for github.com/ossf/scorecard.
  3. 3.Keep the date, aggregate score, and check names before comparing projects.
Open Official Source
3

Run the Python Example

Install the packages, then run the notebook cell.

python -m pip install pandas requests

import pandas as pd
import requests

response = requests.get(
    "https://api.scorecard.dev/projects/github.com/ossf/scorecard",
    timeout=30,
)
response.raise_for_status()
payload = response.json()
checks = pd.json_normalize(payload.get("checks", []))
checks["repo"] = payload.get("repo", {}).get("name")
checks["score"] = payload.get("score")
print(payload.get("repo"), payload.get("score"))
print(checks[["name", "score", "reason"]].head(10))
4

Test a Useful Signal

Review One Repository's Scorecard Checks

Decide whether Scorecard can support an accept-or-review rule for a new dependency.

  1. 01Store the aggregate score and the Dangerous-Workflow, Branch-Protection, and Maintained checks.
  2. 02Flag any check scored below 5 and record the published reason text.
  3. 03State that Scorecard does not replace CVE monitoring or a review of the exact package version you would install.

Related Datasets

Dataset Details

Open Source Security Foundation is a nonprofit source. Last verified 2026-09-27. Temporal coverage: continuously rescored public repositories.

Geography

Global

Formats

JSON

Provider

Open Source Security Foundation

Data Terms

Community Data License Agreement Permissive 2.0

Send Feedback