MIT licensing, tests, and a two-dependency footprint support straightforward evaluation. There is no security policy, and the project shows little adoption, so maintenance expectations should remain modest.
40%
Total Score
75
100
79
75
The latest release was about 7 years and 11 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency, despite seven historical releases.
There were no commits or active maintainers in the last 3 months, reinforcing the evidence that development has stopped. This materially raises maintenance and abandonment risk.
The repository has only 2 stars, 0 forks, and 1 watcher. Low adoption is supporting caution about maturity and community resilience, though popularity alone is not decisive.
Composer is used as the build tool, but no security scanning tools are present. The missing scanning is a hygiene gap for a package with no recent maintenance.
No repository security policy was found, leaving vulnerability-reporting expectations undocumented. This is a transparency gap, although it is less significant than the long-term inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
toolkit/file-utils 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.