Documentation and packaging are solid, and the repository remains linked to an organization with tests and security tooling. The main concern is the lack of registry releases for over two years, alongside weak workflow pinning and a high-confidence bot-condition warning.
58%
Total Score
63
100
89
83
The package defines a post-autoload-dump install-time script. This deserves awareness because Composer lifecycle scripts execute during installation, but the signal alone does not establish a serious health risk.
Only one registry account has publish access, which is a limited publishing base. The organization-backed repository provides some compensation, so this is not a severe concern.
The package has had no registry release in the last 12 months, and its latest release was in April 2024. This indicates stalled delivery despite the repository remaining available.
There were no commits and no active maintainers in the last three months. The recent repository push partially offsets this, but the lack of current commit activity still points to limited maintenance momentum.
There are no open issues and one open pull request, with no new or closed issues in the last month. This is compatible with a quiet small project but does not demonstrate active support.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/pennant Version ^v1.7.0 | — | — |
illuminate/support Version ^v11.4.0 | — | — |
spatie/laravel-package-tools Version ^1.16.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.