It has a clear README, an exact-version GitHub release, a recent repository push, and no deprecation or archive status. The single maintainer, small user base, absent security scanning, and weak workflow pinning leave meaningful maintenance and build-integrity caveats.
72%
Total Score
50
100
88
67
Only one registry account has publish access, leaving little publishing redundancy and increasing dependence on a single person, although this does not by itself show project abandonment.
The registry namespace is organizational, but the linked repository is owned by an individual user, so the data does not show strong organizational backing for ongoing maintenance.
There were no commits and no active maintainers in the last 3 months. The recent release and repository push partly offset this, but the short-term activity remains thin.
The repository has 3 stars, 3 forks, and 1 watcher. Low popularity is only supporting evidence, but it suggests a small external user and contributor base.
Composer is used for the build, but no security scanning tools are present. The missing scanning is a hygiene weakness rather than evidence of an unsafe release on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^14.3 | — | — |
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.