The project has stopped showing commit activity for about three months despite frequent releases earlier. Its organization backing, repository tests, matching source, and clear MIT licensing provide useful reassurance, while unpinned workflow actions and no security policy weaken transparency.
62%
Total Score
67
100
92
67
The repository recorded zero commits and zero active maintainers over the last three months. That is a meaningful maintenance concern, although the recent release history shows the project was active before this quiet period.
There are no open issues or pull requests and no activity in the last month. This is consistent with a small, quiet project but provides little evidence of ongoing community maintenance.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanner weakens supply-chain hygiene, without proving that the project is unsafe.
The repository has no security policy. For a small developer tool this is a transparency gap rather than a severe risk, but it leaves vulnerability-reporting expectations unclear.
All three workflows were analyzed with no dangerous audit findings and no untrusted checkout or script-injection paths. However, all seven action references are unpinned, which weakens reproducibility and action supply-chain hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
nette/utils Version ^4.1 | — | — |
behat/gherkin Version 4.10.* | — | — |
symfony/finder Version ^7.4|8.0.* | — | — |
entropy/entropy Version dev-main | — | — |
nikic/php-parser Version ^5.7 | — | — |
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.