icybee/module-files
The package is clearly licensed, documented, tested in its repository, and backed by an organization. Its only release was in March 2017, with no recent commits or releases, so maintenance appears abandoned despite the repository remaining unarchived.
43%
Total Score
50
100
81
67
Health Score Breakdown
This is the package's only release, published about 9 years ago, with no releases in the last 12 months. That is strong evidence of stagnation for a dependency.
There were no commits and no active maintainers in the last 3 months. Combined with the single 2017 release, this materially increases abandonment risk.
A post-autoload-dump Composer lifecycle script runs during installation. This adds installation behavior that should be understood, but the signal alone is not severe enough to make the package unfit.
The repository uses Make and Composer, showing a reproducible build and test workflow, but it has no security scanning tooling. That is a modest transparency gap rather than a decisive risk.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it is secondary to the much stronger maintenance concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Olivier Laviale |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 icanboogie/http Version ^2.5 | — | — |
icybee/module-nodes Version ^3.0 | — | — |
icybee/module-registry Version ^3.0 | — | — |
icanboogie/module-installer Version ^1.2 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 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.