The repository is tiny and does not mention the package, while organizational backing and a matching MIT license provide useful transparency. It has no install-time scripts and only one runtime dependency, but the single registry maintainer limits resilience.
45%
Total Score
50
100
75
75
Only two releases exist, with no release in more than four years and none in the last 12 months. That is strong evidence of abandonment for a package developers may need to maintain over time.
There were no commits and no active maintainers in the last three months, consistent with the long release gap and materially increasing abandonment risk.
The repository name does not match the package name and its README does not mention the package, creating uncertainty that this repository is the intended source rather than a related or reused repository.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these values provide no evidence of an active user or contributor community.
The repository has no security policy. This is a transparency and response-process gap, though it is less serious than the demonstrated maintenance stagnation.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.