The MIT license, matching repository, tests, and lack of install-time scripts support adoption. A single maintainer and no security scanning limit resilience if maintenance stops.
58%
Total Score
50
86
75
The registry lists one maintainer, which leaves the project dependent on a single publisher. The linked repository is owned by the same individual, providing direct ownership but not much redundancy.
This is the package's only release, published about three years ago, with no releases in the last 12 months. That makes compatibility and ongoing maintenance uncertain.
The repository recorded zero commits and zero active maintainers in the last three months, indicating no recent development activity despite the repository remaining available.
Composer is used for the build, but no security-scanning tooling is present. The missing scanning adds a modest supply-chain hygiene gap.
The repository has no security policy, so there is no documented process for reporting or handling security issues. This is a transparency and maintenance gap, not evidence of malicious behavior.
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.