RepoPilot

ldqk/masuit.tools vs thangchung/awesome-dotnet-core

Both showing Mixed signals — pick on fit, not health

As of June 2026, masuit.tools and awesome-dotnet-core both show mixed maintenance signals. masuit.tools last saw a commit 1 month ago with 3+ active contributors, while awesome-dotnet-core last saw a commit 4 months ago with 34+ 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.

ldqk/masuit.tools

Mixed

Single-maintainer risk — review before adopting

MixedDependency

top contributor handles 98% of recent commits; no CI workflows 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.

  • Small team — 3 contributors active in recent commits
  • Single-maintainer risk — top contributor 98% of recent commits
  • No CI workflows detected
  • Last commit today
  • 3 active contributors
  • MIT licensed
  • Tests present

What would improve this?

  • Use as dependency MixedHealthy if: diversify commit ownership (top <90%)

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

thangchung/awesome-dotnet-core

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 2mo ago
  • 34+ active contributors
  • Distributed ownership (top contributor 42% 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

masuit.toolsawesome-dotnet-core
Stars6,16521,225
Last commit1mo ago4mo ago
LicenseMIT
Open issues0193
Has tests
Has CI
Test coverage29%0%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineMixed signalsMixed signals

Want the full analysis? ldqk/masuit.tools · thangchung/awesome-dotnet-core

Ask AI about ldqk/masuit.tools vs thangchung/awesome-dotnet-core

Open the chat with a comparison question pre-filled.