@builder.io/buildercode-linux-x64
Builder Code binary for linux x64
Supply chain provenance
Status for the latest visible version.
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
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 from Builder.io; rg is ripgrep, a standard search tool bundled in IDE tooling. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary sub-package; no repo/keywords/deps is expected for this package type. | ai |
v0.5.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pabloelisseo) than the most recent previously approved version (manucorporat) on 2026-06-09, but pabloelisseo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.3
2 findingsThis version was published by a different npm account than previous versions on 2026-06-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
2 findingsPackage contains compiled binaries that could be backdoors: • rg
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.