Repository navigation
fix(docs): correct the repository name in the Scorecard badge - #22
Merged
Merged
Conversation
The OpenSSF Scorecard API is case sensitive, and the badge asked it for `amagioss/opentams`. That path returns 404, so shields.io rendered the badge as unknown rather than showing the score. Uses `amagioss/OpenTAMS` in both the badge image and the viewer link, which the API answers with the real report (score 6.3, scanned 2026-09-23). The other lowercase `amagioss/opentams` paths in the README stay as they are. github.com resolves a repository name without regard to case, and the `go install` path must match the module path in go.mod, which is lowercase. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014Z8F6zDFV8KeU3G8JrCGko
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
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.
The OpenSSF Scorecard API is case sensitive, and the badge asked it for
amagioss/opentams:shields.io therefore rendered the badge as unknown rather than showing a score. The badge URL itself answers 200 in both cases because it only redirects, which is why this was not obvious.
Uses
amagioss/OpenTAMSin the badge image and the viewer link, which matches the repository name GitHub reports and returns the real report: score 6.3, scanned 2026-09-23, scorecard v5.5.0.