RepoPilot

n8n-io/n8n vs solidjs/solid

Both showing Healthy signals — pick on fit, not health

As of June 2026, n8n and solid both show healthy maintenance signals. n8n was committed to today with 42+ active contributors, while solid was committed to today with 27+ active contributors. n8n is Other-licensed while solid is MIT-licensed. 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.

n8n-io/n8n

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
  • 42+ active contributors
  • Distributed ownership (top contributor 13% 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, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

solidjs/solid

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.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10

  • Concentrated ownership — top contributor handles 63% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 27+ active contributors
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is MixedHealthy 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

n8nsolid
Stars194,26235,660
Last committodaytoday
LicenseOtherMIT
Open issues1,48259
Has tests
Has CI
Test coverage100%75%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? n8n-io/n8n · solidjs/solid

Ask AI about n8n-io/n8n vs solidjs/solid

Open the chat with a comparison question pre-filled.