The package is licensed, documented, and backed by repository tests. Its single release and no commits for nearly five years make future compatibility and maintenance uncertain; unpinned workflow actions add a smaller supply-chain hygiene concern.
40%
Total Score
33
100
81
67
Only one release exists, published nearly five years ago, with no releases in the last 12 months. This provides little evidence of ongoing compatibility maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with prolonged inactivity and substantial abandonment risk.
Only one registry account has publish access. This is a thin publishing base and increases continuity risk when the repository also shows no recent activity.
The repository is owned by an individual user rather than an organization, so the one-person registry maintainer base is not offset by organizational backing.
Composer build tooling is present, but no security-scanning tooling was detected. That is a modest transparency and maintenance gap, not evidence that the package is unsafe by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
pestphp/pest Version ^1.0 | — | — |
pestphp/pest-plugin Version ^1.0 | — | — |
cerbero/octane-testbench 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.