Tests, release notes, and a matching source repository provide useful transparency. The lack of recent activity and unpinned workflow actions weaken maintenance and build confidence; pin this version only if its current behavior meets your needs.
64%
Total Score
50
100
88
75
The package and repository are owned by the same individual account, so the ownership relationship is transparent. It also indicates a narrow backing base rather than organizational support.
The package has 13 releases over roughly eight years, but none in the last 12 months and its latest release was about 20 months ago. This is meaningful evidence of slowing maintenance.
The repository had no commits and no active maintainers in the last three months. Combined with the long release gap, this raises abandonment risk.
Composer is used for the build, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy. That reduces transparency for reporting and handling vulnerabilities, though it is not 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.