There has been no release since January 2022 and no repository activity is shown after May 2022; the project also lacks a security policy. The MIT license, focused dependency profile, matching repository, and consumer README provide useful transparency but do not offset the long inactivity.
42%
Total Score
50
100
71
88
The package has only two releases, with the latest in January 2022 and none in roughly four years. This is strong evidence of abandonment risk for a dependency.
Only one registry maintainer is listed. This is a thin publishing base, though the repository is owned by the same individual and the registry list alone does not establish maintenance activity.
The repository is owned by an individual rather than an organization, so there is no demonstrated organizational maintenance backing. This matters alongside the stale release and repository activity.
There are no open issues or pull requests and no recent issue activity. This does not prove abandonment by itself, but it offers no evidence of an active maintenance loop.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of community adoption or review.
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.