The package has had no release or commit activity for more than two years, and one person maintains a very small project without security scanning. Its stable version, clear README, license, minimal dependency set, and non-deprecated, non-archived status reduce but do not remove maintenance risk.
58%
Total Score
50
100
86
83
One registry maintainer is consistent with a small owner-led package, but it leaves limited visible publishing capacity when combined with the absence of recent activity.
The latest release was 2 years and 6 months ago, with no releases in the last 12 months. The six-release history shows prior activity but does not offset the current pause.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the long release gap and raising abandonment risk.
The repository name matches the package, supporting that it belongs to this release. Its README does not mention the exact package name, a minor transparency gap for package identification.
The repository has no security policy, which reduces disclosure transparency for a package with no other shown security-scanning process.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^10.4.43 || ^11.5.35 | — | — |
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.