MIT licensing, release notes, and a repository that clearly matches the package support transparency. The single-maintainer project shows limited recent activity, and all three workflow actions are unpinned.
60%
Total Score
50
94
50
One registry maintainer creates a thin publishing base. The linked repository is user-owned rather than organization-backed, so there is no provided compensating backing signal.
The package has only four releases, with none in the last 12 months and the latest published about 2 years 6 months ago. This indicates slowing maintenance, although the repository was pushed more recently than the last registry release.
The repository recorded zero commits and zero active maintainers in the last 3 months. That weakens evidence of ongoing maintenance for a package whose latest registry release is already about 2 years 6 months old.
No repository security policy was found, which is a modest transparency gap for vulnerability reporting. The repository does use Dependabot, providing some compensating security tooling.
The single workflow was fully analyzed with no injection or high-severity findings, but all 3 action references are unpinned, leaving build inputs less reproducible. The absence of a top-level permissions block is not a concern by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^9.0|^10.0|^11.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.