May’d It
OpenSSF Scorecard Monitor — illustrative workflow

DATA TOOLS / ai

OpenSSF Scorecard Monitor – Repository Posture Changes

Track public OpenSSF repository scores and check-level changes with scan dates, commits and comparable-scan evidence. Flag stale or inconclusive checks without claiming software is secure.

JSON / CSV outputLimited permissionsSource: maydit/openssf-scorecard-change-monitor

FROM SOURCE TO A USEFUL RESULT

A practical workflow

Choose this tool when…

For AI integrators, open-source program offices and developer platforms maintaining a public GitHub dependency watchlist.

titlerepositoryscorescanDatescorecardVersionscanAgeDaysstaleScanchecksreviewFindings

Which repositories need a closer supply-chain review, and what actually changed in their published checks?

Collect published Scorecard scans, review low check scores with original reasons, then compare only newer scans produced by the same Scorecard version and commit.

Check the fit and source limits

Published scans only: this Actor does not run Scorecard, inspect private repositories, or certify software safety. A missing scan is a source diagnostic, not a zero score or a paid result. No deterioration alert is produced across different Scorecard versions/commits, changed date precision, older scans or stale current scans.

Download this workflow as Markdown · Configure a small first run

REAL RUN · DATED EVIDENCE

See an actual saved result

Captured 2026-11-21. Selected columns from one saved row. Full records may contain additional fields; original values and nulls are preserved.

{
  "recordId": "openssf:ossf/scorecard",
  "title": "ossf/scorecard — OpenSSF Scorecard",
  "repository": "ossf/scorecard",
  "score": 8.8,
  "scanDate": "2026-11-21T01:38:51.000Z",
  "scorecardVersion": "v5.7.0",
  "scanAgeDays": 0.777,
  "staleScan": false,
  "comparisonEligibility": "no_prior_scan",
  "comparisonStatus": "not_requested",
  "sourceUrl": "https://api.scorecard.dev/projects/github.com/ossf/scorecard",
  "url": "https://github.com/ossf/scorecard",
  "observedAt": "2026-11-21T20:18:23.944Z"
}

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health. Run reference: E2537DuBpVAyzwEku. Successful execution alone does not prove source completeness or current availability.

START SMALL

Example input

Historical evidence for this exact JSON was recorded 2026-11-21 on its original build. This is not a fresh source-availability test. Adjust targets and dates for your use case. Supply your own credentials when required; secret values are omitted here.

{
  "repositories": [
    "ossf/scorecard",
    "nodejs/node"
  ],
  "maxResults": 2
}
Download input.json

CHOOSE A STARTING POINT

3 ready-to-use inputs

Pick a focused example, copy or download its JSON, then review the inputs and current pricing in your own Apify account. Downloading a configuration does not start a run.

Default input · Input schema · Saved output capture

Review two open-source foundation repositories

Read published Scorecard scans for Scorecard and Node.js with dates, commits and check-level evidence.

{
  "repositories": [
    "ossf/scorecard",
    "nodejs/node"
  ],
  "maxResults": 2
}

Saved run evidence: 2026-11-21 UTC · 2 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Inspect workflow and dependency posture

Focus on Dangerous-Workflow, Pinned-Dependencies and Code-Review checks in the official Scorecard repository.

{
  "repositories": [
    "ossf/scorecard"
  ],
  "checkNames": [
    "Dangerous-Workflow",
    "Pinned-Dependencies",
    "Code-Review"
  ],
  "maxResults": 1
}

Saved run evidence: 2026-11-21 UTC · 1 saved row. This is a historical check, not live data or a guarantee that every query will succeed today.

Start a comparable-scan repository watch

Establish a private baseline for two repositories. Later comparable scans identify deteriorated checks.

{
  "repositories": [
    "ossf/scorecard",
    "nodejs/node"
  ],
  "maxResults": 2,
  "comparePrevious": true,
  "snapshotName": "repository-posture-watch"
}

Saved run evidence: 2026-11-21 UTC · 2 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Download all example inputs and evidence references

A CLEAR DATA CONTRACT

Inputs you can configure

FieldTypeMeaning
repositoriesarray

Public GitHub owner/repository names or exact repository URLs. Empty means ossf/scorecard and nodejs/node. A repository must already have a published OpenSSF scan.

checkNamesarray

Optional exact check names such as Dangerous-Workflow and Pinned-Dependencies. Empty includes all published checks. Missing or inconclusive checks remain explicit.

maxScanAgeDaysinteger

Mark published scans older than this threshold as stale. Stale scans remain source observations but cannot produce a fresh regression alert.

maxResultsinteger

Limit validated saved rows. If lower than the selected source count, the run is incomplete and does not advance history.

comparePreviousboolean

A complete first run establishes a private baseline. Incomplete sources, output, time or spending limits preserve previous history. Avoid overlapping runs for the same watchlist.

onlyChangesboolean

Enables comparison. An unchanged run may legitimately save zero rows. First complete run saves all observations. No removal inference from missing sources.

snapshotNamestring

A stable name for this watchlist: 1–80 letters, numbers, underscores or hyphens.

maxRunSecondsinteger

Network requests honor the remaining budget. Smaller watchlists improve completeness. Platform timeout is also respected.

reviewBelowScoreinteger

Make an evidence-backed review list of scored checks below this value. Sorted by actual published check score, not an invented security rating. Inconclusive and missing checks are listed separately.

Output fields

titlerepositoryscorescanDatescorecardVersionscanAgeDaysstaleScanchecksreviewFindingscomparisonEligibilitydeterioratedCheckscomparisonStatussourceUrl

These are the columns in the default dataset view. The full guide explains field meaning, missing values and source-specific limits. JSON preserves nested data; CSV is useful for flat columns.

Input schema JSON

KNOW THE COST

Event pricing

Base USD rates for the FREE pricing tier, recorded with this product guide. Plan discounts and future pricing changes may apply. Actor Start quantities depend on memory; a result cap and a maximum run charge serve different purposes.

EventUSD per eventWhat is charged
Actor Start$0.00005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Saved observation$0.002One validated observation confirmed saved to the dataset.

BUILD A REVIEWED WORKFLOW

Use this with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

Parallel research context

Combine repository maintenance and supply-chain checks with package vulnerability advisories.

  1. Review the repository's named Scorecard checks and scanned commit.
  2. Map your own dependency inventory to exact package ecosystem and name inputs for the OSV monitor.
  3. Join evidence in your review queue; confirm affected versions before taking action.

Repository names are not package identifiers. Scorecard posture and vulnerability exposure are different evidence sources; neither certifies safety.

Read the companion guide →

Parallel research context

Investigate the repository activity behind changed security-posture checks.

  1. Select the repository associated with the observation.
  2. Run the repository monitor separately for the same public repository.
  3. Review activity and source links alongside Scorecard's scan date and tool version.

Repository activity does not prove a security issue or resolve a finding. The two observations can have different source times.

Read the companion guide →

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Source contract captured from build 1.0.1. Presentation refreshed 2026-11-21. Example outputs retain their original sample context; they are not live results.

OpenSSF Scorecard Monitor – Repository Posture Changes

Which repositories need a closer supply-chain review, and what actually changed in their published checks?

Follow the public repositories behind your AI tools and applications with an evidence-based review list. Each observation preserves the published scan date, repository commit, Scorecard version and named check results.

Start with a small useful result

For AI integrators, open-source program offices and developer platforms maintaining a public GitHub dependency watchlist. No API key, account login or proxy is required. Press Start to collect at most two real public observations. Leave comparison off for the first exploration. Every row includes a stable recordId, title, url, sourceUrl and observedAt.

What you can do with the results

Use reviewBelowScore to collect checks below your chosen threshold. Each row’s reviewFindings retains the exact check score, reason and documentation link; SUMMARY.reviewQueue combines the watched repositories and sorts by the published check score, ascending. This is a transparent review order, not a new security rating. The summary can include observed but unsaved results when output is capped—always consult rowsSaved and coverage before consuming it. Missing and inconclusive checks remain separate from scored findings.

Three practical input recipes

Review two open-source foundation repositories

Read published Scorecard scans for Scorecard and Node.js with dates, commits and check-level evidence.

{
  "repositories": [
    "ossf/scorecard",
    "nodejs/node"
  ],
  "maxResults": 2
}

Inspect workflow and dependency posture

Focus on Dangerous-Workflow, Pinned-Dependencies and Code-Review checks in the official Scorecard repository.

{
  "repositories": [
    "ossf/scorecard"
  ],
  "checkNames": [
    "Dangerous-Workflow",
    "Pinned-Dependencies",
    "Code-Review"
  ],
  "maxResults": 1
}

Start a comparable-scan repository watch

Establish a private baseline for two repositories. Later comparable scans identify deteriorated checks.

{
  "repositories": [
    "ossf/scorecard",
    "nodejs/node"
  ],
  "maxResults": 2,
  "comparePrevious": true,
  "snapshotName": "repository-posture-watch"
}

Changes you can verify

Deterioration requires a newer scan with the same Scorecard version, Scorecard commit and date precision, within maxScanAgeDays. comparisonEligibility explains every suppression. A lower comparable check score appears in deterioratedChecks with its prior value; -1 means inconclusive and is never converted to zero. An updated scan can be a changed observation even when its scores are unchanged.

Set comparePrevious: true and a stable snapshotName to retain a private baseline for the selected scope. The first complete run marks observations new; later runs mark them changed or unchanged with changedFields and the previous normalized observation. The baseline belongs to the account running the Actor. A different source list or comparison scope creates separate history.

onlyChanges: true enables comparison and suppresses unchanged rows; a successful repeat can legitimately save zero rows. Source failures, truncated output, a deadline or a spending limit preserve the prior baseline. A concurrent-history change detected before commit is reported rather than overwritten; avoid overlapping runs for the same watchlist because the storage service does not provide an atomic compare-and-swap transaction.

Coverage and limits

  • The default watches ossf/scorecard and nodejs/node; both had public scans at source verification. Other repositories may not be indexed by OpenSSF.
  • Repository URLs must be exact public GitHub repository URLs; repository names are case-insensitive. Up to 20 repositories per run.
  • checkNames selects exact source names. Unknown requested names appear in missingChecks; a missing selected check does not imply a failure or low score.
  • scanAgeDays is computed from the published date and observation time. Day-only dates are normalized to midnight UTC and retain scanDatePrecision: day.
  • The source is OpenSSF’s published result API. Its availability, collection coverage and scoring method are outside this Actor’s control. HTTP 401,403 or429 stops the remaining requests.
  • At most 20 targets and 20 saved observations per run. Requests use a 120-second maximum run budget and the platform’s earlier deadline.
  • All-source failure fails honestly. Source errors and access problems are written to SUMMARY, never fabricated as paid dataset rows. A partial run retains useful rows and clearly reports incomplete coverage.

Output, pricing and scheduling

Export the dataset as JSON, CSV or Excel. Read SUMMARY for source coverage, limits and history status; open RUN_REPORT for a readable overview. For nested checks or skills, JSON preserves the full structure.

Base pricing is $0.002 per confirmed saved observation, plus $0.00005 per Actor start at the default 256 MB. Standard plan-tier discounts may apply to results. A row containing several checks or skills is still one observation. Failed sources and unchanged results suppressed by onlyChanges do not incur a result charge. Apify platform usage may also apply under your plan. The Actor checks remaining result allowance before saving, and the last accepted row at the limit is counted correctly.

For recurring checks, save a task with your watchlist and use Apify Schedules at a cadence appropriate to the upstream source. Configure integrations yourself if you need to deliver results elsewhere; this Actor sends no messages and creates no schedules.

Source and interpretation

OpenSSF Scorecard publishes heuristic repository supply-chain checks. Public result example. This independent monitor is not affiliated with OpenSSF or a substitute for a security review.

Use the Actor’s Issues tab to report source changes or request a supported input example.

Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

OSV Package Advisory Monitor

Combine repository maintenance and supply-chain checks with package vulnerability advisories.

  1. Review the repository's named Scorecard checks and scanned commit.
  2. Map your own dependency inventory to exact package ecosystem and name inputs for the OSV monitor.
  3. Join evidence in your review queue; confirm affected versions before taking action.

Repository names are not package identifiers. Scorecard posture and vulnerability exposure are different evidence sources; neither certifies safety.

GitHub Repository Change Monitor - Stars, Forks & Activity

Investigate the repository activity behind changed security-posture checks.

  1. Select the repository associated with the observation.
  2. Run the repository monitor separately for the same public repository.
  3. Review activity and source links alongside Scorecard's scan date and tool version.

Repository activity does not prove a security issue or resolve a finding. The two observations can have different source times.