github ossf/scorecard v5.7.0

one hour ago

Highlights

  • Built with Go 1.27.4, which rejects TLS certificate chains through the distrusted eMudhra intermediate CAs
    (GO-2026-6809), so Scorecard no longer connects to servers that present them
    (#5364). by @justaugustus in #5460
  • GitHub immutable releases count for Signed-Releases and Pinned-Dependencies. See Score changes.

scorecard mcp: Scorecard in your AI assistant (experimental)

scorecard mcp runs a Model Context Protocol (MCP) server, so assistants such as Claude Code, Claude Desktop and VS
Code can answer questions about a project's security practices from Scorecard data. Ask for a repository's score, the
details and remediation for one check, or a comparison of several repositories, and the answer comes from Scorecard's
published results, with the commit, scan date and Scorecard version it reflects.

It needs no token and no extra install: it's part of the scorecard binary and talks to the client over stdio. For
Claude Code:

claude mcp add scorecard --scope user -- scorecard mcp

It covers repositories that publish their results, such as those using scorecard-action or included in the weekly public
scan. It doesn't run new scans yet. Setup for other clients is in the README and docs/mcp.md.
by @justaugustus in #5402, with fixes listed under General.

OSPS Baseline conformance mode (experimental)

Scorecard can now report a repository's results against OSPS Baseline requirements
instead of check scores. Choose a maturity level and an output format:

scorecard --repo=github.com/ossf/scorecard \
  --catalog=osps-baseline --profile=maturity-1 --format=json

Each requirement gets PASS, FAIL, UNKNOWN, NOT_APPLICABLE or NEEDS_REVIEW, with the probe findings behind it as
evidence. Requirements Scorecard doesn't map yet are listed as not evaluated. This first release evaluates the
primary-branch protection requirements, OSPS-AC-03.01 and OSPS-AC-03.02. --format=gemara writes a
Gemara Evaluation Log for compliance tooling. Runs without --catalog are
unchanged. The options and output may change, and every run says so on standard error. Details are in
docs/conformance.md. by @justaugustus in #5449

Action Required

  • Scorecard exits 1 again when a repository scan or writing results fails. v5.4.0 through v5.6.0 exited 0 in these
    cases, for example a missing --local path, an unwritable --output file, or an unknown probe. v5.3.0 and earlier
    exited 1. Remaining repositories are still scanned, and low or inconclusive scores still exit 0. by @JamieMagee in
    #5319
  • scorecard serve listens on 127.0.0.1 by default and no longer sends CORS headers. To reach it from other hosts,
    including through a published container port, pass --listen, for example scorecard serve --listen 0.0.0.0.
    scorecard serve --help now says the server has no authentication or rate limiting. by @justaugustus in #5378 and
    #5337
  • scorecard-attestor has been removed, along with its attestor/ Go packages. by @justaugustus in #5371
  • GitLab: GITLAB_AUTH_TOKEN is sent only to the instance in GL_HOST, or to GitLab.com when GL_HOST is unset.
    Other GitLab instances are scanned without the token, so set GL_HOST to scan private projects on a self-managed
    instance. GitLab repository URLs must use https. by @justaugustus in 8517fc1
  • Library users: Go 1.27.4 or later is required (go directive raised from 1.26.8). by @justaugustus in #5475
  • Library users: clients.RepoClient has a new method, IsReleaseImmutable. Implementations outside Scorecard must
    add it. by @jessehouwing in #5248

Security

v5.7.0 fixes the issues in these advisories.

Also published: GHSA-crhh-248m-2rm9, for this repository's scdiff CI workflow, fixed in 2024 by #4376. It needs no
action from users.

Score changes

Branch-Protection

  • A GitHub merge queue required by an active repository ruleset now satisfies "require branches to be up to date before
    merging". Scores can go up. by @osterman in #5281
  • Azure DevOps: PR policies for default and named branches are mapped to branch protection, without counting unrelated
    push restrictions or unproven permissions. by @JamieMagee in #5340
  • GitLab: a failed API request no longer stops the check, and a 401 or 403 from the external status checks API counts as
    no status checks instead of failing the check. by @vishnums2k5 in #5359

Code-Review

  • Azure DevOps: approvals use PR identity IDs and reviewer votes, and a missing identity no longer counts as an
    approval. Scores can go down. by @JamieMagee in #5325

Dangerous-Workflow

  • An unterminated ${{ expression in a workflow no longer aborts the check. by @Sahana2524 in #5177

Maintained

  • GitLab: each issue's author is checked separately. Before, one issue opened by a project member made every issue count
    as member activity, so some GitLab projects may score lower. by @vishnums2k5 in #5381

Pinned-Dependencies

  • Actions pinned to a tag of a GitHub immutable release count as pinned. Scores can go up. by @jessehouwing in #5248

SAST

  • References to LGTM.com, closed in 2022, have been removed. by @Kielek in #4985

Signed-Releases

  • A GitHub immutable release counts as signed, so projects that publish immutable releases can score higher. by
    @martincostello in #5002

Vulnerabilities

  • osv-scanner is updated to v2.7.1. Two upstream fixes drop false matches: Go standard library vulnerabilities on
    modules whose path ends in /go, and results from network-based plugins in offline mode. Scores can go up. by
    @justaugustus in #5475

General

  • With --file-mode git, a malformed or all-zero --commit fails with invalid commit SHA instead of silently
    scanning the default branch. by @cpanato in #5368
  • scorecard --help documents the token environment variables, corrects the --repo and --repos formats, and sorts
    the --checks values. by @lasomethingsomething in #5430

scorecard mcp

Fixes since the subcommand landed in #5402:

  • get_check_result returns missing_checks and complete metadata. by @areeebs in #5418
  • Repository references with an uppercase scheme or a trailing .git are accepted, . and .. path segments are
    rejected, and GitLab subgroup paths are reported as unsupported. by @areeebs in #5419
  • Commit SHAs are lowercased before querying published results, a missing result for a pinned commit is reported
    separately from a repository with no results, and results whose commit doesn't match the request are rejected. by
    @areeebs in #5420
  • The experimental flag for each check comes from its definition. by @Muneer320 in #5421

Docs

Other

Project

  • We closed 165 issues filed before 2024 to refresh the tracker, and new issues now go through issue forms (#5414).
    Details are in the issue cleanup discussion.

Known Issues

  • GitLab: Vulnerabilities returns −1 (inconclusive) for GitLab repositories
    (#5056).
  • Pinned-Dependencies: findings reached through a YAML alias point at the anchor's line, not the alias
    (#5291). Planned for v5.8.0.
  • Dangerous-Workflow misses some untrusted checkouts and workflow_run context fields
    (#5379, #5396).
  • CI-Tests and SAST can fail with an unrelated organization IP allow-list error when recent commits carry
    third-party app check suites (#5382).
  • CI-Tests and SAST can score lower when GitHub no longer returns older PR check data
    (#5411).
  • GitLab: Maintained reads only the first 20 issues and project members, so large projects may score lower.

New Contributors

Full Changelog: v5.6.0...v5.7.0

Don't miss a new scorecard release

NewReleases is sending notifications on new releases.