aws-lambda
Deploy AWS Lambda functions from command line using a json or yaml config file.
3
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
adrian.praja
Keywords
lambdaaws lambdadeploydeploy lambda
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): This is a CLI deployment tool; child_process usage is expected and legitimate for executing system commands as part of Lambda deployment workflows. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used to decode AWS Lambda's LogResult field, which AWS returns base64-encoded. Standard AWS SDK usage, not obfuscation. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is a declared runtime dependency in package.json; the phantom-dep finding is a false positive for this package. | ai |
v1.0.7
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.