Its single runtime dependency keeps the integration surface small. The stable version and unarchived repository offer limited reassurance because development stopped after March 2018 and the package has no license or consumer documentation.
40%
Total Score
50
100
42
75
Neither the registry metadata nor the package or repository contains a recognized license. That leaves developers without clear permission to use or redistribute the code.
The package has had no release in more than eight years, with only three releases overall and none in the last 12 months. This is strong evidence of abandonment risk despite the short early release interval.
The artifact has no README, tests, or changelog, and the repository also reports none; the missing README reduces consumer transparency while the absent tests increase maintenance uncertainty.
The repository is owned by an individual user rather than an organization. This does not prove poor maintenance, but there is no organizational backing signal to compensate for the project's inactivity.
There are no open issues or pull requests and no issue or pull-request activity in the last month. With the repository last pushed in 2018, this is consistent with an inactive project rather than merely a quiet current release.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
eelf/net Version ^1.0.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.