flo/nimic
Composer packaging, an MIT license, and a useful README provide basic transparency. The repository has no tests or security policy, and its tooling shows no security scanning, leaving maintenance and assurance gaps.
35%
Total Score
38
100
67
83
Health Score Breakdown
The package has only one release, published over 11 years ago, with no releases in the last 12 months. This strongly suggests abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the last release being over 11 years ago, this is strong evidence of abandonment risk.
A single registry maintainer is consistent with the individually owned repository, but it leaves little visible publishing redundancy if that maintainer stops responding.
The repository is owned by an individual account rather than an organization, so the single registry maintainer offers no organizational backing to compensate for the thin maintenance base.
There are no open issues or pull requests and no activity in the last month. While this is not inherently unhealthy, it provides no evidence of an active community around the package.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Flo |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 symfony/config Version ~2.5 | — | — |
monolog/monolog Version ~1.1 | — | — |
symfony/console Version ~2.5 | — | — |
symfony/event-dispatcher Version ~2.5 | — | — |
symfony/dependency-injection Version ~2.5 | — | — |
Weekly Downloads
Info
- Last Published
- 11 years ago
- Created
- 11 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.