Configuration control for production node deployments
88%
Total Score
100
100
95
67
50
No build attestation or trusted-publisher provenance was recorded, so consumers have less evidence about how the published artifact was produced.
The project uses TypeScript, webpack, and npm scripts, but no security scanning tools were detected; this is a modest transparency gap.
No repository security policy was found, leaving vulnerability-reporting and response expectations undocumented.
The only workflow was fully analyzed with no audit findings or untrusted-trigger sinks, but all four action references are unpinned, reducing reproducibility and update integrity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
json5 Version ^2.2.3 | — | — |
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.