decodelabs/kingdom

Clear licensing, a useful README, repository tests, and release notes support adoption. The workflow is fully unpinned and lacks a security policy, adding maintenance and build-hygiene concerns. The small dependency set and organization backing provide some context but do not offset the quiet release and commit history.

Latest v0.2.0

Packagist

66%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only three releases and no releases in the last 12 months, with the latest release about one year ago. This indicates a quiet release cadence for a relatively young package, although the regular early release interval is a modest compensating signal.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with no registry releases in the last year, this points to currently quiet maintenance and raises abandonment risk.

Repo tooling

The repository uses Composer build tooling, but no security scanning tool was detected. The missing scanner is a modest transparency and hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no published security policy. That leaves vulnerability reporting and response expectations unclear, which is a small but real transparency gap.

Version stability

Version v0.2.0 is not a stable major release, so the public API may still change. It is not marked as a prerelease, which provides limited compensation but does not remove the maturity concern.