@localstack/localstack-mcp-server
A LocalStack MCP Server for managing LocalStack containers with Pro support
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/44.js | AI (source-diff): Standard webpack chunk output from xmcp build; content is LocalStack tool logic, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/466.js | AI (source-diff): Standard webpack chunk output from xmcp build; content is LocalStack config/client logic. | ai | |
| source-diff | net-exec-file:dist/44.js | AI (source-diff): Network calls are to LocalStack endpoints; dynamic execution is webpack module system boilerplate. | ai | |
| source-diff | obfuscated-file:dist/235.js | AI (source-diff): Same webpack chunk pattern as dist/184.js; no malicious content. | ai | |
| source-diff | obfuscated-file:dist/184.js | AI (source-diff): Standard webpack/xmcp build chunk; numeric chunk IDs and LocalStack config constants confirm legitimate build output. | ai | |
| source-diff | obfuscated-file:dist/780.js | AI (source-diff): Same webpack chunk pattern; legitimate build artifact. | ai | |
| source-diff | obfuscated-file:dist/956.js | AI (source-diff): Same webpack chunk pattern; legitimate build artifact. | ai | |
| phantom-deps | phantom-dep:xmcp | AI (phantom-deps): xmcp is the build framework; invoked via scripts, not direct import — stable false positive. | ai | |
| phantom-deps | phantom-dep:posthog-node | AI (phantom-deps): Declared runtime dep for telemetry; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared runtime dep used via xmcp build toolchain; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:dockerode | AI (phantom-deps): Declared runtime dep for Docker management; phantom detection is a false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 4 / 10 | |
| 0.3.0 | 4 / 10 | |
| 0.2.0 | 4 / 8 | |
| 0.1.5 | 3 / 8 | |
| 0.1.4 | 3 / 7 | |
| 0.1.3 | 2 / 6 | |
| 0.1.2 | 2 / 6 | |
| 0.1.1 | 2 / 1 |
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.