nnvoc/router

Usable with caveats: it is actively releasing and has a matching, non-archived repository, but the project is only 7 days old and all recent commits come from one contributor. The absence of tests, changelog, and a security policy limits confidence in long-term maintenance.

Latest v1.1.3

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README is present, but neither the package nor repository includes tests or a changelog. For a reusable routing library, those omissions make behavior and release history harder to verify.

Project backing

The registry namespace and repository owner match, but both identify an individual user rather than an organization. The alignment supports authenticity of the repository link, while the individual ownership offers limited continuity assurance.

Release history

The package is only 7 days old but already has 6 releases, with the latest released very recently and a median interval of about 1.5 days. This shows active early development, though it provides little evidence of long-term stability.

Repo bus factor

One contributor made all 4 recent commits, leaving the project dependent on a single active maintainer. The repository is user-owned rather than organization-owned, so there is no provided backing signal to offset this concentration.

Repo commit activity

There were 4 commits in the last 3 months, all within the package's 7-day observed age, showing current activity but not yet demonstrating sustained maintenance.