It has a clear README, MIT licensing, and a small dependency surface. The workflow uses two unpinned actions, and the lack of a security policy reduces transparency. The package should be treated as a maintenance liability for new projects.
45%
Total Score
25
100
75
75
Only one release exists, published about five years ago, with none in the last 12 months. This is strong evidence of abandonment risk for a dependency.
The repository had zero commits and zero active maintainers in the last three months. Combined with the old release history, this materially increases abandonment risk.
There are two open issues and no new or closed issues in the last month, showing little evidence of active issue handling.
Composer is used for builds, but no security scanning tool is configured. This is a modest transparency and maintenance gap for a package intended for application dependencies.
The linked repository is not archived, but it was last pushed about four years ago; the stale timestamp reinforces the separate maintenance concerns without making the repository formally unavailable.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^8.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.