The artifact is small and focused, with a clear README, stable version, and organization-backed repository. Its lack of licensing, absent follow-up commits, and weak package-to-repository identification reduce confidence in long-term adoption.
55%
Total Score
83
100
78
83
No license declaration, license file, or repository license file was detected, leaving the legal terms for using this dependency unclear.
The package has three releases, all published within roughly 2 hours on its first release day, with no later release activity over the following 208 days. That suggests limited ongoing maintenance, though a small stable plugin may not need frequent releases.
The repository recorded zero commits and zero active maintainers during the last 3 months, indicating no observed maintenance after the initial publication.
The repository name does not match the package name and its README does not mention this package, so the linkage is not clearly demonstrated even though it is organization-owned.
Composer build tooling is present, but no security-scanning tools were detected. For this tiny plugin, the missing scanning setup is a modest transparency gap rather than a severe risk.
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.