react-native-builder-bob
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Passing process.env to child processes is standard for build tools; no exfiltration risk. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Build tool legitimately uses child_process for Android assembly tasks. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Config loader pattern; loads user-specified config files at runtime — expected for a build CLI. | ai | |
| phantom-deps | phantom-dep:escape-string-regexp | AI (phantom-deps): escape-string-regexp is declared as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.41.0 | 22 / 17 | |
| 0.40.18 | 22 / 17 | |
| 0.40.17 | 22 / 17 | |
| 0.40.16 | 22 / 17 | |
| 0.40.15 | 22 / 18 | |
| 0.40.14 | 22 / 18 | |
| 0.40.13 | 22 / 18 | |
| 0.40.12 | 22 / 18 | |
| 0.40.11 | 23 / 17 |
v0.41.0
3 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/callstack/react-native-builder-bob/blob/f0da652b454d58268ca7ac50468a6c2f106fb5b7/lib/targets/typescript.js#L64 62 | const result = await (0, _spawn.spawn)('yarn', ['bin', 'tsc'], { 63 | cwd: root, > 64 | env: { 65 | ...process.env, 66 | FORCE_COLOR: '0'
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/callstack/react-native-builder-bob/blob/f0da652b454d58268ca7ac50468a6c2f106fb5b7/lib/utils/workerize.js#L34 32 | data 33 | }, > 34 | env: { 35 | ...process.env, 36 | FORCE_COLOR: process.stdout.isTTY ? '1' : '0'
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.17
3 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/callstack/react-native-builder-bob/blob/d91c82aa73bcedb7f5364adb0c15ce1f7a486f6e/lib/targets/typescript.js#L64 62 | const result = await (0, _spawn.spawn)('yarn', ['bin', 'tsc'], { 63 | cwd: root, > 64 | env: { 65 | ...process.env, 66 | FORCE_COLOR: '0'
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/callstack/react-native-builder-bob/blob/d91c82aa73bcedb7f5364adb0c15ce1f7a486f6e/lib/utils/workerize.js#L34 32 | data 33 | }, > 34 | env: { 35 | ...process.env, 36 | FORCE_COLOR: process.stdout.isTTY ? '1' : '0'
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.