@camunda/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, so a manually published version cannot be tied back to a reviewed commit.
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/examples/cost-dashboard/CostDashboardPage.js | AI (source-diff): Readable JSX example code, long lines are minified-style single-line output not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/examples/project-detail/ProjectDetailPage.js | AI (source-diff): Readable JSX example code, same build pattern as sibling file. | ai | |
| phantom-deps | phantom-dep:shadcn | AI (phantom-deps): Used via config/CLI (shadcn.json), not a direct import. | ai | |
| phantom-deps | phantom-dep:@fontsource/geist-sans | AI (phantom-deps): Used in build:fonts script to copy font files, not imported in source. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.35.0 | 11 / 41 | |
| 0.34.0 | 11 / 41 | |
| 0.33.0 | 11 / 41 | |
| 0.32.2 | 11 / 41 | |
| 0.32.1 | 11 / 41 | |
| 0.32.0 | 11 / 41 | |
| 0.31.0 | 11 / 41 | |
| 0.30.0 | 11 / 41 | |
| 0.29.0 | 11 / 41 | |
| 0.28.0 | 11 / 41 | |
| 0.27.0 | 11 / 41 | |
| 0.26.0 | 11 / 41 | |
| 0.25.0 | 11 / 41 | |
| 0.24.0 | 11 / 41 | |
| 0.23.0 | 11 / 41 | |
| 0.22.0 | 11 / 41 | |
| 0.21.1 | 11 / 41 | |
| 0.21.0 | 10 / 42 | |
| 0.20.0 | 10 / 42 | |
| 0.14.0 | 12 / 40 | |
| 0.2.0 | 10 / 40 | |
| 0.1.0 | 10 / 39 |
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
4 findingsThis version was published by a different npm account than previous versions on 2026-06-28. This could indicate a legitimate maintainer transition or an account compromise.
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.2.0
4 findingsThis version was published by a different npm account than previous versions on 2026-06-18. This could indicate a legitimate maintainer transition or an account compromise.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.