waxis/registry

The small artifact has minimal documentation and no visible security policy, making long-term use harder to assess. Its MIT license and single runtime dependency are positives, but maintenance capacity appears limited.

Latest v1.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in March 2017, and there were no releases in the last 12 months. This long gap is strong evidence of abandonment risk.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months. Combined with the last push in 2017, this indicates sustained inactivity.

Package file tree

The package contains only five files, including two source files and a configuration file. This may be sufficient for a small package, but it leaves little visible project context for evaluating maturity.

Package scaffolding

The artifact has no README, while its lack of tests and changelog is normal packaging practice. Missing consumer documentation is still a modest transparency gap for a library.

Project backing

The repository owner is an individual user rather than an organization. That is not inherently unhealthy, but it provides no visible organizational backing to offset the inactive project.