@crystaldesign/grid
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@mui/lab | AI (phantom-deps): Listed as runtime dep in package.json; phantom-dep heuristic misfires for config-referenced deps. | ai | |
| phantom-deps | phantom-dep:jsonpath | AI (phantom-deps): Listed as runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): Listed as runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:assign-deep | AI (phantom-deps): Listed as runtime dep; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped grid component; levenshtein match to 'uuid' is a false positive with no functional or naming resemblance. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Private commercial package; missing public metadata (repo, description, keywords) is expected for internal libraries. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 26.5.0 | 20 / 7 | |
| 26.4.5 | 20 / 7 | |
| 26.4.3 | 20 / 7 | |
| 26.4.2 | 20 / 7 | |
| 26.1.1 | 20 / 7 | |
| 25.14.4 | 20 / 7 | |
| 25.14.2 | 20 / 7 | |
| 25.13.4 | 20 / 7 |
v26.5.0
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.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.1.1
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.