# OpenSSF Scorecard Monitor – Repository Posture Changes — workflow

## 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"
}
```

## Combine with companion tools

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

### [OSV Package Advisory Monitor](https://mayd-it.com/data-tools/actors/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://mayd-it.com/data-tools/actors/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.
