Deploy AWS Lambda functions from command line using a json or yaml config file.
55%
Total Score
67
83
50
The package has 23 releases since 2015, but its latest release was in November 2021 and there were no releases in the last 12 months. This long release gap is a meaningful maintenance concern.
The repository recorded zero commits and zero active maintainers in the last three months. Although it was pushed in July 2024, current development activity is absent.
There are 8 open issues and 3 open pull requests, with no issues closed or pull requests merged in the last month. This suggests limited recent project attention, though it is not evidence of abandonment by itself.
The repository has no detected build tooling or security scanning. For this small command-line package this is a hygiene gap rather than a severe risk, but it reduces transparency around automated checks.
No security policy was found in the repository. This matters because the README documents a prior command-injection vulnerability, although the absence of a policy alone does not make the release unfit.
| Title | Versions | Severity |
|---|---|---|
CVE-2019-10777 aws-lambda is vulnerable to Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in versions 0.0.0 - 1.0.4. | 0.0.0 - 1.0.4 | Critical |
| Dependency | Last Release | Score |
|---|---|---|
aws-sdk Version ^2.814.0 | — | — |
js-yaml Version ^3.14.1 | — | — |
commander Version ^3.0.2 | — | — |
watchpack Version ^2.0.0-beta.10 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.