@preply/ds-ai-mcp
MCP server for the Preply Design System
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/create-server-DZ_NAhUM.js | AI (source-diff): Vite/Rolldown bundled output; long lines are minified bundle artifacts, not obfuscation. Expected for this build tool package. | ai | |
| source-diff | obfuscated-file:dist/create-server-Df2uutA3.js | AI (source-diff): Vite/Rolldown bundle output; long lines are minified but readable JS, not obfuscated malware. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore provenance is common and not a risk signal for this scoped org package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 11.5.0 | 3 / 5 | |
| 11.4.0 | 3 / 5 | |
| 11.3.0 | 3 / 5 | |
| 11.2.0 | 3 / 5 | |
| 11.1.0 | 3 / 5 |
v11.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.