The repository includes tests, a README, and Psalm scanning, providing useful maintenance evidence. However, every workflow action is unpinned and the project has no published security policy.
42%
Total Score
0
71
50
This is the only release, published nearly five years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a package still at an early version.
There were no commits and no active maintainers in the last three months. This confirms that current maintenance activity has effectively stopped.
The repository is not archived, which avoids a severe abandonment signal, but its last push was nearly five years ago and does not offset the stale release history.
No security policy is published. For a package handling filesystem and cache operations, this is a transparency gap, although it is less severe than the absence of maintenance.
The package remains at v0.1.0 and is not marked as a stable major release. Combined with the lack of subsequent releases, this limits maturity evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
league/flysystem Version ^2.3.2 | — | — |
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.