aws-lambda @0.1.2
rejected
This version was rejected.
It did not pass GreenFlagged's security review and is not served by the registry.
The findings and risk dispositions below explain why.
46
Risk Score
MIT
License
No
Install Scripts
3
Dependencies
0
Dev Dependencies
2.6 KB
Package Size
Published
Deploy AWS Lambda functions from command line using a json or yaml config file.
Maintainers
adrian.praja
Keywords
lambdaaws lambdadeploydeploy lambda
Dependencies (3)
| Package | Constraint | Registry Status |
|---|---|---|
| dotenv | ^0.4.0 | auto_approved |
| aws-sdk | ^* | No greenflagged match |
| commander | ^2.5.0 | auto_approved |
Transitive Dependency Tree
3 transitive deps
max depth 1
├─
aws-sdk
^*
├─
commander
^2.5.0
→ 2.20.3
├─
dotenv
^0.4.0
→ 0.4.0
SAST Findings (2)
CRITICAL
GHSA-934x-72xh-5hrg: OS command injection in aws-lambda
osv
CVSS 9.8 (CRITICAL) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H In aws-lambda versions prior to version 1.0.5, the "config.FunctioName" is used to construct the argument used within the "exec" function without any sanitization. It is possible for a user to inject arbitrary commands to the "zipCmd" used within "config.FunctionName".
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
Review Summary
Risk score: 46. Findings: 1 critical (+40), 2 low (+6), 2 info (+0).
Commit: b8391b279394 Browse source
Published to npm: