The package has a substantial README, broad tests, and a matching MIT license, with no deprecation or install-time scripts. Its small, inactive project has no security policy or security scanning, increasing the chance that defects remain unaddressed.
58%
Total Score
25
78
83
There were no commits and no active maintainers in the last three months. Combined with the old latest release, this is strong evidence that maintenance has stopped or is highly limited.
The registry namespace and repository owner match, and the repository is user-owned rather than organization-backed. The matching ownership supports attribution, while the individual backing offers limited visible maintenance capacity.
The package has 19 releases but none in the last 12 months, and its latest release was about five years ago. This indicates prolonged maintenance inactivity despite a previously established release history.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no community or adoption cushion for the observed inactivity.
Composer build tooling is present, but no security scanning tools are configured. For a file-upload library, this weakens ongoing vulnerability-detection practices.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
cocur/slugify Version ^4.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.