@digital-ai/dot-components
A component library the follows the Dot 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 | encoded-string-file:index.esm.js | AI (source-diff): Encoded strings are base64 SVG logos in mock/test data, not obfuscated payloads. Stable pattern for this component library. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): @emotion/react is a peer/config-level dep for MUI; not directly imported in source is expected for this component library. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): @emotion/styled is a peer/config-level dep for MUI; same pattern as @emotion/react, stable false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 5.12.0 | 11 / 0 | |
| 5.11.0 | 11 / 0 | |
| 5.10.0 | 11 / 0 | |
| 5.9.0 | 11 / 0 | |
| 5.8.0 | 11 / 0 | |
| 5.7.0 | 11 / 0 | |
| 5.6.0 | 11 / 0 | |
| 5.5.1 | 11 / 0 | |
| 5.4.0 | 11 / 0 | |
| 5.3.0 | 11 / 0 | |
| 5.2.0 | 11 / 0 | |
| 5.1.0 | 11 / 0 | |
| 5.0.0 | 11 / 0 |
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.