Usable with caveats: the release is well-scaffolded, clearly backed by an organization, and actively developed, but it is only 34 days old and all recent commits come from one contributor. Missing security scanning and a security policy add transparency concerns.
68%
Total Score
83
100
88
75
The package is only 34 days old with seven releases, and the median release interval is about 14 hours. This shows active iteration but provides little long-term maintenance history.
One contributor made all 11 commits in the last three months. Organization backing provides some handoff capacity, but no second active contributor is shown, leaving a meaningful concentration risk.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces supply-chain transparency for a package handling uploads and storage.
No SECURITY.md or equivalent security policy was found, so the project provides no clear documented channel or process for reporting vulnerabilities.
Two workflows lack top-level token permissions, and the release workflow declares write access. This is not an observed exploit, but the workflow permission posture is less restrictive than ideal.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^13.0 | — | — |
league/flysystem-aws-s3-v3 Version ^3.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
league/flysystem-path-prefixing Version ^3.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.