soukicz/hyperslevy

Documentation and project safeguards are sparse for a client library, leaving consumers with little guidance or security context. The MIT license and lack of install scripts reduce adoption friction.

Latest 0.0.3

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only three releases and none in the last 12 months; its latest release was in December 2020, roughly five years and nine months before collection. This indicates a long-standing maintenance gap.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and a prolonged lack of maintenance.

Package scaffolding

The published library has no README, while the source repository also reports no tests or changelog. Missing consumer documentation is a real usability gap, although absent tests and changelogs are not unusual in small published artifacts.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these values provide little evidence of community adoption or review.

Security policy

The source repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This is a transparency gap, though it is less severe than the clear maintenance inactivity.