82%
Total Score
88
100
94
67
100
One contributor made about 89% of the 81 recent commits. Five others contributed, but their much smaller shares leave maintenance unusually concentrated.
The repository name does not match the package name and its README does not mention builder-util-runtime, so the package-to-source relationship is not directly transparent despite the normal monorepo possibility.
No repository security policy was found, leaving vulnerability reporting and response expectations less transparent.
All nine workflows were analyzed, with no untrusted checkout or script-injection paths and no unpinned actions. One high-confidence low-severity finding reports an install outside a lockfile, a minor reproducibility concern; two workflows also grant top-level write access.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-805853 builder-util-runtime is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in versions 1.0.0 - 9.6.3. | 1.0.0 - 9.6.3 | High |
| Dependency | Last Release | Score |
|---|---|---|
sax Version ^1.2.4 | — | — |
debug Version ^4.3.4 | — | — |
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.