aquasecurity/tfsec vs avelino/awesome-go
Both showing Healthy signals — pick on fit, not health
As of September 2026, tfsec and awesome-go both show healthy maintenance signals. tfsec last saw a commit 5 months ago with 21+ active contributors, while awesome-go was committed to 2 weeks ago with 56+ active contributors. Both use the MIT 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.
aquasecurity/tfsec
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.
- ⚠Slowing — last commit 5mo ago
- ⚠Scorecard: marked unmaintained (0/10)
- ✓Last commit 5mo ago
- ✓21+ active contributors
- ✓Distributed ownership (top contributor 34% of recent commits)
- ✓MIT 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
avelino/awesome-go
Strong maintenance signals
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.
Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10
- ⚠Scorecard: dangerous CI workflow (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓56+ active contributors
- ✓Distributed ownership (top contributor 10% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)
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
| tfsec | awesome-go | |
|---|---|---|
| Stars | 7,037 | 182,930 |
| Last commit | 5mo ago | 14d ago |
| License | MIT | MIT |
| Open issues | 18 | 223 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 100% |
| Dependency CVEs | No CVEs | 0 critical · 0 high · 1 moderate · 0 low |
| Architecture grade | — | A |
| Cycles | — | 0 |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? aquasecurity/tfsec · avelino/awesome-go
Ask AI about aquasecurity/tfsec vs avelino/awesome-go
Open the chat with a comparison question pre-filled.