@3mo/data-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@3mo/menu | AI (phantom-deps): Same-org monorepo component; phantom-dep heuristic unreliable for peer/transitive usage patterns in web component libraries. | ai | |
| phantom-deps | phantom-dep:@3mo/select-field | AI (phantom-deps): Same-org monorepo component; phantom-dep heuristic unreliable for this package's usage patterns. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.31.0 | 34 / 0 | |
| 0.30.1 | 34 / 0 | |
| 0.30.0 | 34 / 0 | |
| 0.29.4 | 33 / 0 | |
| 0.29.3 | 33 / 0 | |
| 0.29.2 | 33 / 0 | |
| 0.29.1 | 33 / 0 | |
| 0.29.0 | 33 / 0 | |
| 0.28.0 | 32 / 0 | |
| 0.27.0 | 32 / 0 | |
| 0.26.4 | 32 / 0 | |
| 0.26.3 | 32 / 0 | |
| 0.26.2 | 32 / 0 | |
| 0.26.1 | 32 / 0 | |
| 0.26.0 | 32 / 0 | |
| 0.25.2 | 32 / 0 | |
| 0.25.1 | 32 / 0 | |
| 0.25.0 | 32 / 0 | |
| 0.24.0 | 32 / 0 | |
| 0.23.0 | 32 / 0 | |
| 0.22.3 | 32 / 0 | |
| 0.22.2 | 32 / 0 | |
| 0.22.1 | 32 / 0 | |
| 0.22.0 | 32 / 0 | |
| 0.21.5 | 32 / 0 | |
| 0.21.2 | 32 / 0 | |
| 0.21.1 | 32 / 0 | |
| 0.21.0 | 32 / 0 | |
| 0.20.3 | 32 / 0 | |
| 0.20.2 | 32 / 0 | |
| 0.20.1 | 32 / 0 | |
| 0.20.0 | 32 / 0 | |
| 0.19.4 | 32 / 0 | |
| 0.19.3 | 32 / 0 | |
| 0.19.2 | 32 / 0 | |
| 0.19.1 | 33 / 0 | |
| 0.19.0 | 33 / 0 | |
| 0.18.0 | 33 / 0 | |
| 0.17.2 | 33 / 0 | |
| 0.17.0 | 33 / 0 | |
| 0.16.1 | 33 / 0 | |
| 0.16.0 | 33 / 0 |
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.