clue/json-merge-patch

Its small, tested codebase and clear licensing reduce adoption friction. The long-standing lack of maintenance and missing security policy make future fixes and security response uncertain.

Latest v0.1.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published over 11 years ago, with no releases in the last 12 months. That strongly raises abandonment risk despite the package not being deprecated.

Repo commit activity

The repository recorded no commits and no active maintainers in the last 3 months, consistent with a project that has been inactive since its initial release. The repository is not archived, but that does not offset the prolonged inactivity.

Repo issue activity

Five issues remain open, while there were no new or closed issues and no pull-request activity in the last month. This suggests unresolved maintenance needs.

Security policy

The linked repository has no security policy, leaving no documented path for reporting or handling vulnerabilities. This matters more for a library that may process application data.

Version stability

The release is v0.1.0 rather than a stable major version, so API maturity is less certain. Its long age and absence of later releases reinforce that concern.