It has a clear MIT license, repository tests, and no install-time scripts or registry deprecation. Its small project footprint and absent security scanning reduce confidence in ongoing support.
48%
Total Score
50
86
75
The latest release was over five years ago, and there have been no releases in the last 12 months; this is a substantial abandonment concern despite the package having three releases.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the long release gap and indicating no observed maintenance capacity.
The repository uses Composer build tooling, but it has no detected security scanning tools; the missing scanning is a modest transparency and maintenance gap for a dependency project.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented; this matters more when the project has already shown no recent maintenance.
All six analyzed workflow action references are unpinned, weakening build reproducibility. The audit found no untrusted checkouts, script injection, high-severity findings, or incomplete workflow analysis, which keeps this as a hygiene concern rather than a severe risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
pestphp/pest Version ^1.0 | — | — |
pestphp/pest-plugin Version ^1.0 | — | — |
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.