There is no security policy or automated security scanning, and the project has only one registry maintainer. Its clear README, MIT license, and lack of install scripts help, but the limited repository activity makes future compatibility uncertain.
42%
Total Score
25
100
75
75
The package has had only one release, published in October 2017, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the release history and indicating no observed ongoing maintenance.
Only one registry maintainer is listed, creating limited publishing redundancy. The repository is user-owned rather than organization-backed, so there is no provided evidence of a broader maintainer base.
The repository has modest adoption signals at 14 stars and 6 forks. This does not establish health and offers little compensation for the absence of recent maintenance.
Composer build tooling is present, but no security scanning tools were detected. For a small plugin this is a meaningful hygiene gap, though not severe on its own.
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.