The README, MIT license, and matching organization-backed repository provide useful documentation and ownership context. Maintenance evidence is effectively absent, leaving this old release a poor long-term dependency choice.
38%
Total Score
50
71
75
The latest release was published on February 10, 2017, about nine years ago, and there have been no releases in the last 12 months. This strongly raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.
There were four open issues but no new or closed issues, pull requests, or merges in the last month, so reported project needs are not being actively handled.
Composer build tooling is present, supporting reproducible package structure, but no security scanning tools are configured, leaving a modest transparency and maintenance gap.
The repository has no security policy, which reduces clarity about vulnerability reporting and maintenance expectations, although this is secondary to the much longer inactivity risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
typo3/flow Version * | — | — |
typo3/neos Version * | — | — |
alchemy/zippy Version ~0.3 | — | — |
cocur/slugify Version ~1.4 | — | — |
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.