miaoxing/nav

The package has a clear MIT license, tests, a changelog, and an organization-backed repository that matches the package. Its small audience, absent security policy, and post-update script reduce confidence for long-term use.

Latest v0.1.64

Packagist

60%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were 0 commits and 0 active maintainers in the last 3 months, consistent with the long release pause. This is the strongest evidence of current maintenance risk.

Lifecycle scripts

The package defines a post-update-cmd lifecycle script, which adds install-time behavior that should be understood before adoption. The signal does not show that the script is harmful, so this is a limited hygiene concern.

Release history

The package has 65 releases over about 6 years, but none in the last 12 months; its latest release was about 16 months ago. This indicates a meaningful maintenance slowdown despite a previously regular median interval of about 28 days.

Repo popularity

The repository has 0 stars and 0 forks, with 1 watcher, so there is little visible external adoption or review. Popularity is supporting evidence only, but this provides little compensating assurance for the maintenance gap.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a moderate transparency gap, not evidence of a vulnerability by itself.