The MIT license, readme, release notes, and lack of install-time scripts provide basic transparency. Its small scope may reduce exposure, but compatibility fixes and issue support cannot be expected.
42%
Total Score
50
86
100
One registry maintainer creates a thin publishing base and limited continuity if that person becomes unavailable. The linked repository is owned by the same individual, so there is no broader organization backing shown here.
Only two releases were published, with the latest in September 2018 and none in the last eight years. This is strong evidence of an abandoned or effectively frozen package.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
Two issues remain open, with no new or closed issues and no pull-request activity in the last month. This reinforces the lack of current support, though the small issue count limits the severity.
Version 0.6.0 is not a stable-major release, which signals a less mature compatibility promise. It is not marked as a prerelease, so this is a secondary concern rather than a release-blocking issue.
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.