imedge/jsonrpc

The package is licensed and tested, but its README is extremely thin and no security policy is provided. Its organizational backing and clean workflow audit reduce, but do not erase, the maintenance concern.

Latest v0.8.0

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact includes tests and the repository contains test files, which supports basic project maturity. The 14-character README is too thin for a library consumers must integrate, while the missing changelog is normal packaging practice.

Release history

There have been no releases in the last 12 months, despite eight releases overall and a recent release on August 11, 2025. This indicates a meaningful maintenance slowdown for a package still at version 0.8.0.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months, which supports the concern that development has gone quiet. The recent release and non-archived repository provide limited counterweight.

Repo package mention

The repository name matches the package name, so the source appears appropriately linked. Its README does not mention the package, which is a minor documentation gap rather than a repository-identity concern here.

Security policy

No security policy was found in the repository, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, not evidence of malicious behavior.