@aws-solutions-constructs/aws-apigateway-lambda

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

aws-solutions-constructs-team

Keywords

awscdkawscdkAWS Solutions ConstructsAmazon API GatewayAWS Lambda

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@aws-cdk/integ-tests-alpha	AI (dependencies): Official AWS CDK package, standard test-time dependency.	ai	2026/07/19
phantom-deps	phantom-dep:@aws-cdk/integ-tests-alpha	AI (phantom-deps): Used in integ test config, not a real phantom dep concern.	ai	2026/07/19
source-diff	obfuscated-file:test/integ.apilam-no-usage-plan.js	AI (source-diff): Long line is a base64 sourcemap comment in compiled test fixture, not obfuscated code.	ai	2026/07/19
source-diff	obfuscated-file:test/apigateway-lambda.test.js	AI (source-diff): Standard CDK jest test file, not obfuscated; long-line heuristic false positive.	ai	2026/07/07
source-diff	net-exec-file:test/apigateway-lambda.test.js	AI (source-diff): Test file has no network/exec malicious behavior; false positive.	ai	2026/07/07
publish-pattern	dormant-publish	AI (publish-pattern): Large official AWS monorepo package with irregular but legitimate release cadence.	ai	2026/07/07

Versions (showing 51 of 56)

View all versions

Version	Deps	Published
2.102.0	2 / 5	2026-05-15
2.101.0	2 / 5	2026-04-07
2.100.1	2 / 5	2026-02-24
2.100.0	2 / 5	2026-02-23
2.99.0	2 / 5	2026-02-09
2.98.0	2 / 5	2026-01-30
2.97.0	2 / 5	2025-12-24
2.96.0	2 / 5	2025-11-26
2.95.1	2 / 5	2025-11-14
2.95.0	2 / 5	2025-11-14
2.94.0	2 / 5	2025-10-07
2.93.0	2 / 5	2025-09-24
2.92.2	2 / 5	2025-09-10
2.92.1	2 / 5	2025-08-22
2.92.0	2 / 5	2025-08-21
2.91.0	2 / 5	2025-08-13
2.90.4	2 / 5	2025-08-05
2.90.3	2 / 5	2025-08-04
2.90.2	2 / 5	2025-08-02
2.90.1	2 / 5	2025-08-01
2.90.0	2 / 5	2025-07-30
2.87.0	2 / 5	2025-07-29
2.86.0	2 / 5	2025-07-14
2.85.6	2 / 5	2025-06-23
2.85.5	2 / 5	2025-06-23
2.85.4	2 / 5	2025-06-20
2.85.3	2 / 5	2025-06-20
2.85.2	2 / 5	2025-05-01
2.85.1	2 / 5	2025-04-30
2.85.0	2 / 5	2025-04-29
2.84.0	2 / 5	2025-04-18
2.83.0	2 / 5	2025-04-08
2.82.0	2 / 5	2025-04-03
2.81.0	2 / 5	2025-03-28
2.80.0	2 / 5	2025-03-27
2.79.1	2 / 5	2025-03-21
2.79.0	2 / 5	2025-03-18
2.78.1	2 / 5	2025-03-11
2.78.0	2 / 5	2025-03-07
2.77.0	2 / 5	2025-01-31
2.76.0	2 / 5	2024-12-24
2.75.0	2 / 5	2024-12-23
2.74.0	3 / 4	2024-10-22
2.73.0	3 / 4	2024-10-21
2.72.0	3 / 4	2024-10-06
2.71.0	3 / 4	2024-09-27
2.70.0	3 / 4	2024-09-18
2.69.0	3 / 4	2024-09-11
2.68.0	3 / 4	2024-08-28
2.67.1	3 / 4	2024-08-27
2.67.0	3 / 4	2024-08-26

v2.102.0

3 findings

HIGH New obfuscated file: test/apigateway-lambda.test.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: test/apigateway-lambda.test.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v2.101.0

3 findings

HIGH New obfuscated file: test/apigateway-lambda.test.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: test/apigateway-lambda.test.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v2.100.1

3 findings

HIGH New obfuscated file: test/apigateway-lambda.test.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: test/apigateway-lambda.test.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v2.100.0

3 findings

HIGH New obfuscated file: test/apigateway-lambda.test.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: test/apigateway-lambda.test.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v2.99.0

1 finding

LOW No provenance attestation provenance

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

v2.98.0

1 finding

LOW No provenance attestation provenance

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

v2.97.0

1 finding

LOW No provenance attestation provenance

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

v2.96.0

1 finding

LOW No provenance attestation provenance

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

v2.95.1

1 finding

LOW No provenance attestation provenance

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

v2.95.0

1 finding

LOW No provenance attestation provenance

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

v2.94.0

1 finding

LOW No provenance attestation provenance

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

v2.93.0

1 finding

LOW No provenance attestation provenance

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

v2.92.2

1 finding

LOW No provenance attestation provenance

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

v2.92.1

1 finding

LOW No provenance attestation provenance

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

v2.92.0

1 finding

LOW No provenance attestation provenance

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

v2.91.0

1 finding

LOW No provenance attestation provenance

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

v2.90.4

1 finding

LOW No provenance attestation provenance

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

v2.90.3

1 finding

LOW No provenance attestation provenance

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

v2.90.2

1 finding

LOW No provenance attestation provenance

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

v2.90.1

1 finding

LOW No provenance attestation provenance

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

v2.90.0

1 finding

LOW No provenance attestation provenance

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

v2.87.0

1 finding

LOW No provenance attestation provenance

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

v2.86.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.

v2.85.6

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.85.5

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.85.4

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.85.3

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.85.2

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.85.1

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.85.0

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.84.0

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.83.0

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.82.0

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.81.0

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.80.0

2 findings

HIGH New obfuscated file: test/integ.apilam-no-usage-plan.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.79.1

1 finding

LOW No provenance attestation provenance

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

v2.79.0

1 finding

LOW No provenance attestation provenance

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

v2.78.1

1 finding

LOW No provenance attestation provenance

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

v2.78.0

1 finding

LOW No provenance attestation provenance

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

v2.77.0

1 finding

LOW No provenance attestation provenance

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

v2.76.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.

v2.75.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.

v2.74.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.

v2.73.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.

v2.72.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.

v2.71.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.

v2.70.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.

v2.69.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.

v2.68.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.

v2.67.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.

v2.67.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.