Filesystem pattern - the seven operations every storage backend can honour, plus an opt-in capability for the ones that can describe a path.
78%
Total Score
healthy
A clean, tested release from an organization-backed repository, but it has almost no track record yet.
The package is only 0 days old with two releases, so there is too little history to establish long-term maintenance reliability. The recent second release shows active initial development but does not offset the limited track record.
There were no commits or active maintainers in the last 3 months, but the package is only 0 days old and the repository was pushed recently. This is insufficient history rather than evidence of abandonment.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest supply-chain hygiene gap, not a standalone adoption blocker.
The repository has no security policy. For a small contracts-only package this limits vulnerability-reporting transparency, but the package's scope keeps the impact modest.
We didn't find any vulnerabilities for this package.
No maintainer information available.
No direct dependencies.
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.