A single registry maintainer, no security policy, and unpinned workflow actions reduce confidence in long-term upkeep. The MIT license, clear README, release notes, repository tests, and matching source repository provide useful transparency.
61%
Total Score
50
92
50
Only one registry publishing account is listed. That is a thin publishing base for continuity, although repository evidence shows an active project owner rather than an abandoned package.
The package has 15 releases over about six years, but none in the 12 months before collection and the latest release was about 17 months ago, indicating stalled maintenance.
The repository recorded no commits and no active maintainers in the last three months, which is a concrete sign that maintenance has slowed or stopped.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities in a package used within applications.
All 8 analyzed action references are unpinned, which weakens build reproducibility. The audit found no untrusted checkout, script injection, dangerous trigger, or other high-severity workflow issue.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version >=7.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.