The source repository includes tests, a README, and a matching package reference, which supports practical use. Unpinned workflow actions and no security policy leave avoidable maintenance and build-transparency gaps.
66%
Total Score
50
100
88
83
The registry namespace and repository are owned by the same individual account, providing direct ownership alignment but no organizational backing or maintainer redundancy.
The package has only 2 releases across nearly 6 years, with a median interval of about 5 years, although 1 release arrived in the last 12 months. This suggests limited release maturity despite the recent update.
The repository recorded 0 commits and 0 active maintainers during the last 3 months. Combined with the long historical release interval, this is a meaningful maintenance warning.
The repository uses Make and Composer for builds, but no security-scanning tools were detected. Build tooling is present, while security-process visibility is limited.
No security policy was found. For a Composer plugin that operates on installed vendor files, this weakens vulnerability-reporting transparency.
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.