OSS Criticality Radar

What is OSS Criticality Radar

OSS Criticality Radar is an OpenSSF criticality score lookup for GitHub projects. It takes a repository identifier in either owner/repo form or a full GitHub URL, then calculates the OpenSSF criticality score on the 0 = least critical to 1 = most critical scale. That makes it a focused criticality score tool rather than a general GitHub analytics dashboard.

The app is built for fast checks when you want to understand how central a repository may be in the open source ecosystem. It also exposes a signal breakdown, which helps separate the final criticality score from the inputs behind it. The site notes that the algorithm is by Rob Pike and that it is maintained by the OpenSSF Securing Critical Projects Working Group.

Key features

• Accepts either owner/repo text or a GitHub repository URL, so you can use the criticality score lookup with the format you already have.
• Returns a numeric criticality score on the OpenSSF 0 to 1 scale.
• Shows a signal breakdown alongside the score, which makes the criticality score easier to interpret.
• Focuses on GitHub repositories only, so the app stays narrow and fast.
• Uses a simple search-and-result flow with a single "Get score" action.
• Includes example repositories such as softmaple/softmaple, vercel/next.js, and storybookjs/storybook.

Because it is a dedicated criticality score tool, the interface is minimal. You are not asked to create an account or manage a project list based on the available site copy, and the main workflow is centered on one repository at a time.

How to use it

1. Copy a GitHub repository identifier in owner/repo form, or copy the full repository URL.
2. Paste it into the GitHub repository field on the page.
3. Click Get score.
4. Review the criticality score and the signal breakdown shown by the app.
5. Use the score as a starting point for triage, reporting, or comparison with other repositories.

If you are testing the criticality score lookup, the sample repositories on the page are a quick way to see how the app behaves before entering your own target. That is useful when you want to understand the score format or confirm that a repository resolves correctly.

Who it is for

OSS Criticality Radar is useful for people who need a quick criticality score lookup without building their own pipeline.

• Open source maintainers who want to understand how a repo might be ranked by the OpenSSF criticality model.
• Security and platform teams that review dependency risk and project centrality.
• Researchers and analysts comparing repository importance across GitHub.
• Contributors who want a fast way to inspect the criticality score before opening an issue or making a recommendation.

The app is especially practical when you need a lightweight criticality score tool for one-off checks. It is less useful if you need bulk analysis, historical tracking, or a custom scoring workflow.

What to know before you use it

The criticality score is only one signal, not a full security or maintenance assessment. A high score does not prove that a project is secure, well maintained, or suitable for every dependency decision, and a low score does not mean a repository is unimportant.

A few limits are worth keeping in mind:

• The app works with GitHub repositories, so it is not a general source for GitLab, Bitbucket, or other hosts.
• The score is computed from the OpenSSF criticality model, so it may not match your internal prioritization rules.
• The signal breakdown explains the output, but it does not replace a manual review of the repository itself.
• For policy decisions, supply-chain reviews, or incident work, use the official repository, package metadata, and your own operational data alongside the criticality score lookup.

In practice, OSS Criticality Radar is best used as a fast first pass. For GitHub-only checks, it gives you the OpenSSF criticality score and supporting signals in one place, but you should still verify important decisions against authoritative sources and current repo activity.