Package Health/cryonighter/currency-converter

cryonighter/currency-converter

Usable with caveats: it is a small, clearly packaged library with documentation, tests, a license, and no deprecation or workflow red flags. However, its only release was over four years ago and the repository has had no recent commits, so ongoing compatibility and maintenance are uncertain.

Latest 1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old last push and release, this is the strongest evidence of weak ongoing maintenance.

Project backing

The registry namespace and repository owner match, and the owner is an individual rather than an organization. That is consistent ownership evidence, but it offers less organizational continuity if the maintainer becomes unavailable.

Release history

The package has only one release, published over four years ago, with no releases in the last 12 months. That limits evidence of ongoing compatibility work and increases maintenance risk.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not decisive for a small package, but this provides little supporting evidence of broad review or community resilience.

Repo tooling

Composer is used for the build, but no security scanning tool is configured. The missing scanner is a transparency gap, though it is not by itself evidence that the package is unsafe.