RepoPilot

mantinedev/mantine vs siyuan-note/siyuan

Both showing Mixed signals — pick on fit, not health

As of September 2026, mantine and siyuan both show mixed maintenance signals. mantine was committed to 2 weeks ago with 13+ active contributors, while siyuan was committed to 4 days ago with 2+ active contributors. mantine is MIT-licensed while siyuan is AGPL-3.0-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.

mantinedev/mantine

Mixed

Single-maintainer risk — review before adopting

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; 3 cyclic import chains — pervasive coupling

  • Single-maintainer risk — top contributor 86% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit 1w ago
  • 13 active contributors
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is Mixed to Healthy 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

siyuan-note/siyuan

Mixed

Single-maintainer risk — review before adopting

ConcernsDependency

copyleft license (AGPL-3.0) — review compatibility; top contributor handles 94% of recent commits…

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Token-Permissions" is 0/10; dependency CVE scan unavailable

  • Small team — 2 contributors active in recent commits
  • Single-maintainer risk — top contributor 94% of recent commits
  • AGPL-3.0 is copyleft — check downstream compatibility
  • Last commit today
  • 2 active contributors
  • AGPL-3.0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

Signal-by-signal breakdown

mantinesiyuan
Stars31,68546,320
Last commit15d ago4d ago
LicenseMITAGPL-3.0
Open issues6419
Has tests
Has CI
Test coverage14%49%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeB
Cycles3
Bottom-lineMixed signalsMixed signals

Want the full analysis? mantinedev/mantine · siyuan-note/siyuan

Ask AI about mantinedev/mantine vs siyuan-note/siyuan

Open the chat with a comparison question pre-filled.