The MIT license and detailed README make integration clearer, and the repository is not archived. However, the package has had no registry release since November 2015 and no commits in the last three months, so maintenance risk is substantial.
42%
Total Score
25
72
50
The latest registry release was in November 2015, with no releases in the last 12 months. This long release gap is strong evidence of abandonment risk for a library dependency.
There were no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates that maintenance has effectively stopped.
The package and repository are owned by an individual account rather than an organization, so there is no organizational backing shown to compensate for the thin recent activity.
The repository name does not match the package name and its README does not mention the package, so the repository-to-package relationship is not clearly established. This weakens provenance transparency despite the repository being linked.
The repository has zero stars, forks, and watchers, offering no community activity signal. Popularity is supporting evidence only, so this reinforces but does not determine the maintenance concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.