The package is small, clearly identified, documented, and has only one runtime dependency. Its repository has no tests, changelog, security scanning, or security policy, leaving limited evidence of ongoing care.
42%
Total Score
25
100
64
83
Only two releases were published, both in March 2018, and there have been no releases in about eight years. This strongly raises abandonment risk for a dependency, despite the stable 1.0.1 version.
There were zero commits and zero active maintainers in the last three months, with the repository last pushed about eight years ago. This is the strongest evidence of abandonment risk.
The package and repository are owned by the same individual account, and the repository name matches the package. This supports provenance, but provides less organizational maintenance capacity than project backing from an organization.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these figures provide no additional community or maintenance signal.
Composer is used for the build, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
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.