The linked project has tests, a README, an MIT license, and a GitHub release for this version. Its repository has had no commits for about six months, and the package is not named or mentioned in that repository; the missing security policy adds a smaller transparency concern.
58%
Total Score
25
100
75
75
There were no commits and no active maintainers in the last three months. For a package this young, that is a meaningful abandonment warning.
The package is backed by an individual GitHub user rather than an organization, so the single registry maintainer represents a genuinely narrow ownership base.
The package is only about six months old and has three releases, but all three arrived within about 25 minutes, so there is not yet a sustained release pattern.
The repository name does not match the package name and its README does not mention the package. This makes the package-to-source relationship unclear and raises a piggybacking concern.
The repository uses Composer, but no security-scanning tool was detected, leaving a modest repository hygiene gap.
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.