RepoPilot

jgthms/bulma vs picocss/pico

Both showing Mixed signals — pick on fit, not health

As of September 2026, bulma and pico both show mixed maintenance signals. bulma last saw a commit 6 months ago with 16+ active contributors, while pico last saw a commit 4 months ago with 17+ active contributors. Both use the MIT 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.

jgthms/bulma

Mixed

Slowing — last commit 6mo ago

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

last commit was 6mo ago; Scorecard "Branch-Protection" is 0/10…

  • Slowing — last commit 6mo ago
  • Concentrated ownership — top contributor handles 79% of recent commits
  • Scorecard: marked unmaintained (0/10)
  • Scorecard: default branch unprotected (0/10)
  • Last commit 6mo ago
  • 16 active contributors
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days; 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

picocss/pico

Mixed

Slowing — last commit 4mo ago

MixedDependency

no tests detected in the complete Git tree; no CI workflows detected

HealthyFork & modify

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

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No blocking repository-level signals were found; deployment review is still required.

  • Slowing — last commit 4mo ago
  • Concentrated ownership — top contributor handles 78% of recent commits
  • No CI workflows detected
  • No tests detected in the complete Git tree
  • Scorecard: marked unmaintained (0/10)
  • Last commit 4mo ago
  • 17 active contributors
  • MIT licensed

What would improve this?

  • Use as dependency Mixed to Healthy if: add a test suite

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

bulmapico
Stars50,06516,827
Last commit6mo ago4mo ago
LicenseMITMIT
Open issues527124
Has testsNo
Has CINo
Test coverage48%0%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineMixed signalsMixed signals

Want the full analysis? jgthms/bulma · picocss/pico

Ask AI about jgthms/bulma vs picocss/pico

Open the chat with a comparison question pre-filled.