The package includes a README, changelog, and small runtime dependency set, while its organization-owned repository remains available and matches the package. Missing security scanning and limited recent development reduce confidence in long-term maintenance.
58%
Total Score
75
100
75
75
The latest registry release was about 6 years and 9 months ago, with no releases in the last 12 months. The repository is not archived, but this release history indicates substantial abandonment risk.
There were no commits and no active maintainers in the last 3 months. This weakens evidence of ongoing maintenance, despite the repository's recent push timestamp.
Composer is used for builds, which fits the package ecosystem, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, but not severe enough to make the release unfit alone.
Version 0.3.0 is not marked as a prerelease, which avoids prerelease risk, but the sub-1.0 version signals a less mature API than a stable major release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^9.5 | — | — |
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.