Skip to content

Releases: ossf/scorecard-action

v2.5.0

Choose a tag to compare

@justaugustus justaugustus released this 12 Oct 02:54
v2.5.0
fa7117d

What's Changed

This release moves the action to Scorecard v5.6.0, the first Scorecard release since its hosted
services moved to new infrastructure.

For changes to checks and results, and what the infrastructure move means for you, see the
Scorecard v5.6.0 release notes.

  • The action's container image is built with Go 1.27.2 on a refreshed distroless base. by
    @justaugustus in #1716
  • The installer (cmd/installer) now creates .github/workflows/scorecard.yml, and still
    recognizes existing scorecards.yml and scorecards-analysis.yml workflows. by @justaugustus in #1716
  • The Scorecard version in results now always matches the Scorecard release the action is built
    with. by @justaugustus in #1718
  • The action no longer prints the GitHub token variable while validating its options. by
    @arpitjain099 in #1709
  • results_format accepts intoto, which wraps the JSON results in an in-toto attestation
    statement. by @puerco in #1702

Other

New Contributors

Full Changelog: v2.4.4...v2.5.0

v2.4.4

Choose a tag to compare

@spencerschrock spencerschrock released this 23 Jul 21:12
v2.4.4
2d11466

What's Changed

This update bumps the Scorecard version to the v5.5.0 release. For a complete list of changes, please refer to the Scorecard v5.4.0 release notes and the Scorecard v5.5.0 release notes.

Full Changelog: v2.4.3...v2.4.4

v2.4.3

Choose a tag to compare

@spencerschrock spencerschrock released this 30 Sep 20:40
v2.4.3
4eaacf0

What's Changed

This update bumps the Scorecard version to the v5.3.0 release. For a complete list of changes, please refer to the Scorecard v5.3.0 release notes.

Documentation

Other

New Contributors

Full Changelog: v2.4.2...v2.4.3

v2.4.2

Choose a tag to compare

@spencerschrock spencerschrock released this 30 May 17:03
v2.4.2
05b42c6

What's Changed

This update bumps the Scorecard version to the v5.2.1 release. For a complete list of changes, please refer to the Scorecard v5.2.0 and v5.2.1 release notes.

Full Changelog: v2.4.1...v2.4.2

v2.4.1

Choose a tag to compare

@spencerschrock spencerschrock released this 21 Feb 17:13
v2.4.1
f49aabe

What's Changed

  • This update bumps the Scorecard version to the v5.1.1 release. For a complete list of changes, please refer to the v5.1.0 and v5.1.1 release notes.
  • Publishing results now uses half the API quota as before. The exact savings depends on the repository in question.
  • Some errors were made into annotations to make them more visible
    • Make default branch error more prominent by @jsoref in #1459
  • There is now an optional file_mode input which controls how repository files are fetched from GitHub. The default is archive, but git produces the most accurate results for repositories with .gitattributes files at the cost of analysis speed.
  • The underlying container for the action is now hosted on GitHub Container Registry. There should be no functional changes.

Docs

New Contributors

v2.4.0

Choose a tag to compare

@spencerschrock spencerschrock released this 26 Jul 16:53
v2.4.0
62b2cac

What's Changed

This update bumps the Scorecard version to the v5 release. For a complete list of changes, please refer to the v5.0.0 release notes. Of special note to Scorecard Action is the Maintainer Annotation feature, which can be used to suppress some Code Scanning false positives. Alerts will not be generated for any Scorecard Check with an annotation.

Documentation

New Contributors

Full Changelog: v2.3.3...v2.4.0

v2.3.3

Choose a tag to compare

@spencerschrock spencerschrock released this 09 May 21:18
v2.3.3
dc50aa9

Note

There is no v2.3.2 release as a step was skipped in the release process. This was fixed and re-released under the v2.3.3 tag

What's Changed

  • 🌱 Bump github.com/ossf/scorecard/v4 (v4.13.1) to github.com/ossf/scorecard/v5 (v5.0.0-rc1) by @spencerschrock in #1366
  • 🌱 Bump github.com/ossf/scorecard/v5 from v5.0.0-rc1 to v5.0.0-rc2 by @spencerschrock in #1374
  • 🌱 Bump github.com/ossf/scorecard/v5 from v5.0.0-rc2 to v5.0.0-rc2.0.20240509182734-7ce860946928 by @spencerschrock in #1377

For a full changelist of what these include, see the v5.0.0-rc1 and v5.0.0-rc2 release notes.

Documentation

Full Changelog: v2.3.1...v2.3.3

v2.3.1

Choose a tag to compare

@spencerschrock spencerschrock released this 23 Oct 19:49
v2.3.1
0864cf1

What's Changed

  • 🌱 Bump github.com/ossf/scorecard/v4 from v4.13.0 to v4.13.1 by @spencerschrock in #1282
    • Adds additional Fuzzing detection and fixes a SAST bug related to detecting CodeQL. For a full changelist of what this includes, see the v4.13.1 release notes

Full Changelog: v2.3.0...v2.3.1

v2.3.0

Choose a tag to compare

@spencerschrock spencerschrock released this 06 Oct 21:10
v2.3.0
483ef80

What's Changed

  • 🌱 Bump github.com/ossf/scorecard/v4 from v4.11.0 to v4.13.0 by @spencerschrock in #1270
    • For a full changelist of what this includes, see the v4.12.0 and v4.13.0 release notes
  • ✨ Send rekor tlog index to webapp when publishing results by @spencerschrock in #1169
  • 🐛 Prevent url clipping for GHES instances by @rajbos in #1225

Documentation

New Contributors

Full Changelog: v2.2.0...v2.3.0

v2.2.0

Choose a tag to compare

@spencerschrock spencerschrock released this 23 Jun 21:19
v2.2.0
08b4669

What's Changed

Scorecard Result Viewer

Thanks to contributions from @cynthia-sg and @tegioz at CLOMonitor, there is a new Scorecard Result visualization page at https://securityscorecards.dev/viewer/?uri=<project-url>.

As an example, you can see our own score visualized here
Checkout our README to learn how to link your README badge to the new visualization page.

Publishing Results

This release contains two fixes which will improve the user experience when publish_results is true

  • Runs that fail our workflow restrictions will fail with a 400 response indicating the problem, instead of a vague 500 status. (#1156, resolved #1150)
  • Scorecard action will retry when signing results and submitting them to our web API. This should help with flakiness from connection failures. (#1191)

Docs

  • 📖 Update README to accept fine-grained tokens by @pnacht in #1175
  • 📖 Update installation instructions to match current GitHub UI by @joycebrum in #1153
  • 📖 Document the GitHub action workflow restrictions when publishing results. by @spencerschrock in

New Contributors

Full Changelog: v2.1.3...v2.2.0