Tests, a changelog, a license, and regular releases provide useful maintenance evidence. Organization ownership helps, but the linked repository's lack of a package mention leaves provenance less clear. No security policy is another modest transparency gap.
65%
Total Score
75
88
50
The repository recorded zero commits and zero active maintainers in the last three months. This is a meaningful maintenance concern despite the recent release history.
The repository name does not match the package name and its README does not mention the package. Although this may reflect packaging structure, the relationship is less transparent.
Composer is used as the build tool, but no security scanning tool was detected. The missing scanning is a hygiene gap, though it is not decisive by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a modest transparency gap, not evidence of unsafe code.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.