The package has no README or security policy, limiting guidance and transparency for adopters. It does include tests and has no runtime dependencies, but the very small project footprint offers little evidence of ongoing support.
40%
Total Score
25
100
56
75
The package has had only 3 releases, all around November 2017, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency, despite the stable v1.2 version.
There were no commits and no active maintainers in the last 3 months, reinforcing that the project is not actively maintained. This materially increases the risk of unresolved defects or compatibility problems.
The repository is not marked archived, but its last push was on November 15, 2017, consistent with the release history's long inactivity. The non-archived status provides little practical compensation.
The package contains tests and the repository also has tests, which provides some validation evidence. The missing README and changelog reduce consumer guidance, though missing changelogs are normal for published artifacts.
The repository is owned by an individual user rather than an organization, so there is no organizational backing shown to compensate for the thin maintenance record. This supports the abandonment concern but is not independently decisive.
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.