File manager
34%
Total Score
33
50
78
50
Only three releases were published, all in October 2016, with no releases in the last 12 months. This is strong evidence that the package is no longer maintained.
There were no commits and no active maintainers in the last three months, consistent with the last repository push being about nine years ago. This materially raises abandonment risk.
The package declares 11 runtime dependencies, largely Laravel components, which is a substantial but coherent dependency surface for a Laravel file manager. This adds some upkeep exposure without indicating abandonment by itself.
Only one registry publishing account is listed, and the project is user-owned rather than organization-backed. This leaves limited visible publishing redundancy, though registry access records are weaker evidence than actual activity.
The registry namespace and repository owner match, and both are a personal account. This supports ownership continuity but provides no organizational backing to compensate for inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/auth Version ~5.3 | — | — |
illuminate/view Version ~5.3 | — | — |
illuminate/config Version ~5.3 | — | — |
illuminate/console Version ~5.3 | — | — |
illuminate/routing Version ~5.3 | — | — |
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.