The package is small and focused, with tests, a README, a stable release, and a clear MIT declaration. Its maintenance pace and workflow pinning leave more operational risk than a mature dependency.
62%
Total Score
50
86
50
Only two releases have been published, with no releases in the last 12 months and a median interval of about 389 days. This suggests a slow maintenance cadence, though the package is not necessarily abandoned.
There were no commits and no active maintainers in the last three months. This is a meaningful maintenance warning, although the recent repository push shows the project has not been abandoned outright.
The repository uses Composer build tooling, but no security scanning tools were detected. For this small package that is a hygiene gap rather than a severe dependency risk.
The repository has no security policy. This weakens disclosure transparency but does not by itself indicate that the release is unsafe to depend on.
The sole workflow uses a pull_request_target trigger without an untrusted checkout or script-injection sink, so that trigger is not concerning on its own. However, all three action references are unpinned, reducing build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
league/flysystem Version ^3.10.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.