[OSSFScorecard] Read api.scorecard.dev, not the diverged legacy host - #12121
Open
richcreations wants to merge 1 commit into
Open
[OSSFScorecard] Read api.scorecard.dev, not the diverged legacy host#12121richcreations wants to merge 1 commit into
richcreations wants to merge 1 commit into
Conversation
Contributor
|
richcreations
added a commit
to richcreations/imud
that referenced
this pull request
Sep 1, 2026
The canonical badge URL, https://api.scorecard.dev/projects/.../badge, is a 302 to img.shields.io/ossf-scorecard/..., and shields' ossf-scorecard service hardcodes the legacy host api.securityscorecards.dev. The two OpenSSF API hosts have diverged, so the badge rendered 7.3 while the viewer it links to showed 8.3. Measured 2026-09-01, through shields' own dynamic/json route so that one shields instance fetched both hosts in the same second: shields -> api.scorecard.dev 8.3 shields -> api.securityscorecards.dev 7.3 Nothing on this side is caching it. cf-cache-status was MISS on every cache-busted request, a bogus repo path returned a live "invalid repo path", and both hosts answer 8.3 when queried directly from here and from a third-party fetcher on another network. Querying ?commit=<sha> across the history dates the freeze: the legacy host still serves the result for 7989661 (2026-08-25T20:03:14Z, 7.3), and the next published result, 504ae64 at 22:54 the same day, was 8.1. Confirmed upstream in badges/shields#12117, where a Scorecard maintainer says purges reach api.scorecard.dev but not api.securityscorecards.dev. Fix sent as badges/shields#12121; revert to the canonical URL once it lands. Signed-off-by: Richard Simpson <richcreations@gmail.com>
richcreations
added a commit
to richcreations/imud
that referenced
this pull request
Sep 1, 2026
The canonical badge URL, https://api.scorecard.dev/projects/.../badge, is a 302 to img.shields.io/ossf-scorecard/..., and shields' ossf-scorecard service hardcodes the legacy host api.securityscorecards.dev. The two OpenSSF API hosts have diverged, so the badge rendered 7.3 while the viewer it links to showed 8.3. Measured 2026-09-01, through shields' own dynamic/json route so that one shields instance fetched both hosts in the same second: shields -> api.scorecard.dev 8.3 shields -> api.securityscorecards.dev 7.3 Nothing on this side is caching it. cf-cache-status was MISS on every cache-busted request, a bogus repo path returned a live "invalid repo path", and both hosts answer 8.3 when queried directly from here and from a third-party fetcher on another network. Querying ?commit=<sha> across the history dates the freeze: the legacy host still serves the result for 7989661 (2026-08-25T20:03:14Z, 7.3), and the next published result, 504ae64 at 22:54 the same day, was 8.1. Confirmed upstream in badges/shields#12117, where a Scorecard maintainer says purges reach api.scorecard.dev but not api.securityscorecards.dev. Fix sent as badges/shields#12121; revert to the canonical URL once it lands. Signed-off-by: Richard Simpson <richcreations@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #12117, where a Scorecard maintainer confirmed the divergence is a CDN
bug: purges reach
api.scorecard.devbut notapi.securityscorecards.dev.Same repo, fetched just now:
api.scorecard.devapi.securityscorecards.devResponse shape is unchanged, and both service-test fixtures behave identically
on the new host —
rohankh532/org-workflow-addreturns 200 with a score,invalid-user/invalid-reporeturns 404.@rhalbersma had planned this PR; happy to close in favour of theirs.