@whook/aws-lambda
Build and deploy to AWS Lambda with Whook.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@whook/cors | AI (dependencies): Same-org sibling package; stable dependency relationship across versions. | ai | |
| dependencies | unvetted-dep:@whook/whook | AI (dependencies): Same-org core package; stable dependency relationship across versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @types/qs is a DefinitelyTyped types-only package; no executable risk. | ai | |
| phantom-deps | phantom-dep:ajv-formats | AI (phantom-deps): Referenced in config files; stable false positive for this framework package. | ai | |
| phantom-deps | phantom-dep:camelcase | AI (phantom-deps): Referenced in config files; stable false positive for this framework package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64+gunzip is standard CloudWatch Logs decoding; not a malicious payload pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/bytes | AI (phantom-deps): Framework-scoped type package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/aws-lambda | AI (phantom-deps): Framework-scoped type package; stable false positive. | ai | |
| phantom-deps | phantom-dep:strict-qs | AI (phantom-deps): Referenced in config files; stable false positive for this framework package. | ai | |
| phantom-deps | phantom-dep:@whook/cors | AI (phantom-deps): Same org scope; used as a framework-level dependency, not directly imported in all files. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): Referenced in config files; stable false positive for this framework package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 25.0.1 | 22 / 17 | |
| 25.0.0 | 22 / 17 | |
| 24.1.1 | 22 / 17 | |
| 24.1.0 | 22 / 17 | |
| 24.0.2 | 21 / 17 | |
| 23.0.0 | 21 / 16 | |
| 22.0.0 | 21 / 16 | |
| 21.0.1 | 21 / 16 | |
| 21.0.0 | 21 / 16 | |
| 20.1.2 | 21 / 17 | |
| 20.1.1 | 21 / 17 |
v25.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.