@aws/run-mcp-servers-with-aws-lambda
Run Model Context Protocol (MCP) servers with AWS Lambda
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual (cliguori) to GitHub Actions CI/CD publishing under awslabs org; SLSA attestation confirms legitimate pipeline. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD automation is a common pattern for AWS Labs packages; SLSA attestation confirms integrity. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 0.5.21 | 8 / 16 | |
| 0.5.20 | 8 / 16 | |
| 0.5.19 | 8 / 15 | |
| 0.5.18 | 8 / 15 | |
| 0.5.17 | 8 / 15 | |
| 0.5.16 | 8 / 15 | |
| 0.5.15 | 8 / 15 | |
| 0.5.14 | 8 / 15 | |
| 0.5.13 | 8 / 15 | |
| 0.5.12 | 8 / 15 | |
| 0.5.11 | 8 / 15 | |
| 0.5.10 | 8 / 15 | |
| 0.5.9 | 8 / 15 | |
| 0.5.8 | 8 / 15 | |
| 0.5.7 | 8 / 15 | |
| 0.5.6 | 8 / 15 | |
| 0.5.5 | 8 / 15 | |
| 0.5.4 | 8 / 15 | |
| 0.5.3 | 8 / 14 | |
| 0.5.2 | 8 / 14 | |
| 0.5.1 | 8 / 14 | |
| 0.5.0 | 8 / 14 | |
| 0.4.8 | 8 / 14 | |
| 0.4.7 | 8 / 14 | |
| 0.4.6 | 8 / 14 | |
| 0.4.5 | 8 / 14 | |
| 0.4.4 | 8 / 14 | |
| 0.4.3 | 8 / 14 | |
| 0.4.2 | 8 / 14 | |
| 0.4.1 | 8 / 14 | |
| 0.4.0 | 8 / 14 | |
| 0.3.5 | 8 / 14 | |
| 0.3.4 | 8 / 14 | |
| 0.3.3 | 9 / 13 | |
| 0.3.2 | 9 / 13 | |
| 0.3.1 | 9 / 13 | |
| 0.3.0 | 9 / 13 | |
| 0.2.4 | 9 / 12 | |
| 0.2.3 | 4 / 12 | |
| 0.2.2 | 4 / 12 | |
| 0.2.1 | 4 / 12 | |
| 0.2.0 | 4 / 12 | |
| 0.1.6 | 4 / 12 | |
| 0.1.5 | 4 / 12 | |
| 0.1.4 | 4 / 12 | |
| 0.1.3 | 4 / 12 | |
| 0.1.2 | 4 / 12 | |
| 0.1.1 | 4 / 12 | |
| 0.1.0 | 4 / 12 | |
| 0.0.1 | 4 / 12 |
v0.5.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.