The package has a clear README, tests, an MIT license, and only one runtime dependency. Its source repository does not name the package, which makes ownership less transparent.
58%
Total Score
50
100
80
50
Only one account has registry publish access. This is a thin publishing base and leaves the release process dependent on one maintainer.
The latest release was over four years ago, with no releases in the last 12 months. This indicates materially reduced maintenance activity, although the package has a stable 1.1.0 release rather than a pre-release.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long period without a release and increasing abandonment risk.
The linked repository name does not match the package name and its README does not mention the package, so the package-to-source relationship is less transparent than expected.
The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This is a transparency gap, though it is less severe for a small utility package.
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.