The package includes a clear README, tests, and an MIT license. A single maintainer and minimal repository use leave limited evidence of ongoing support; the workflow also uses unpinned actions.
61%
Total Score
50
100
86
75
Only one registry account publishes the package. Because the repository is user-owned rather than organization-backed, this leaves a relatively thin visible maintainer base.
This is the package's only release, published about 12 months ago, with no releases in the last 12 months. That limits evidence of sustained maintenance, despite the stable 1.0.0 version.
There were no commits and no active maintainers during the last three months. Combined with only one release, this is meaningful evidence of limited ongoing maintenance.
Composer-based build tooling is present, but no security scanning tool was detected. This is a modest transparency gap, not a standalone reason to reject the package.
All 3 of 3 analyzed action references are unpinned, weakening build reproducibility and update control. The reported cache-poisoning issue has low confidence, so it is only a hygiene concern rather than a severe workflow risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
antlr4/antlr4 Version ^4.7 | — | — |
antlr/antlr4-php-runtime Version ^0.9 | — | — |
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.