The artifact has usable documentation and a matching repository, but the license metadata is inconsistent and the project has no security policy. Its very small maintainer base and absence of recent activity add substantial abandonment risk.
42%
Total Score
50
63
50
The latest release was published in April 2017, and there have been no releases in the last 12 months. This long gap is a substantial maintenance concern for a dependency.
The artifact contains an MIT license file, so the release is licensed, but the manifest declares it as proprietary. That mismatch creates avoidable uncertainty for consumers.
Only one registry account, vis, has publish access. A single maintainer is a thin publishing base and provides little resilience when combined with the lack of recent activity.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the package's long release gap. This increases abandonment risk.
The linked repository has no security policy. This is a transparency and vulnerability-reporting gap, although it is not evidence that the package is malicious.
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.