Which has better activity and maintenance signals?
Which has better activity and maintenance signals?
About julien-cpsn/atac · 2 messages · last activity 9/6/2026
Based on the RepoPilot analysis and repository metadata:
julien-cpsn/atac shows stronger engagement signals but weaker maintenance signals:
- 3715 stars and 137 forks indicate significant user interest
- However, the verdict is WAIT — Single-maintainer risk, suggesting limited active maintenance capacity
- OpenSSF Scorecard is 4.9/10 with critical weaknesses: Security-Policy 0/10, SAST 0/10, Branch-Protection 0/10 — indicating minimal security and governance infrastructure
- 1 moderate CVE (RUSTSEC-2025-0141 in bincode) is present but not in direct dependencies
ultraworkers/claw-code lacks explicit signals in the provided data:
- No star count, fork count, or maintainer information is visible
- No OpenSSF Scorecard or dependency vulnerability data is included
- Repository appears to be a code analysis/audit tool (based on file names like
parity_audit.py,execution_registry.py)
Verdict: atac has higher visibility and adoption, but the single-maintainer risk and low security scorecard are significant concerns. claw-code's activity level cannot be assessed from the available data. If you need production-grade tooling, atac's popularity must be weighed against its maintenance risk; claw-code's status is indeterminate without additional metadata.
FOLLOW_UPS:
- What is claw-code's purpose and maturity level?
- Does atac have CI/CD automation configured?
- Are there open security issues in atac's issue tracker?
Want to ask your own question?
Open chat for julien-cpsn/atacPublic Q&A. Generated by RepoPilot from the actual source of julien-cpsn/atac. AI answers can be incomplete or stale — verify before relying on them.