open-policy-agent/opa vs osohq/oso
open-policy-agent/opa shows stronger signals overall
As of September 2026, opa shows healthier maintenance signals than oso. opa rates Healthy overall while oso rates Mixed. opa was committed to 1 day ago with 13+ active contributors, while oso last saw a commit 1 year ago with 30+ active contributors. Both use the Apache-2.0 license. Neither has known critical or high-severity CVEs in its dependency tree.
Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.
open-policy-agent/opa
Healthy across all four use cases
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
No blocking repository-level signals were found; deployment review is still required.
- ⚠Scorecard: known vulnerabilities detected (scored 2/10 by OpenSSF)
- ✓Last commit today
- ✓13 active contributors
- ✓Distributed ownership (top contributor 31% of recent commits)
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
osohq/oso
Stale — last commit 2y ago
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; Scorecard "Token-Permissions" is 0/10
- ⚠Stale — last commit 2y ago
- ⚠Scorecard: marked unmaintained (0/10)
- ✓30+ active contributors
- ✓Distributed ownership (top contributor 21% of recent commits)
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
Signal-by-signal breakdown
| opa | oso | |
|---|---|---|
| Stars | 12,238 | 3,488 |
| Last commit | 1d ago | 1y ago |
| License | Apache-2.0 | Apache-2.0 |
| Open issues | 308 | 119 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 56% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? open-policy-agent/opa · osohq/oso
Ask AI about open-policy-agent/opa vs osohq/oso
Open the chat with a comparison question pre-filled.