A single registry maintainer and one-star repository provide little demonstrated support capacity. The MIT license, matching repository, and lack of install scripts reduce adoption friction but do not offset the maintenance gap.
41%
Total Score
50
60
75
The latest release was published nearly six years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite 11 historical releases.
Only one registry maintainer is listed, leaving little visible publishing redundancy or support capacity. This is more concerning alongside the long release gap.
The repository has 1 star, 0 forks, and 1 watcher, so there is little observable community adoption or outside support. Popularity is supporting evidence rather than a verdict by itself.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled. The absence is a maintenance and disclosure gap, though not a severe risk alone.
Version v0.4.5 is still below 1.0, and the package has not reached a stable major release. The published project guidance also describes it as early-stage, limiting maturity confidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/inflector Version ^1.3 | — | — |
symfony/polyfill-ctype Version ^1.13 | — | — |
symfony/polyfill-php73 Version ^1.13 | — | — |
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.