Healthy and suitable to depend on, with a small maintainer base as the main caveat. It has frequent stable releases, active repository work, matching source code with tests, and automated security checks.
82%
Total Score
70
100
100
80
Only one registry account has publishing access, creating concentration risk. This is partly offset by the repository's recent release and commit activity, but the publishing base remains narrow.
The registry namespace and repository are owned by the same individual account, confirming ownership alignment but offering less continuity assurance than organization backing.
All five recent commits came from one contributor, so maintenance could be disrupted if that person becomes unavailable. The individual-owned project backing does not provide evidence of organizational handoff capacity.
The repository has no published security policy, which makes vulnerability reporting and response expectations less transparent.
All workflows declare permissions, and half use read-only permissions; four workflows request top-level write access, which is broader than ideal but is explicitly configured rather than left unspecified.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^1.1.2 || ^2.0.2 | — | — |
laminas/laminas-i18n Version ^2.33.0 | — | — |
laminas/laminas-view Version ^2.44.0 | — | — |
laminas/laminas-stdlib Version ^3.21.0 | — | — |
mimmi20/mezzio-navigation Version ^5.0.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.