The package has a README, tests, a stable version, and a repository that matches its name. Workflow dependencies are all unpinned, and no security policy is published, leaving avoidable maintenance and build-integrity gaps.
65%
Total Score
63
100
94
67
A single registry maintainer is consistent with the linked repository being user-owned, but it leaves limited visible publishing redundancy.
The latest registry release was over two years ago, with no releases in the last 12 months. This indicates a substantial release-maintenance gap, although the repository was pushed more recently.
There were no commits and no active maintainers during the last three months. Combined with the stale registry release history, this raises concern about ongoing maintenance.
There is one open issue and one open pull request, but no issues or pull requests were opened or merged in the last month. This offers little evidence of an active contributor community.
No security policy is present in the repository. For a small development-time testing extension this is a transparency gap, but it is not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^v6.4.3 | — | — |
phpunit/phpunit Version ^11.0.4 | — | — |
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.