RepoPilot

endoflife-date/endoflife.date vs lewagon/setup

endoflife-date/endoflife.date shows stronger signals overall

As of June 2026, endoflife.date shows healthier maintenance signals than setup. endoflife.date rates Healthy overall while setup rates Mixed. endoflife.date last saw a commit 1 month ago with 25+ active contributors, while setup last saw a commit 2 months ago with 13+ active contributors. 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.

endoflife-date/endoflife.date

Healthy

Healthy across the board

HealthyDependency

Permissive license, no critical CVEs, actively maintained — safe to depend on.

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.

  • No test directory detected
  • Last commit today
  • 25+ active contributors
  • Distributed ownership (top contributor 26% of recent commits)
  • MIT licensed
  • CI configured

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

lewagon/setup

Mixed

Missing license — unclear to depend on

ConcernsDependency

no license — legally unclear; no tests detected

ConcernsFork & modify

no license — can't legally use code; no tests detected

HealthyLearn from

Documented and popular — useful reference codebase to read through.

ConcernsDeploy as-is

no license — can't legally use code

  • No license — legally unclear to depend on
  • No test directory detected
  • Last commit 3w ago
  • 13 active contributors
  • Distributed ownership (top contributor 46% of recent commits)
  • CI configured

What would improve this?

  • Use as dependency ConcernsMixed if: publish a permissive license (MIT, Apache-2.0, etc.)
  • Fork & modify ConcernsMixed if: add a LICENSE file
  • Deploy as-is ConcernsMixed if: add a LICENSE file

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

Signal-by-signal breakdown

endoflife.datesetup
Stars3,25319,599
Last commit1mo ago2mo ago
LicenseMIT
Open issues3361
Has tests
Has CI
Test coverage0%0%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsMixed signals

Want the full analysis? endoflife-date/endoflife.date · lewagon/setup

Ask AI about endoflife-date/endoflife.date vs lewagon/setup

Open the chat with a comparison question pre-filled.