Its MIT licensing, focused scope, and single runtime dependency make adoption straightforward. Maintenance evidence is dated, and the repository does not clearly identify this package in its README. The missing security policy adds a smaller transparency concern.
57%
Total Score
50
100
81
75
The package has 13 releases over about 26 months, but no releases in the last 12 months; the latest release was about 19 months ago. This indicates a meaningful maintenance slowdown, though the release history was initially active.
There were no commits and no active maintainers in the last three months, consistent with the broader absence of releases for about 19 months. For a maintained dependency, this raises abandonment risk.
The repository name does not match the package name and its README does not mention the package. Because this makes package ownership less clear, it adds a transparency concern even though the repository otherwise contains the package files.
The repository uses Composer, which fits the package ecosystem, but no security scanning tools were detected. This is a modest repository hygiene gap rather than evidence of an unsafe release.
The repository has no security policy. That weakens vulnerability-reporting transparency, although it is a smaller concern than the inactive maintenance signals.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
magento/framework Version * | — | — |
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.