RepoPilot

microsoft/stl vs valvesoftware/proton

microsoft/stl shows stronger signals overall

As of June 2026, stl shows healthier maintenance signals than proton. stl rates Healthy overall while proton rates Mixed. stl last saw a commit 1 month ago with 24+ active contributors, while proton last saw a commit 1 month ago with 12+ active contributors. Both use the Other 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.

microsoft/stl

Healthy

Healthy across the board

ConcernsDependency

non-standard license (Other)

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No critical CVEs, sane security posture — runnable as-is.

  • Non-standard license (Other) — review terms
  • Last commit today
  • 24+ active contributors
  • Distributed ownership (top contributor 27% of recent commits)
  • Other licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: clarify license terms

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

valvesoftware/proton

Mixed

Mixed signals — read the receipts

ConcernsDependency

non-standard license (Other); no tests detected…

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No critical CVEs, sane security posture — runnable as-is.

  • Non-standard license (Other) — review terms
  • No CI workflows detected
  • No test directory detected
  • Last commit today
  • 12 active contributors
  • Distributed ownership (top contributor 36% of recent commits)
  • Other licensed

What would improve this?

  • Use as dependency ConcernsMixed if: clarify license terms

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Signal-by-signal breakdown

stlproton
Stars11,04531,365
Last commit1mo ago1mo ago
LicenseOtherOther
Open issues5615,073
Has tests
Has CI
Test coverage36%0%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsMixed signals

Want the full analysis? microsoft/stl · valvesoftware/proton

Ask AI about microsoft/stl vs valvesoftware/proton

Open the chat with a comparison question pre-filled.