88%
Total Score
88
94
75
100
One contributor made about 89% of the recent commits, creating concentration risk; organization ownership and five other active contributors partly compensate for it.
The repository name does not match the package name and its README does not mention builder-util, creating some uncertainty about package-to-repository ownership; the organization-backed repository and package contents provide partial context but do not remove it.
No repository security policy was found, leaving disclosure guidance and security contact expectations less transparent.
All 9 workflows were analyzed with no untrusted checkout or script-injection findings, all 36 action references are pinned, and most workflows use read-only permissions. A high-confidence low-severity finding reports an out-of-lockfile package install, and two workflows have top-level write permissions, so workflow hygiene is slightly weaker but not severe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
chalk Version ^4.1.2 | — | — |
debug Version ^4.3.4 | — | — |
js-yaml Version ^4.1.0 | — | — |
fs-extra Version ^10.1.0 | — | — |
stat-mode Version ^1.0.0 | — | — |
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.