Gestion des fichiers et répertoires
55%
Total Score
caution
A single release and no recent commits point to an inactive 0.0.1 package.
The registry namespace and repository owner match, but the owner is an individual account rather than an organization. This provides limited backing evidence without proving abandonment.
This is the only release, published about 19 months ago, with no releases in the last 12 months. That limited history and long silence reduce confidence in ongoing maintenance.
There were no commits and no active maintainers in the last three months. Combined with the single-release history, this is meaningful evidence of currently inactive maintenance.
Composer is used for the build, but no security scanning tool was detected. This is a transparency and hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. For a library, that leaves vulnerability-reporting expectations unclear and modestly lowers maintenance transparency.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
nesbot/carbon Version ^1.39 | — | — |
league/flysystem Version ^3.29 | — | — |
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.