miguelenred/jsonsqldb

Healthy and usable, with caveats: it has strong documentation, tests, a changelog, clear licensing, and active recent development. It is only 20 days old and all 35 recent commits come from one contributor, so long-term stability and continuity are not yet proven.

Latest v2.6.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Release history

The package has 17 releases in 20 days, showing active development, but the very short history leaves little evidence of long-term maintenance or release stability.

Repo bus factor

One contributor accounts for 100% of the 35 recent commits. The repository is user-owned rather than organization-owned, so there is no provided organizational backing to offset this concentration.

Repo commit activity

There were 35 commits in the last three months, demonstrating active work, but only one active maintainer made them all, limiting evidence of durable maintenance capacity.

Repo popularity

The repository has 1 star, 0 forks, and 0 watchers. This is weak supporting evidence of adoption, though popularity alone is not decisive and the project is only 20 days old.

Repo tooling

The repository uses Composer build tooling, but no security scanning tool was detected. The missing scanner is a transparency gap, while the separate security policy and safe workflow configuration provide some compensation.