Expand environment variables using dotenv
84%
Total Score
83
100
94
63
A prepack lifecycle script is used, adding some build-time complexity, but this is limited to packaging rather than an install-time script executed by consumers.
All 19 recent commits came from one contributor, creating a meaningful continuity risk. Organization ownership provides some ability to hand maintenance off, but no second active contributor is shown.
The repository uses esbuild, TypeScript, and npm scripts, indicating a structured build; however, no security scanning tools were detected.
No SECURITY.md or equivalent security policy was found, leaving vulnerability-reporting and response expectations unclear.
The single workflow has no top-level token permissions declaration. No write permissions were detected, but explicitly limiting permissions would provide stronger workflow hygiene.
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.