back/laravel-filesystem-obs
The release has a clear MIT license, usable README, changelog, and release notes. Maintenance is thin: no releases in the last 12 months, no commits in three months, one publisher, no tests or security scanning, and the repository does not identify this package.
55%
Total Score
50
100
75
75
Health Score Breakdown
Only one registry account has publish access. That is a limited publishing base and provides little resilience if the maintainer stops releasing.
The repository is owned by an individual user rather than an organization, so the single registry maintainer does not benefit from clear organizational backing.
The package has existed since December 2021 and has seven releases, but it had no releases in the last 12 months; this indicates stalled maintenance for a dependency release.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release-history evidence of stalled maintenance.
The repository name does not match the package name and its README does not mention the package. That makes package-to-source ownership unclear and weakens transparency.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 back |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.4 | — | — |
illuminate/filesystem Version ^11.45 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 4 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.