The package has no releases in 16 months and no commits in the last three months, with one registry maintainer. Its MIT license, small dependency set, and matching repository provide useful transparency, but no tests or security policy add uncertainty.
58%
Total Score
38
100
83
83
The repository had zero commits and zero active maintainers in the last three months. Combined with no releases in the last year, this materially raises abandonment risk.
Only one registry account has publish access. The repository is user-owned rather than organization-backed, so there is little visible publishing redundancy if that maintainer becomes unavailable.
The repository is owned by an individual user rather than an organization. That is not inherently unhealthy, but it provides less visible institutional backing for a package with a single registry maintainer.
The package has 21 releases over about four years, but none in the last 12 months; the latest release was about 16 months ago. This is meaningful evidence of slowing or stopped maintenance.
There are no open issues or pull requests and no recent issue or pull request activity. This is consistent with a small project but offers no evidence of active community maintenance.
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.