← Home

jsii-pacmak

npm Repository Homepage
18
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

amzn-ossaws-cdk-team

Keywords

jsiiaws

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Spreading process.env to pass environment to subprocess (venv/build tools) is standard for this code-gen package. ai
semgrep semgrep:child-process-import AI (semgrep): Build/packaging tool legitimately invokes compilers and language runtimes via child_process; stable pattern across all versions. ai

Versions (showing 18 of 18)

Version Deps Published
1.129.0 12 / 19
1.128.0 12 / 19
1.127.0 12 / 16
1.126.0 12 / 16
1.125.0 12 / 16
1.124.0 12 / 16
1.123.0 12 / 16
1.122.0 12 / 16
1.121.0 12 / 16
1.120.0 12 / 16
1.119.0 12 / 16
1.118.0 12 / 16
1.117.0 12 / 16
1.116.0 12 / 16
1.115.0 12 / 16
1.114.1 12 / 16
1.113.0 12 / 15
1.112.0 12 / 15

v1.129.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.128.0

4 findings
HIGH env-spread: lib/targets/python.js:65 semgrep

Spreading entire process.env into an object — may capture all secrets 63 | venv, 64 | ]); > 65 | const env = { 66 | ...process.env, 67 | PATH: `${venvBin}:${process.env.PATH}`,

HIGH env-spread: lib/util.js:154 semgrep

Spreading entire process.env into an object — may capture all secrets 152 | ...options, 153 | shell: true, > 154 | env: { ...process.env, ...(options?.env ?? {}) }, 155 | stdio: ['ignore', 'pipe', 'pipe'], 156 | }),

HIGH env-spread: lib/util.js:189 semgrep

Spreading entire process.env into an object — may capture all secrets 187 | child: (0, child_process_1.spawn)(binary, args, { 188 | ...options, > 189 | env: { ...process.env, ...(options?.env ?? {}) }, 190 | stdio: ['ignore', 'pipe', 'pipe'], 191 | }),

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.127.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.126.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.125.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.124.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.123.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.122.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.121.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.120.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.119.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.118.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.117.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.116.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.115.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.114.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.113.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.112.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.