The package has a clear README, an explicit MIT license, and only two runtime dependencies. Limited testing, security tooling, and maintainer capacity leave more maintenance work for adopters.
63%
Total Score
50
100
93
50
The package runs a post-autoload-dump install-time script. Lifecycle execution deserves attention because it runs during installation, although this signal does not show that the script is harmful.
Only one registry account has publish access, so publishing capacity is concentrated in a single person. The linked repository is also user-owned rather than organization-backed, leaving limited visible redundancy if that maintainer becomes inactive.
The repository recorded zero commits and zero active maintainers in the last three months, despite recent registry releases. That mismatch weakens confidence that source maintenance is keeping pace with publishing.
There were no new or closed issues or pull requests in the last month, and no open issues or pull requests. This may reflect a small, quiet project, but it provides little evidence of active community maintenance.
Composer is used as the build tool, but no security scanning tools are present. The missing scanning is a maintenance and transparency gap, though it is not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^10.0|^11.0|^12.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.