rpy/string-reverse

This is a very small, stable-major Composer package with a clear MIT declaration, no install-time scripts, an unarchived repository, and a repository that matches the package name. However, it is extremely new—released within minutes of the assessment—with no observed commit activity, no tests, README, changelog, security policy, or security scanning, and only one registry maintainer. Those gaps do not make the package unfit by themselves for such a minimal utility, but the lack of history and maintenance evidence creates meaningful adoption risk until the project demonstrates continued activity and clearer documentation.

Latest v1.1.2

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. That is a narrow publishing base and increases continuity risk, although registry access alone does not establish actual maintenance activity.

Package scaffolding

The artifact and repository contain no README, tests, or changelog. For a tiny utility this is partly understandable, but the absence of both packaged and repository tests or documentation reduces transparency and verification.

Project backing

The repository is owned by an individual user rather than an organization. Individual ownership is valid, but it provides less visible institutional continuity for a package with only one registry maintainer.

Release history

The package is brand new, with four releases published within roughly 23 minutes and no meaningful age or historical maintenance record. Rapid initial releases do not compensate for the absence of longer-term evidence.

Repo commit activity

No commits and no active maintainers were observed over the last three months. Because the project was only created recently, this is partly explained by its age, but there is still no demonstrated ongoing maintenance capacity.