The package is clearly licensed and documented, with repository tests and no install-time scripts. Its small user footprint and absent security policy reduce confidence in long-term support, while recent release activity provides some counterweight.
66%
Total Score
50
100
83
75
The registry namespace and repository owner match, but both are tied to an individual account rather than an organization, leaving a relatively narrow visible support base.
The repository recorded zero commits and zero active maintainers during the last three months. This is a meaningful maintenance concern, although the repository was pushed recently and the package has released twice in the last year.
The repository has 0 stars, 0 forks, and 1 watcher, providing little community evidence or outside support. Popularity is supporting evidence, so this lowers confidence rather than determining fitness alone.
Composer is used as a build tool, but no security scanning tools are configured. The build tooling is positive, while the missing scanning reduces repository hygiene.
The repository has no security policy. For a package that exposes file-management APIs, this leaves vulnerability-reporting and response practices undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tomk79/filesystem Version ~1.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.