@dereekb/dbx-cli
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): CLI tool spreading process.env to pass environment to child process with a single override; standard pattern, no exfiltration risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo sub-package; missing metadata signals are expected for internal packages. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 loopback used as OAuth CLI redirect URI — standard RFC 8252 pattern, not exfiltration. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 13.15.0 | 0 / 3 | |
| 13.14.0 | 0 / 3 | |
| 13.13.0 | 0 / 3 | |
| 13.12.9 | 0 / 3 | |
| 13.12.8 | 0 / 3 | |
| 13.12.7 | 0 / 3 | |
| 13.12.6 | 0 / 3 | |
| 13.12.5 | 0 / 3 | |
| 13.12.4 | 0 / 3 | |
| 13.12.3 | 0 / 3 | |
| 13.12.2 | 0 / 2 | |
| 13.12.1 | 0 / 2 | |
| 13.12.0 | 0 / 2 | |
| 13.11.18 | 0 / 2 | |
| 13.11.17 | 0 / 2 | |
| 13.11.16 | 0 / 2 | |
| 13.11.15 | 0 / 2 | |
| 13.11.14 | 0 / 1 | |
| 13.11.13 | 0 / 1 | |
| 13.11.12 | 0 / 1 | |
| 13.11.11 | 0 / 1 | |
| 13.11.10 | 0 / 1 | |
| 13.11.9 | 0 / 1 | |
| 13.11.8 | 0 / 1 | |
| 13.11.7 | 0 / 1 | |
| 13.11.6 | 0 / 1 | |
| 13.11.5 | 0 / 1 | |
| 13.11.4 | 0 / 1 | |
| 13.11.3 | 0 / 1 | |
| 13.11.2 | 0 / 1 | |
| 13.11.1 | 0 / 1 | |
| 13.11.0 | 0 / 1 |
v13.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.9
2 findingsSpreading entire process.env into an object — may capture all secrets 311 | const child = spawn("npx", args, { 312 | cwd: opts.workspaceRoot, > 313 | env: { ...process.env, FORCE_COLOR: "0" }, 314 | stdio: ["ignore", "inherit", "inherit"] 315 | });
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.8
2 findingsSpreading entire process.env into an object — may capture all secrets 311 | const child = spawn("npx", args, { 312 | cwd: opts.workspaceRoot, > 313 | env: { ...process.env, FORCE_COLOR: "0" }, 314 | stdio: ["ignore", "inherit", "inherit"] 315 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.12.7
2 findingsSpreading entire process.env into an object — may capture all secrets 311 | const child = spawn("npx", args, { 312 | cwd: opts.workspaceRoot, > 313 | env: { ...process.env, FORCE_COLOR: "0" }, 314 | stdio: ["ignore", "inherit", "inherit"] 315 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.12.6
2 findingsSpreading entire process.env into an object — may capture all secrets 311 | const child = spawn("npx", args, { 312 | cwd: opts.workspaceRoot, > 313 | env: { ...process.env, FORCE_COLOR: "0" }, 314 | stdio: ["ignore", "inherit", "inherit"] 315 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.12.5
2 findingsSpreading entire process.env into an object — may capture all secrets 311 | const child = spawn("npx", args, { 312 | cwd: opts.workspaceRoot, > 313 | env: { ...process.env, FORCE_COLOR: "0" }, 314 | stdio: ["ignore", "inherit", "inherit"] 315 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.12.4
2 findingsSpreading entire process.env into an object — may capture all secrets 311 | const child = spawn("npx", args, { 312 | cwd: opts.workspaceRoot, > 313 | env: { ...process.env, FORCE_COLOR: "0" }, 314 | stdio: ["ignore", "inherit", "inherit"] 315 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.12.3
2 findingsSpreading entire process.env into an object — may capture all secrets 311 | const child = spawn("npx", args, { 312 | cwd: opts.workspaceRoot, > 313 | env: { ...process.env, FORCE_COLOR: "0" }, 314 | stdio: ["ignore", "inherit", "inherit"] 315 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.12.2
2 findingsSpreading entire process.env into an object — may capture all secrets 311 | const child = spawn("npx", args, { 312 | cwd: opts.workspaceRoot, > 313 | env: { ...process.env, FORCE_COLOR: "0" }, 314 | stdio: ["ignore", "inherit", "inherit"] 315 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.12.1
2 findingsSpreading entire process.env into an object — may capture all secrets 311 | const child = spawn("npx", args, { 312 | cwd: opts.workspaceRoot, > 313 | env: { ...process.env, FORCE_COLOR: "0" }, 314 | stdio: ["ignore", "inherit", "inherit"] 315 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.12.0
2 findingsSpreading entire process.env into an object — may capture all secrets 307 | const child = spawn("npx", args, { 308 | cwd: opts.workspaceRoot, > 309 | env: { ...process.env, FORCE_COLOR: "0" }, 310 | stdio: ["ignore", "inherit", "inherit"] 311 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.18
2 findingsSpreading entire process.env into an object — may capture all secrets 307 | const child = spawn("npx", args, { 308 | cwd: opts.workspaceRoot, > 309 | env: { ...process.env, FORCE_COLOR: "0" }, 310 | stdio: ["ignore", "inherit", "inherit"] 311 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.17
2 findingsSpreading entire process.env into an object — may capture all secrets 307 | const child = spawn("npx", args, { 308 | cwd: opts.workspaceRoot, > 309 | env: { ...process.env, FORCE_COLOR: "0" }, 310 | stdio: ["ignore", "inherit", "inherit"] 311 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.16
2 findingsSpreading entire process.env into an object — may capture all secrets 307 | const child = spawn("npx", args, { 308 | cwd: opts.workspaceRoot, > 309 | env: { ...process.env, FORCE_COLOR: "0" }, 310 | stdio: ["ignore", "inherit", "inherit"] 311 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.15
2 findingsSpreading entire process.env into an object — may capture all secrets 307 | const child = spawn("npx", args, { 308 | cwd: opts.workspaceRoot, > 309 | env: { ...process.env, FORCE_COLOR: "0" }, 310 | stdio: ["ignore", "inherit", "inherit"] 311 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.