darkspock/just-query

Usable with caveats: it has a substantial, tested package with clear licensing and no deprecation, but it is a young one-release project with no commits in the last three months. The lack of security tooling and policy adds transparency risk for a database library.

Latest v1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. For a package with only one release, that is a meaningful warning about maintenance continuity.

Project backing

The registry namespace and repository owner match, but the owner is an individual rather than an organization. This is coherent ownership, yet it provides less backing capacity than an established organization.

Release history

This is a young package, about 167 days old, with only one release and no established release cadence. That limits evidence of long-term maintenance and compatibility stability.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of any adoption signal means there is little external evidence to offset the limited maintenance history.

Repo tooling

The repository uses Make and Composer, but no security-scanning tools were detected. Build tooling is present, while the missing security automation is a modest transparency gap for a database-facing library.