The repository has no recent commits and only one published release, leaving little evidence of ongoing maintenance. Workflow permissions and unpinned actions add avoidable supply-chain hygiene concerns, despite clear documentation, tests in the repository, and an MIT license.
45%
Total Score
0
89
50
There were zero commits and zero active maintainers in the last three months, consistent with a project that has stopped receiving maintenance.
This is the package's only release, published about two years ago, with no releases in the last 12 months. That provides little evidence of continued maintenance.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this offers no visible community cushion for an inactive package.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, but it is less significant than the maintenance evidence.
All 12 action references are unpinned, three workflows grant top-level write permissions, and a high-confidence bot-conditions finding affects the Dependabot auto-merge workflow. No untrusted checkout or script injection was found, so this is a hygiene concern rather than a standalone severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0|^11.0 | — | — |
league/flysystem Version ^3.0 | — | — |
guzzlehttp/guzzle Version ^7.2 | — | — |
illuminate/support Version ^10.0|^11.0 | — | — |
illuminate/contracts Version ^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.