bixev/firelog
The MIT license, clear README, and matching repository make inspection straightforward. Its minimal scope and lack of security scanning leave little additional assurance for a library that emits application data.
38%
Total Score
50
100
64
75
Health Score Breakdown
The package has had only two releases, both in March 2016, with no release in roughly 10 years. This is strong evidence of abandonment risk despite the stable 1.0.1 version.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since March 2016.
The repository has one star, zero forks, and one watcher, indicating very limited adoption or visible community support. Popularity is only supporting evidence, but it provides no compensating maintenance signal.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and assurance gap rather than evidence of immediate unfitness.
The repository is not archived, which avoids a stronger abandonment signal, but its last push was in March 2016 and does not offset the long inactivity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ccampbell/chromephp Version ~4.0 | — | — |
firephp/firephp-core Version ~0.4 | — | — |
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 10 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.