The MIT license, release notes, repository tests, and matching source make the package transparent. Its small maintainer base and absent security tooling add modest ongoing risk.
58%
Total Score
50
100
88
75
Only one account has registry publish access. That is a thin publishing base for a package with no recent activity, increasing continuity risk, although it does not by itself establish poor project backing.
The registry namespace and repository owner match, and the owner is a user account rather than an organization. This supports repository identity but offers limited evidence of organizational continuity.
The package has 13 releases but none in the last 12 months, and its latest release was over two years ago. This points to a materially increased maintenance and abandonment risk.
There were no commits and no active maintainers in the last three months, consistent with the package's long release gap and indicating substantially reduced maintenance capacity.
The repository uses Composer build tooling, but no security-scanning tools were detected. For a Composer plugin involved in package downloads, this leaves a meaningful security-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.