Voyager configuration in config files
35%
Total Score
unhealthy
One release in 922 days, no recent commits, and a linked repository that does not identify this package make adoption risky.
This is the only release, published 922 days ago, with no releases in the last 12 months. That leaves little evidence of an actively maintained release line.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the package having been inactive since its initial release.
The linked repository name does not match the package name, and its README does not mention the package. This weakens confidence that the repository is the authoritative project source.
The repository has 0 stars, 1 fork, and 1 watcher, so there is very little visible community adoption or independent scrutiny. Popularity is supporting evidence, but it reinforces the maintenance concern here.
The repository uses Composer, but no security scanning tools were detected. This is a modest build and maintenance hygiene gap.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.