@crystaldesign/diva-seller
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Private commercial component library; sparse public metadata is expected and consistent across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Private commercial package; missing description is consistent across versions. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Emotion is a peer/config-level dep in MUI-based packages; not directly imported but legitimately referenced. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Same as @emotion/react — MUI config pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:react-error-boundary | AI (phantom-deps): Likely re-exported or used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@crystaldesign/real-time-viewer | AI (phantom-deps): Same-org dep; phantom flag is a heuristic false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 26.5.0 | 11 / 7 | |
| 26.4.6 | 11 / 7 | |
| 25.14.4 | 11 / 7 | |
| 25.14.3 | 11 / 7 | |
| 25.14.0 | 11 / 7 | |
| 25.13.6 | 11 / 7 | |
| 25.13.5 | 11 / 7 | |
| 25.13.3 | 11 / 7 |
v26.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.