@crystaldesign/product-detail-page
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): Established internal component library with 1671 versions; sparse metadata is consistent across all versions, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:react-laag | AI (phantom-deps): Declared runtime dep referenced in config; phantom-dep heuristic fires on config-only references for this package. | ai | |
| phantom-deps | phantom-dep:react-qr-code | AI (phantom-deps): Same pattern — config-referenced dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@google/model-viewer | AI (phantom-deps): Config-referenced dep; stable false positive for this package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 26.6.3 | 7 / 19 | |
| 26.6.2 | 7 / 19 | |
| 26.6.1 | 7 / 19 | |
| 26.6.0 | 7 / 19 | |
| 26.5.3 | 7 / 19 | |
| 26.5.2 | 7 / 19 | |
| 26.5.1 | 7 / 19 | |
| 26.5.0 | 7 / 19 | |
| 26.4.8 | 7 / 19 | |
| 26.4.7 | 7 / 19 | |
| 26.4.6 | 7 / 19 | |
| 26.4.5 | 7 / 19 | |
| 26.4.4 | 7 / 19 | |
| 26.4.3 | 7 / 19 | |
| 26.4.2 | 7 / 19 | |
| 26.4.1 | 7 / 19 | |
| 26.4.0 | 7 / 19 | |
| 26.3.2 | 7 / 19 | |
| 26.3.1 | 7 / 19 | |
| 26.3.0 | 7 / 19 | |
| 26.2.4 | 7 / 19 | |
| 26.2.3 | 7 / 19 | |
| 26.2.2 | 7 / 19 | |
| 26.2.1 | 7 / 19 | |
| 26.2.0 | 7 / 19 | |
| 26.1.2 | 7 / 19 | |
| 26.1.1 | 7 / 19 | |
| 26.1.0 | 7 / 19 | |
| 25.16.2 | 7 / 19 | |
| 25.16.1 | 7 / 19 | |
| 25.16.0 | 7 / 19 | |
| 25.14.4 | 7 / 19 | |
| 25.14.3 | 7 / 19 | |
| 25.14.2 | 7 / 19 | |
| 25.14.1 | 7 / 19 | |
| 25.14.0 | 7 / 19 | |
| 25.13.7 | 7 / 19 | |
| 25.13.6 | 7 / 19 | |
| 25.13.5 | 7 / 19 | |
| 25.13.4 | 7 / 19 | |
| 25.13.3 | 7 / 19 | |
| 25.13.2 | 7 / 19 |
v26.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.13.4
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.
v25.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.