The package has a clear README, tests in its repository, a changelog, and matching MIT licensing. Its small single-person project has gone quiet, while unpinned workflow actions and missing security scanning add maintenance and release-hygiene concerns.
58%
Total Score
50
100
81
63
The post-autoload-dump script runs code during installation, increasing install-time execution exposure. No provided signal shows that this script is unusually dangerous or unnecessary, so the effect is limited to a hygiene concern.
Only one registry account has publish access. The repository is also owned by that same individual rather than an organization, leaving limited visible continuity if the maintainer becomes unavailable.
The package and repository are backed by the same individual account, so ownership is clear, but there is no organization backing shown to provide additional continuity.
The package has five releases over about two years, but it has had no release in the last 12 months; that weakens confidence that fixes and compatibility updates will continue.
There were no commits and no active maintainers in the last three months, consistent with the broader pause in releases and raising abandonment risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^12.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.