Which has better activity and maintenance signals?

Based on the RepoPilot analysis and repository metadata:

kerryjiang/supersocket shows stronger maintenance signals:

1. Architecture Grade: A (100/100) — The import graph shows 0 import cycles, 13 files parsed, and 11 internal imports, indicating clean, well-structured code with no architectural debt.

2. Security posture: 0 critical, 0 high, and 0 moderate CVEs across 75 scanned dependencies, with 0 critical/high in direct dependencies—a strong security baseline.

3. Build infrastructure: Active CI/CD with GitHub Actions workflows for builds (per the README badge).

4. Community traction: 4,232 stars and 1,165 forks on GitHub, suggesting sustained interest and adoption.

5. Documentation: Dedicated project homepage and documentation site (supersocket.net, docs.supersocket.net).

However, maintenance weaknesses exist:

• OpenSSF Scorecard is only 3.5/10, with critical gaps: no dependency update tool (0/10), no security policy document (0/10), and no SAST scanning (0/10).

lykosai/stabilitymatrix data is limited: The repository_data block provides only the README excerpt with build badge and Discord link; no RepoPilot signals (architecture grade, dependency CVEs, security scorecard) are available, so I cannot make a direct comparison on maintenance rigor.

Verdict: SuperSocket shows measurably better architecture health and security scanning coverage, but both repos lack formal security policies and automated dependency updates—typical gaps in open-source projects.

FOLLOW_UPS:

• What's SuperSocket's typical release cycle?
• Does SuperSocket use dependabot or similar tools?
• What security advisories affect SuperSocket's dependencies?