RepoPilot

jakewharton/butterknife vs lihengming/spring-boot-api-project-seed

jakewharton/butterknife shows stronger signals overall

As of June 2026, butterknife shows healthier maintenance signals than spring-boot-api-project-seed. butterknife rates Healthy overall while spring-boot-api-project-seed rates Concerns. butterknife last saw a commit 2 years ago with 17+ active contributors, while spring-boot-api-project-seed last saw a commit 2 years ago with 3+ 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.

jakewharton/butterknife

Healthy

Healthy across all four use cases

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.

  • Stale — last commit 3y ago
  • Concentrated ownership — top contributor handles 75% of recent commits
  • 17 active contributors
  • Apache-2.0 licensed
  • CI configured
  • Tests present

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

lihengming/spring-boot-api-project-seed

Concerns

Stale and unlicensed — last commit 2y ago

ConcernsDependency

no license — legally unclear; last commit was 2y ago…

ConcernsFork & modify

no license — can't legally use code; no CI workflows detected…

HealthyLearn from

Documented and popular — useful reference codebase to read through.

ConcernsDeploy as-is

no license — can't legally use code; last commit was 2y ago…

  • Stale — last commit 2y ago
  • Small team — 3 contributors active in recent commits
  • Single-maintainer risk — top contributor 91% of recent commits
  • No license — legally unclear to depend on
  • No CI workflows detected
  • 3 active contributors
  • Tests present

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

butterknifespring-boot-api-project-seed
Stars25,3779,707
Last commit2y ago2y ago
LicenseApache-2.0
Open issues119112
Has tests
Has CI
Test coverage57%100%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsConcerns signals

Want the full analysis? jakewharton/butterknife · lihengming/spring-boot-api-project-seed

Ask AI about jakewharton/butterknife vs lihengming/spring-boot-api-project-seed

Open the chat with a comparison question pre-filled.