@mcp-ui/server
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 | obfuscated-file:dist/src/adapters/mcp-apps/adapter-runtime.bundled.d.ts | AI (source-diff): File is a .d.ts embedding a bundled adapter script as a string constant; readable MCP adapter code, not malicious obfuscation. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped MCP UI SDK package; name similarity to semver is coincidental, not a typosquat. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 2 / 7 | |
| 6.0.1 | 2 / 7 | |
| 6.0.0 | 2 / 7 | |
| 5.16.3 | 2 / 7 | |
| 5.16.2 | 1 / 7 | |
| 5.16.1 | 1 / 7 | |
| 5.16.0 | 1 / 7 | |
| 5.15.0 | 1 / 7 | |
| 5.14.0 | 1 / 7 |
v6.1.0
2 findingsPackage name '@mcp-ui/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.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.
v6.0.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.
v5.16.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.
v5.16.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.
v5.16.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.
v5.16.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.
v5.15.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.
v5.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.