@codegenie/serverless-express
This library enables you to utilize AWS Lambda and Amazon API Gateway to respond to web and API requests using your existing Node.js application framework.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used to convert encoded HTTP response bodies back to binary — standard behavior for a serverless HTTP adapter. Not malicious. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 0 / 28 | |
| 4.17.1 | 0 / 28 | |
| 4.17.0 | 0 / 28 | |
| 4.16.1 | 0 / 28 | |
| 4.16.0 | 0 / 28 | |
| 4.15.0 | 0 / 28 | |
| 4.14.2 | 0 / 28 | |
| 4.14.1 | 0 / 28 | |
| 4.14.0 | 0 / 28 | |
| 4.13.0 | 0 / 28 | |
| 4.12.5 | 0 / 28 | |
| 4.12.4 | 0 / 28 | |
| 4.12.3 | 0 / 28 | |
| 4.12.2 | 0 / 28 | |
| 4.12.1 | 0 / 28 | |
| 4.12.0 | 0 / 28 | |
| 4.11.1 | 0 / 28 | |
| 4.11.0 | 0 / 28 | |
| 4.10.7 | 0 / 28 | |
| 4.10.6 | 0 / 28 | |
| 3.4.1 | 2 / 20 | |
| 5.0.0-beta.2 | 0 / 28 | |
| 5.0.0-beta.1 | 0 / 28 | |
| 4.17.2-beta.1 | 0 / 28 |
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.