@aws-cdk/aws-lambda
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/function-url.js | AI (source-diff): Standard jsii-compiled construct file, readable source. | ai | |
| source-diff | obfuscated-file:lib/lambda-canned-metrics.generated.js | AI (source-diff): Auto-generated metrics file with long lines by design. | ai | |
| source-diff | obfuscated-file:.warnings.jsii.js | AI (source-diff): jsii-generated deprecation warning shim, long lines but not obfuscated code | ai | |
| source-diff | obfuscated-file:lib/lambda-insights.js | AI (source-diff): Compiled JSII output, not obfuscation; sample is plain readable JS. | ai | |
| source-diff | obfuscated-file:lib/code-signing-config.js | AI (source-diff): jsii-generated JS, single long line is compiled output not obfuscation. | ai | |
| source-diff | obfuscated-file-transition:lib/function-hash.js | AI (source-diff): Same build-output pattern; sample is plain compiled JS. | ai | |
| npm-metadata | url-dep:cfn2ts | AI (npm-metadata): Monorepo-local build tool via file: dependency, standard lerna pattern. | ai | |
| npm-metadata | url-dep:pkglint | AI (npm-metadata): Monorepo-local lint tool via file: dependency. | ai | |
| npm-metadata | url-dep:cdk-build-tools | AI (npm-metadata): Monorepo-local build tool via file: dependency. | ai | |
| npm-metadata | url-dep:cdk-integ-tools | AI (npm-metadata): Monorepo-local integ tool via file: dependency. | ai | |
| semgrep | semgrep:http-module-request | AI (semgrep): CFN custom-resource response callback to CFN-provided URL, not exfiltration. | ai | |
| source-diff | obfuscated-file:lib/image-function.js | AI (source-diff): Compiled TS lib output for new DockerImageFunction feature, not obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adds sibling first-party @aws-cdk packages for the new ECR-based Lambda feature. | ai | |
| phantom-deps | phantom-dep:@aws-cdk/cx-api | AI (phantom-deps): Same-org monorepo dependency, standard for aws-cdk packages. | ai | |
| phantom-deps | phantom-dep:@aws-cdk/aws-events | AI (phantom-deps): Sibling @aws-cdk/* package in the CDK monorepo; declared but not directly imported is a common monorepo artifact, not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): aws-cdk-team is a well-established AWS publisher; lack of Sigstore provenance is expected for packages of this age and is not a security concern here. | ai |
Versions (showing 41 of 241)
| Version | Deps | Published |
|---|---|---|
| 1.32.0 | 11 / 15 | |
| 1.31.0 | 11 / 15 | |
| 1.30.0 | 11 / 15 | |
| 1.29.0 | 11 / 15 | |
| 1.28.0 | 10 / 15 | |
| 1.27.0 | 10 / 15 | |
| 1.26.0 | 10 / 15 | |
| 1.25.0 | 10 / 15 | |
| 1.24.0 | 10 / 15 | |
| 1.23.0 | 10 / 15 | |
| 1.22.0 | 10 / 15 | |
| 1.21.1 | 10 / 15 | |
| 1.21.0 | 10 / 15 | |
| 1.20.0 | 10 / 15 | |
| 1.19.0 | 10 / 13 | |
| 1.18.0 | 10 / 13 | |
| 1.17.1 | 10 / 13 | |
| 1.17.0 | 10 / 13 | |
| 1.16.3 | 10 / 13 | |
| 1.16.2 | 10 / 13 | |
| 1.16.1 | 10 / 13 | |
| 1.16.0 | 10 / 13 | |
| 1.15.0 | 10 / 13 | |
| 1.14.0 | 10 / 13 | |
| 1.13.1 | 10 / 13 | |
| 1.13.0 | 10 / 13 | |
| 1.12.0 | 10 / 13 | |
| 1.11.0 | 10 / 13 | |
| 1.10.1 | 10 / 13 | |
| 1.10.0 | 10 / 13 | |
| 1.9.0 | 10 / 13 | |
| 1.8.0 | 10 / 14 | |
| 1.7.0 | 10 / 14 | |
| 1.6.1 | 10 / 14 | |
| 1.6.0 | 10 / 14 | |
| 1.5.0 | 10 / 14 | |
| 1.4.0 | 10 / 14 | |
| 1.3.0 | 10 / 14 | |
| 1.2.0 | 10 / 14 | |
| 1.1.0 | 10 / 14 | |
| 1.0.0 | 10 / 14 |
v1.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.