@apideck/mcp
[](https://www.npmjs.com/package/@apideck/mcp) [](https://registry.modelcontext
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects removal of bundled/generated bloat in favor of cleaner TypeScript source; not a stub replacement. | ai | |
| phantom-deps | phantom-dep:json-schema-to-zod | AI (phantom-deps): Used in generator/build scripts; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@apidevtools/swagger-parser | AI (phantom-deps): Used in generator/build scripts; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/src/tools.js | AI (source-diff): tools.js is a generated TypeScript build artifact with clear SPDX header and standard MCP/Zod imports; long lines are from generated tool definitions, not obfuscation. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Used in generator/build scripts; phantom-dep heuristic misses indirect usage patterns in this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Buffer.from(payload, 'base64') in generated runtime code for decoding binary API responses; not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @apideck/mcp; Levenshtein match to 'yup' is a false positive with no brand overlap. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 7 / 13 | |
| 0.4.0 | 7 / 13 | |
| 0.3.0 | 7 / 13 | |
| 0.2.8 | 7 / 13 | |
| 0.2.7 | 7 / 13 | |
| 0.2.6 | 7 / 13 | |
| 0.2.5 | 7 / 13 | |
| 0.2.4 | 7 / 13 | |
| 0.2.3 | 7 / 13 | |
| 0.2.2 | 7 / 13 | |
| 0.2.1 | 7 / 13 | |
| 0.2.0 | 7 / 13 | |
| 0.1.18 | 7 / 13 | |
| 0.1.17 | 7 / 13 | |
| 0.1.16 | 7 / 13 | |
| 0.1.15 | 7 / 13 | |
| 0.1.14 | 7 / 13 | |
| 0.1.13 | 6 / 12 | |
| 0.1.12 | 6 / 12 | |
| 0.1.10 | 5 / 12 | |
| 0.1.9 | 5 / 12 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsNewly 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.3.0
2 findingsNewly 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.2.8
2 findingsNewly 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.2.7
2 findingsNewly 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.2.6
2 findingsNewly 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.2.5
2 findingsNewly 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.2.4
2 findingsNewly 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.2.3
2 findingsNewly 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.2.2
2 findingsNewly 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.2.1
2 findingsNewly 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.2.0
2 findingsNewly 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.18
2 findingsNewly 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.17
2 findingsNewly 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.16
2 findingsNewly 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.15
2 findingsNewly 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.14
2 findingsNewly 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.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.