The package has a clear MIT license, tests, a changelog, and a matching repository with no install-time scripts. Its very old maintenance record leaves compatibility and support uncertain; pinning version 1.1 is prudent if adoption is unavoidable.
38%
Total Score
0
100
71
50
The package has had only two releases, with the latest published in March 2017 and none in the last nine years. This is strong evidence of abandonment risk for a framework integration.
The repository recorded no commits and no active maintainers in the last three months, consistent with its last push occurring in March 2017. The included tests do not compensate for the lack of current maintenance.
The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these counters provide no supporting evidence of an active user or contributor community.
The repository is not archived, which avoids the strongest repository-level abandonment signal, but its last push was in March 2017. The inactive history still materially lowers confidence in ongoing compatibility.
The repository has no security policy. For an old package this weakens the route for reporting and handling vulnerabilities, although it is secondary to the much larger maintenance concern.
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.