league/flysystem
Healthy and suitable to depend on. It has a long release history, frequent recent releases, active contributions from eight people, clear licensing, and strong repository hygiene; the only notable gap is that its workflows do not declare top-level token permissions.
92%
Total Score
100
100
94
90
Health Score Breakdown
The project uses Composer build tooling, but no security scanning tools were detected. This is a modest transparency gap, partially offset by the repository's other security and workflow evidence.
All three workflows lack top-level token permissions declarations, so their default token access is less explicit than ideal. However, none declares top-level write permissions, limiting the severity of this workflow-hygiene gap.
Vulnerabilities
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-155029 league/flysystem is vulnerable to Improper Input Validation in versions 0.1.0 - 3.35.2. | 0.1.0 - 3.35.2 | Medium |
CVE-2021-32708 league/flysystem is vulnerable to Time-of-check Time-of-use (TOCTOU) Race Condition in versions 0.0.0 - 1.1.4 and 2.0.0 - 2.1.1. | 0.0.0 - 1.1.42.0.0 - 2.1.1 | Critical |
Package versions
Maintainers
 Frank de Jonge |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 league/flysystem-local Version ^3.0.0 | — | — |
league/mime-type-detection Version ^1.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 19 days ago
- Created
- 12 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.