NodeJS Require that let you handle module not found error without try/catch
78%
Total Score
63
100
94
75
50
No build attestation, trusted publisher, or staged publishing evidence is present, leaving the relationship between source and published artifact less transparent.
Only one registry account has publish access. That is a continuity concern, although repository activity shows the same maintainer is still actively publishing and contributing.
The repository is owned by an individual user rather than an organization, so the single-maintainer concentration is not offset by visible organizational backing.
One contributor made all four commits in the last three months, so maintenance depends entirely on a single individual and has limited handoff resilience.
The project uses TypeScript, Vitest, and npm scripts for its build and tests, but no security-scanning tooling was detected. The build tooling is a positive; the missing scanning is a minor hygiene gap.
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.