Tests, a changelog, a clear license, and repository/package alignment support transparency. Composer setup is conventional, but the small project footprint limits confidence for long-term support.
52%
Total Score
25
100
78
75
The package has only three releases, all within four days in December 2020, and none in the last 12 months. This long release silence materially raises abandonment and compatibility risk.
There were zero commits and zero active maintainers in the last three months. Combined with the old last push, this is a clear maintenance concern.
The repository is owned by an individual user rather than an organization, so the small registry maintainer and project footprint provide limited backing for sustained maintenance.
The repository has three stars, zero forks, and two watchers. This indicates a small user and contributor footprint, providing little supporting evidence of long-term resilience.
The repository uses Composer, which is appropriate for the package ecosystem, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of abandonment by itself.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms Version 8.7.* | — | — |
typo3/cms-fluid Version 8.7.* | — | — |
typo3/cms-extbase Version 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.