Its clear README, explicit license, and single runtime dependency reduce integration uncertainty. Limited repository activity and the absence of tests leave maintenance risk unresolved.
42%
Total Score
75
100
64
75
The latest release was published about eight years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having eight releases overall.
One issue and one pull request remain open, with no new or closed issues or pull requests in the last month. This suggests unresolved maintenance work rather than active stewardship.
The repository has one star, zero forks, and two watchers. Low adoption is only supporting evidence, but it provides little external maturity signal for an otherwise inactive project.
Composer is used for builds, but no security-scanning tooling is present. The missing scanner is a hygiene limitation, not evidence that the release is unsafe by itself.
The repository is not archived, which preserves a path for future maintenance, but its last push was about eight years ago and does not offset the prolonged inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-frontend Version ^6.2 || ^7.6 || ^8.7 | — | — |
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.