The one-person publishing base and absent security scanning leave little operational reassurance. Documentation and tests are present, but they do not offset roughly 14 years without a new release or repository activity.
18%
Total Score
25
75
75
The package has only one release, published about 14 years ago, and none in the last 12 months. This is strong evidence of abandonment for a dependency.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the package's long release hiatus. No compensating maintenance activity is shown.
Only one registry publishing account is listed. The repository is user-owned rather than organization-backed, so there is little visible redundancy if that publisher stops maintaining the package.
The linked repository name does not match the package name and its README does not mention the package, so ownership of this package is not clearly established by the source.
The repository has no security policy, leaving no documented channel or process for handling security reports. This compounds the risk of relying on an apparently inactive project.
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.