onetoweb/multivers

The stable 1.0.1 release has a matching, organization-backed repository, a license file, and a small dependency surface. Its short README and limited project safeguards leave little guidance or evidence for long-term support.

Latest v1.0.1

Packagist

43%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only two releases, both in January 2023, with no releases in the last three years. That strongly limits evidence of ongoing maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in January 2023. This is a substantial abandonment concern.

Package scaffolding

The artifact includes a README, but it is only 113 characters and points consumers to an example rather than documenting the client in depth. No tests or changelog are expected in the published artifact, so those absences are not concerns.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. This is a modest transparency and maintenance gap, not evidence that the release is unsafe.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. For an API client, that is a real but secondary maintenance gap.