Open issues have had no recent movement, and the repository has no security policy. MIT licensing, a substantial README, and tests improve transparency but cannot resolve the maintenance concern.
42%
Total Score
50
67
75
The package has had no release in about 11 years: its latest release was March 16, 2015, with no releases in the last 12 months. Six total releases show some history, but the prolonged gap is a substantial maintenance risk.
Five issues remain open, while there were no new or closed issues and no pull-request activity in the last month. This supports the broader evidence of an inactive project.
The linked repository name does not match the package name and its README does not mention the package. That makes package-to-source ownership less clear, although the repository path otherwise uses the same owner and project name.
The repository is not marked archived, which is a positive. However, its last push was about 11 years ago, so the repository's active status does not compensate for the absence of recent maintenance.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, especially for a package that may be embedded in web or mobile applications.
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.