The package is small but clearly documented, has a changelog, a stable release, and no install-time scripts. Its licensing record is inconsistent, and the linked repository has little visible project activity or package identification, which weakens confidence in long-term support.
58%
Total Score
75
100
75
88
The artifact includes an MIT license file, but the manifest declares the package proprietary. That mismatch reduces licensing transparency even though the release is not unlicensed.
Only two releases exist over roughly one year, with the latest released about nine months before collection. That is limited evidence of an established maintenance cadence.
The repository shows zero commits and zero active maintainers in the three months measured. Together with the sparse release history, this is a meaningful maintenance concern.
The repository name does not match the package name and its README does not mention the package. That makes the package-to-source relationship less clear and warrants caution.
Composer is used for builds, but no security-scanning tools are present. The missing scanner is a hygiene gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^3.7 || ^4.0 || ^5.0 | — | — |
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.