Repository tests, a changelog, and release notes give consumers useful project evidence. The install hook and unpinned workflow actions add modest supply-chain exposure, while no security policy reduces transparency.
58%
Total Score
50
90
50
The package runs a post-autoload-dump install-time script, which adds execution during installation and modestly increases supply-chain exposure. No evidence here shows that the script is malicious or unusually broad.
The package has only two releases, both published in August 2024, with no releases in the last 12 months. This suggests limited maintenance momentum for a dependency last released about two years ago.
The repository recorded no commits and no active maintainers in the last three months, consistent with a project that is no longer actively maintained. The repository is not archived, but that does not compensate for the lack of recent activity.
The repository has no documented security policy, leaving vulnerability-reporting and response expectations unclear. This is a transparency gap, not evidence that the package is unsafe.
All four analyzed workflow action references are unpinned, which weakens build reproducibility. The audit found no untrusted checkouts, script injection, high-severity findings, or top-level write permissions, limiting the impact to caution.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
pestphp/pest Version ^2.5 | — | — |
laravel/framework Version ^10.48.9|^11.5.0 | — | — |
pestphp/pest-plugin Version ^2.0.1 | — | — |
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.