The MIT license and matching license file make reuse clear, while the repository remains unarchived. Its small artifact omits a README, but the source repository includes one; workflow pinning and security-policy gaps add little weight.
18%
Total Score
75
70
50
Packagist marks the entire package abandoned and provides azure-oss/storage-blob-flysystem as a replacement. This is a severe dependency risk even though the repository remains available.
The package has existed since 2018 with 28 releases, but only one release occurred in the last 12 months. That indicates reduced release activity and adds abandonment concern.
The repository had zero commits and zero active maintainers in the last three months, despite a recent release and push. This suggests little current development capacity.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a transparency gap, but it does not outweigh the package-level abandonment status.
The only workflow was fully analyzed with no dangerous triggers or audit findings, but its one action reference is unpinned. That is a minor reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
league/flysystem Version ^3.10.0 | — | — |
microsoft/azure-storage-blob Version ^1.1 | — | — |
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.