jbernavaprah/eloquent-fs
The tiny user base and absent security policy add maintenance uncertainty. A clear MIT license, tests, README, and matching repository improve transparency, but this is a poor choice for a new dependency.
42%
Total Score
64
50
Health Score Breakdown
The package has had no release in more than 5 years, with no releases in the last 12 months and only four releases overall. This is strong evidence of abandonment risk despite the stable version number.
One star and no forks show very limited adoption and community review. Popularity is supporting evidence rather than decisive on its own, but it provides little confidence to offset the stale release history.
Composer is used for the build, but no security-scanning tooling is reported. This is a modest supply-chain hygiene gap rather than evidence that the package is unsafe.
The repository is not archived, which is a meaningful counterpoint to the long release gap, but it was last pushed more than 5 years ago and does not demonstrate active maintenance.
No security policy is present. That weakens vulnerability-reporting transparency, although it is less serious than the package's lack of recent maintenance.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jure Bernava Prah |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/events Version ^8.0 | — | — |
illuminate/database Version ^8.0 | — | — |
illuminate/filesystem Version ^8.0 | — | — |
illuminate/pagination Version ^8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 5 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.