Healthy and suitable to use, with a concentrated maintenance base. It has a long release history, a recent release, an active repository, clear licensing, and organization backing, but all recent commits come from one contributor and the repository lacks a security policy.
78%
Total Score
70
50
89
80
The package has nine runtime dependencies, including several related Innmind components. This is a meaningful dependency surface but remains consistent with a reusable HTTP abstraction library.
Only one registry account has publishing access, which creates continuity risk. The concern is partly mitigated by the repository being owned by the Innmind organization.
One contributor made all 5 commits in the last 3 months, creating a concentrated maintenance risk. Organization ownership provides some ability to hand maintenance off, so this is a caution rather than a severe abandonment signal.
The repository received 5 commits in the last 3 months, all from one active maintainer, demonstrating recent maintenance but limited review breadth.
The repository has only 4 stars, 0 forks, and 1 watcher, so external adoption and review appear limited. Popularity is supporting evidence rather than decisive evidence, and the project otherwise shows active maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
innmind/io Version ~4.0 | — | — |
innmind/url Version ~5.0 | — | — |
ramsey/uuid Version ~4.7 | — | — |
innmind/time Version ~1.0 | — | — |
innmind/immutable Version ~6.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.