Tests, licensing, release notes, and repository tooling provide useful maintenance evidence. The workflow uses unpinned actions, and the project has no published security policy.
52%
Total Score
50
79
75
The latest registry release was about 5 years ago, with no releases in the last 12 months. This is a substantial freshness and abandonment concern despite the package having 11 releases overall.
There were no commits or active maintainers in the last 3 months. The repository is not archived, but the absence of recent development weakens confidence in ongoing maintenance.
The repository has no security policy. This is a transparency gap, although the presence of Sonar scanning provides some compensating security practice.
Version v0.9.0 is not a stable-major release, so API compatibility may still change. It is not marked as a prerelease, which partly offsets the concern.
The sole workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, all 6 action references are unpinned, which leaves a modest supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
league/flysystem Version ^2.0 | — | — |
league/flysystem-aws-s3-v3 Version ^2.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.