kherge/json

Clear licensing, tests, and a focused package structure make the release straightforward to inspect and integrate. Maintenance has effectively stopped for over six years, with one registry maintainer and no security policy, so pinning this version carries meaningful aging risk.

Latest 3.0.1

Packagist

55%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access. Because the repository is owned by that same individual rather than an organization, the narrow publishing base adds continuity risk.

Release history

The latest release was published over six years ago, with no releases in the last 12 months. This is strong evidence of an aging project, though the stable 3.0.1 release may still be suitable if its dependencies remain compatible.

Repo commit activity

The repository had no commits and no active maintainers in the last three months, consistent with the release history showing maintenance ended over six years ago.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and no open work remains. Alongside the absent recent commits, this supports a conclusion of inactivity rather than active maintenance.

Repo tooling

The project uses Composer, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not a severe risk on its own.