The small user-owned project has little visible adoption and no current issue activity. Its clear license, README, changelog, and security policy help, but the workflow’s unpinned container image adds maintenance risk.
42%
Total Score
50
70
50
The latest release was over four years ago, with no releases in the last 12 months and only six releases overall. This is strong evidence of abandonment risk for a package still being considered for adoption.
There are no open issues or pull requests and no issue or pull-request activity in the past month. This is not inherently negative for a small stable package, but alongside the old release history it provides little evidence of ongoing maintenance.
The repository has only 3 stars, 0 forks, and 0 watchers, indicating limited adoption and community support. Popularity is supporting evidence rather than decisive on its own, but it reinforces the maintenance concern.
All three workflows were analyzed and had no untrusted checkouts or script injection, but the audit found a high-confidence unpinned container image. That is a concrete release-hygiene weakness, though not severe enough to make the package unfit by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^8.37 | — | — |
spatie/laravel-package-tools Version ^1.4.3 | — | — |
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.