@aws-cdk/aws-iam
1
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
romainmulleramzn-ossrix0rrraws-cdk-team
Keywords
awscdkconstructsiam
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in oidc-provider entrypoint is a standard AWS CDK Lambda custom resource pattern; the variable references a controlled handler index, not arbitrary user input. | ai | |
| provenance | no-provenance | AI (provenance): AWS CDK v1 packages predate Sigstore provenance adoption; publisher is the official aws-cdk-team with strong track record. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.204.0 | 4 / 10 |
v1.204.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.