The tiny source tree has no README or tests, making integration and verification harder. It also has no security scanning or policy, while the MIT declaration and minimal dependency set are positives.
38%
Total Score
0
100
58
50
The latest release was published in March 2016, with no releases in the last 12 months. That long period without updates is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity for years.
The artifact and repository each contain only four files, with two source files and no visible documentation or test structure. This leaves little evidence of maintained project practice.
The package has no README, tests, or changelog. Missing tests and changelog are common in published artifacts, but the absent README is a real integration and transparency gap for a library.
The repository name does not match the package name, and no README mention was collected. Because the repository is a tiny four-file project rather than an evident monorepo, package ownership is less clear.
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.