Tests, release notes, licensing, and a matching repository make the project easy to inspect. The workflow still uses a floating container image, so its build inputs should be pinned before relying on automated releases.
62%
Total Score
63
100
78
67
The package has only two releases, both dating to December 2020, with no release in the last 12 months. This long release gap materially raises abandonment and compatibility risk.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old registry release history, this supports a meaningful maintenance concern.
Composer install and update commands run post-install and post-update scripts. These scripts add supply-chain exposure compared with a package without lifecycle execution, although this signal alone does not show malicious behavior.
There are no open issues or pull requests and no recent issue or pull-request activity. For a small, stable package this is not inherently negative, but it provides little evidence of active support.
The repository has one star and one fork. This indicates limited adoption evidence, but popularity is only supporting evidence and does not outweigh the project's other signals.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/polyfill-php80 Version ^1.20 | — | — |
symfony/polyfill-mbstring Version ^1.20 | — | — |
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.