@builder.io/buildercode-win32-x64 MIT 2 versions

@builder.io/buildercode-win32-x64

npm

Builder Code binary for win32 x64

Versions

MIT

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

steve8708samijaberteleaziz123mrkoreyemheverygustavohgsmanucorporatsanyamkamatbengironemidhunadarvinkylefowlerbuilderio-botarmelaaishwarya_parabemmaacanaghavarhadesidmohanty11jcortesebuildervishwasgopinathnicholaskoechpaprikafpabloelisseoliamdebeasi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	bundled-binaries	AI (npm-metadata): Platform binary package; rg.exe is ripgrep, legitimately bundled in Builder Code IDE tooling.	ai	2026/05/04
bogus-package	bogus-package	AI (bogus-package): Binary sub-package pattern; no repo/keywords/deps is expected for platform-specific binary distributions.	ai	2026/05/04

Versions (showing 2 of 2)

Version	Deps	Published
0.5.1	0 / 0	2026-05-04
0.4.19	0 / 0	2026-05-01

v0.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.19

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • rg.exe

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.