Risky to adopt without checking that the project is still maintained. The package has had no repository commits for the last three months and only two releases, while the linked repository does not identify or mention this package, weakening confidence that it is the correct source.
48%
Total Score
25
100
72
90
The repository recorded zero commits and zero active maintainers during the last three months. For a package only about seven months old, this is meaningful evidence of stalled maintenance.
The repository name does not match the package name and its README does not mention the package. This raises a concrete concern that the registry package may not be clearly backed by the linked source repository.
The repository is owned by an individual account rather than an organization, so the single registry maintainer is not offset by visible organization backing.
The package is about seven months old but has only two releases, both published within the same day, with no later release activity shown. This provides limited evidence of an ongoing maintenance cycle.
The repository has zero stars, forks, and watchers. Popularity is not required for health, but this provides no supporting evidence of community use or review.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
losthost/db Version ^3 | — | — |
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.