@salesforce/ui-design-mode
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/authoring/react/index.js | AI (source-diff): Standard Vite-bundled React output; minification is expected for this package's dist artifacts. | ai | |
| source-diff | obfuscated-file:dist/authoring/web-component/index.js | AI (source-diff): Standard Vite-bundled web-component output; minification is expected for this package's dist artifacts. | ai | |
| phantom-deps | phantom-dep:downshift | AI (phantom-deps): Bundled into dist; phantom-dep heuristic fires because imports are resolved at build time. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): Bundled into dist; phantom-dep heuristic fires because imports are resolved at build time. | ai | |
| phantom-deps | phantom-dep:use-debounce | AI (phantom-deps): Bundled into dist; phantom-dep heuristic fires because imports are resolved at build time. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-icons | AI (phantom-deps): Bundled into dist; phantom-dep heuristic fires because imports are resolved at build time. | ai | |
| phantom-deps | phantom-dep:react-beautiful-color | AI (phantom-deps): Bundled into dist; phantom-dep heuristic fires because imports are resolved at build time. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-toggle-group | AI (phantom-deps): Bundled into dist; phantom-dep heuristic fires because imports are resolved at build time. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 10.6.0 | 8 / 14 | |
| 10.5.1 | 8 / 13 | |
| 10.4.1 | 8 / 13 | |
| 10.3.0 | 8 / 13 | |
| 10.2.2 | 1 / 8 | |
| 10.2.1 | 1 / 8 | |
| 10.2.0 | 1 / 8 |
v10.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.1
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.