Fastest random ID and random string generation for Node.js
60%
Total Score
50
100
89
75
50
The release has no build provenance attestation or trusted-publisher evidence, so consumers cannot verify how it was published. This lowers supply-chain transparency but is not by itself a severe risk.
The latest release was about 4 years ago, with no releases in the last 12 months. This is a meaningful maintenance concern, although the package has four releases and is not marked deprecated.
The repository recorded no commits and no active maintainers in the last 3 months, indicating little recent maintenance activity. The repository is still unarchived, which provides limited compensation.
No build tool or security scanning tool was detected in the repository, leaving build and security practices less visible. The small package and simple file tree reduce the significance of this gap.
The repository has no published security policy, reducing transparency for reporting and handling vulnerabilities. This is a hygiene gap rather than evidence that the package is unsafe.
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.