@salesforce/plugin-data-code-extension
Data Cloud Code Extension
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): Legitimate child-process spawn inheriting env; standard pattern for this Salesforce CLI plugin. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.2.1 | 3 / 7 | |
| 1.2.0 | 3 / 7 | |
| 1.1.1 | 3 / 7 | |
| 1.1.0 | 3 / 7 | |
| 1.0.0 | 3 / 7 | |
| 0.1.5 | 3 / 7 | |
| 0.1.4 | 3 / 7 | |
| 0.1.3 | 3 / 7 | |
| 0.1.2 | 3 / 7 | |
| 0.1.1 | 3 / 7 | |
| 0.1.0 | 3 / 7 |
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsSpreading entire process.env into an object — may capture all secrets 173 | const child = spawn('datacustomcode', args, { 174 | timeout: 600_000, > 175 | env: { ...process.env, PYTHONUNBUFFERED: '1' }, 176 | }); 177 | let stdout = '';
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
2 findingsSpreading entire process.env into an object — may capture all secrets 173 | const child = spawn('datacustomcode', args, { 174 | timeout: 300_000, > 175 | env: { ...process.env, PYTHONUNBUFFERED: '1' }, 176 | }); 177 | let stdout = '';
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsSpreading entire process.env into an object — may capture all secrets 173 | const child = spawn('datacustomcode', args, { 174 | timeout: 300_000, > 175 | env: { ...process.env, PYTHONUNBUFFERED: '1' }, 176 | }); 177 | let stdout = '';
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
2 findingsSpreading entire process.env into an object — may capture all secrets 171 | const child = spawn('datacustomcode', args, { 172 | timeout: 300_000, > 173 | env: { ...process.env, PYTHONUNBUFFERED: '1' }, 174 | }); 175 | let stdout = '';
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsSpreading entire process.env into an object — may capture all secrets 171 | const child = spawn('datacustomcode', args, { 172 | timeout: 300_000, > 173 | env: { ...process.env, PYTHONUNBUFFERED: '1' }, 174 | }); 175 | let stdout = '';
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsSpreading entire process.env into an object — may capture all secrets 212 | const child = spawn('datacustomcode', args, { 213 | timeout: 300_000, > 214 | env: { ...process.env, PYTHONUNBUFFERED: '1' }, 215 | }); 216 | let stdout = '';
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
2 findingsSpreading entire process.env into an object — may capture all secrets 212 | const child = spawn('datacustomcode', args, { 213 | timeout: 300_000, > 214 | env: { ...process.env, PYTHONUNBUFFERED: '1' }, 215 | }); 216 | let stdout = '';
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsSpreading entire process.env into an object — may capture all secrets 212 | const child = spawn('datacustomcode', args, { 213 | timeout: 300_000, > 214 | env: { ...process.env, PYTHONUNBUFFERED: '1' }, 215 | }); 216 | let stdout = '';
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsSpreading entire process.env into an object — may capture all secrets 209 | const child = spawn('datacustomcode', args, { 210 | timeout: 300_000, > 211 | env: { ...process.env, PYTHONUNBUFFERED: '1' }, 212 | }); 213 | let stdout = '';
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.