becker/conversion

The package is well documented, licensed, and has a very small dependency footprint. Its source has seen no commits or active maintainers for over six years, with little adoption and no security policy, so future compatibility and maintenance are uncertain.

Latest v1.0.3

Packagist

48%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only four releases, all clustered in January 2020, with no releases in the last 12 months and no later release activity. This is strong evidence of abandonment for a library consumers may need to keep compatible.

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the last push occurring in January 2020. No provided maintenance signal compensates for this prolonged inactivity.

Project backing

The repository is owned by the same individual namespace as the package, providing consistent ownership context. It does not provide organization-level backing or evidence of a broader maintenance team.

Repo popularity

The repository has 1 star, 1 fork, and 0 watchers, indicating very limited adoption and little visible community support. Popularity is supporting evidence rather than decisive on its own, but it reinforces the maintenance concern.

Repo tooling

The repository uses Composer build tooling, but no security scanning tools are reported. The missing scanning is a modest hygiene gap rather than a standalone dependency risk.