Usable with caveats: the package is only two days old and remains below a stable major release, so its long-term maintenance is unproven. It has repository tests, releases, security tooling, and active publishing, but adoption should account for its very early stage.
72%
Total Score
63
100
89
100
The registry lists one maintainer, consistent with the repository being owned by one user. This leaves limited visible publishing redundancy, but it is not by itself evidence of abandonment.
The package and repository are owned by the same individual account rather than an organization. That is coherent ownership, but it also indicates a single-person project with no demonstrated organizational backing.
This is a very new package: its first release was two days ago and it has only two releases. That shows recent publishing activity but provides little evidence of long-term maintenance or maturity.
There were no commits or active maintainers in the past three months, but the package itself is only two days old and the repository was just pushed. This is an important limitation on historical evidence, not strong abandonment evidence yet.
Version v0.2.0 is not a stable major release, which indicates an API and behavior surface that may still change. It is not marked as a prerelease, so the concern is limited to early maturity rather than release labeling.
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.