# 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.

Canonical product page: https://mayd-it.com/data-tools/actors/openssf-scorecard-change-monitor/

## Example input

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

## Ready-to-use input recipes

These are downloadable JSON configurations. They do not start runs or represent public Apify saved tasks. Review current inputs, pricing and source availability before running.

[Default input](https://mayd-it.com/data-tools/actors/openssf-scorecard-change-monitor/input.json) · [Input schema](https://mayd-it.com/data-tools/actors/openssf-scorecard-change-monitor/input-schema.json) · [Saved output capture](https://mayd-it.com/data-tools/actors/openssf-scorecard-change-monitor/evidence.json)

### Review two open-source foundation repositories

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

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

[Download JSON](https://mayd-it.com/data-tools/actors/openssf-scorecard-change-monitor/examples/recipe-1.json) · [Example evidence](https://mayd-it.com/data-tools/actors/openssf-scorecard-change-monitor/examples/recipe-1.evidence.json)

Historical successful run recorded 2026-11-21 UTC, with 2 saved rows. This does not establish current availability.

### Inspect workflow and dependency posture

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

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

[Download JSON](https://mayd-it.com/data-tools/actors/openssf-scorecard-change-monitor/examples/recipe-2.json) · [Example evidence](https://mayd-it.com/data-tools/actors/openssf-scorecard-change-monitor/examples/recipe-2.evidence.json)

Historical successful run recorded 2026-11-21 UTC, with 1 saved rows. This does not establish current availability.

### Start a comparable-scan repository watch

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

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

[Download JSON](https://mayd-it.com/data-tools/actors/openssf-scorecard-change-monitor/examples/recipe-3.json) · [Example evidence](https://mayd-it.com/data-tools/actors/openssf-scorecard-change-monitor/examples/recipe-3.evidence.json)

Historical successful run recorded 2026-11-21 UTC, with 2 saved rows. This does not establish current availability.

[All example inputs](https://mayd-it.com/data-tools/actors/openssf-scorecard-change-monitor/examples/index.json)
## Choose this tool

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

Useful output columns: `title`, `repository`, `score`, `scanDate`, `scorecardVersion`, `scanAgeDays`, `staleScan`, `checks`, `reviewFindings`.

## Practical workflow

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

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.

## Real output sample

One selected row from a 2026-11-21 run. Selected original scalar fields from one actual saved observation; nested data and private artifact links omitted.

Run: E2537DuBpVAyzwEku. Summary status: ok. Incomplete: false.

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health.

```json
{
  "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"
}
```




## Full guide

![OpenSSF Scorecard Monitor — illustrative workflow](https://mayd-it.com/assets/actor-banners/openssf-scorecard-change-monitor-37779021cbc0.png)

# 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.

```json
{
  "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.

```json
{
  "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.

```json
{
  "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](https://scorecard.dev/) publishes heuristic repository supply-chain checks. [Public result example](https://api.scorecard.dev/projects/github.com/ossf/scorecard). 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](https://apify.com/maydit/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](https://apify.com/maydit/github-repository-change-monitor)

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.
