neosloves/iconify
The focused README and small runtime dependency set make the package straightforward to assess. The repository has organization backing and remains unarchived, but the missing license and lack of recent commits weaken confidence in long-term maintenance.
57%
Total Score
75
100
78
75
Health Score Breakdown
No declared license, license file, or repository license file was detected. This is a genuine transparency and adoption concern for an open-source dependency.
This package has only one release, published 927 days ago, with no releases in the last 12 months. That is the strongest evidence of uncertain ongoing maintenance.
There were no commits or active maintainers in the last three months, consistent with a project that has been inactive since its sole release. Organization backing does not compensate for absent observed maintenance activity.
The repository has one star and no forks, providing little community evidence. Popularity is only supporting evidence, so this modestly limits confidence rather than determining the verdict.
The repository uses Composer build tooling, but no security scanning tooling was detected. The missing scanner is a hygiene gap rather than evidence that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 neos/flow Version * | — | — |
iconify/json Version ^2.2 | — | — |
iconify/json-tools Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 2 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.