@cdktf/commons
CDK for Terraform Common utilities
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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): env passed to local pnpm subprocess, no exfil destination; stable for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads a resolved local JSON file path, not remote code. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.21.0 | 11 / 16 | |
| 0.20.12 | 11 / 16 | |
| 0.20.11 | 11 / 13 | |
| 0.20.10 | 11 / 12 | |
| 0.20.9 | 11 / 12 |
v0.21.0
3 findingsSpreading entire process.env into an object — may capture all secrets 108 | try { 109 | output = await (0, util_1.exec)("pnpm", ["list", packageName, "--json"], { > 110 | env: { ...process.env }, 111 | }); 112 | }
Spreading entire process.env into an object — may capture all secrets 136 | try { 137 | output = await (0, util_1.exec)("npm", ["list", packageName, "--json"], { > 138 | env: { ...process.env }, 139 | }); 140 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.12
3 findingsSpreading entire process.env into an object — may capture all secrets 108 | try { 109 | output = await (0, util_1.exec)("pnpm", ["list", packageName, "--json"], { > 110 | env: { ...process.env }, 111 | }); 112 | }
Spreading entire process.env into an object — may capture all secrets 136 | try { 137 | output = await (0, util_1.exec)("npm", ["list", packageName, "--json"], { > 138 | env: { ...process.env }, 139 | }); 140 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.11
3 findingsSpreading entire process.env into an object — may capture all secrets 108 | try { 109 | output = await (0, util_1.exec)("pnpm", ["list", packageName, "--json"], { > 110 | env: { ...process.env }, 111 | }); 112 | }
Spreading entire process.env into an object — may capture all secrets 136 | try { 137 | output = await (0, util_1.exec)("npm", ["list", packageName, "--json"], { > 138 | env: { ...process.env }, 139 | }); 140 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.10
3 findingsSpreading entire process.env into an object — may capture all secrets 108 | try { 109 | output = await (0, util_1.exec)("pnpm", ["list", packageName, "--json"], { > 110 | env: { ...process.env }, 111 | }); 112 | }
Spreading entire process.env into an object — may capture all secrets 136 | try { 137 | output = await (0, util_1.exec)("npm", ["list", packageName, "--json"], { > 138 | env: { ...process.env }, 139 | }); 140 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.9
3 findingsSpreading entire process.env into an object — may capture all secrets 108 | try { 109 | output = await (0, util_1.exec)("pnpm", ["list", packageName, "--json"], { > 110 | env: { ...process.env }, 111 | }); 112 | }
Spreading entire process.env into an object — may capture all secrets 136 | try { 137 | output = await (0, util_1.exec)("npm", ["list", packageName, "--json"], { > 138 | env: { ...process.env }, 139 | }); 140 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.