The package has clear licensing, substantial documentation, tests, and source that matches its published identity. A single maintainer and no security policy or scanning reduce confidence for a developer tool with broad framework dependencies.
58%
Total Score
50
100
79
75
One registry maintainer is consistent with a small user-owned project, but it also indicates a thin publishing base and limited continuity if that maintainer becomes unavailable.
The registry namespace and repository are owned by the same individual account, providing consistent ownership context but no organizational backing to broaden maintenance capacity.
This is the package's only release, published 489 days ago, with no releases in the last 12 months. That leaves maintenance continuity unproven.
There were zero commits and zero active maintainers in the last three months. Combined with the single-release history, this is meaningful abandonment risk.
There were no new or closed issues or pull requests in the last month. With no open backlog this is not itself negative, but it provides no evidence of active community maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
pestphp/pest Version ^1.22|^2.8.1|^3.0 | — | — |
symfony/finder Version ^5.0|^6.0|^7.0 | — | — |
phpunit/phpunit Version ^9.5.10|^10.1|^11.0|^12.0 | — | — |
laravel/framework Version ^8.0|^9.0|^10.0|^11.0|^12.0 | — | — |
pestphp/pest-plugin-arch Version ^2.0|^v3.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.