@stenajs-webui/grid
This package contains hooks and components that can help create grids that can be navigated similar to Excel.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from individual maintainer to GitHub Actions CI is a documented pattern for this established StenaIT monorepo. | ai | |
| dependencies | unvetted-dep:@stenajs-webui/core | AI (dependencies): Sibling package in the same StenaIT monorepo; not an external unvetted dependency. | ai | |
| dependencies | unvetted-dep:@stenajs-webui/forms | AI (dependencies): Sibling package in the same StenaIT monorepo. | ai | |
| dependencies | unvetted-dep:@stenajs-webui/redux | AI (dependencies): Sibling package in the same StenaIT monorepo. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped monorepo package; name similarity to uuid is coincidental and not impersonation. | ai | |
| dependencies | unvetted-dep:@stenajs-webui/tooltip | AI (dependencies): Sibling package in the same StenaIT monorepo. | ai | |
| dependencies | unvetted-dep:@stenajs-webui/elements | AI (dependencies): Sibling package in the same StenaIT monorepo. | ai | |
| dependencies | unvetted-dep:@stenajs-webui/panels | AI (dependencies): Sibling package in the same StenaIT monorepo. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 23.18.0 | 9 / 12 | |
| 23.17.3 | 9 / 12 | |
| 23.17.2 | 9 / 12 | |
| 23.17.1 | 9 / 12 | |
| 23.17.0 | 9 / 12 | |
| 23.16.3 | 9 / 12 | |
| 23.16.2 | 9 / 12 | |
| 23.16.1 | 9 / 12 | |
| 23.16.0 | 9 / 12 | |
| 23.15.3 | 9 / 12 | |
| 23.15.2 | 9 / 12 | |
| 23.15.1 | 9 / 12 | |
| 23.15.0 | 9 / 12 | |
| 23.14.0 | 9 / 12 | |
| 23.13.3 | 9 / 12 | |
| 23.13.2 | 9 / 12 | |
| 23.13.1 | 9 / 12 | |
| 23.13.0 | 9 / 12 | |
| 23.12.11 | 9 / 12 | |
| 23.12.10 | 9 / 12 | |
| 23.12.9 | 9 / 12 | |
| 23.12.8 | 9 / 12 | |
| 23.12.7 | 9 / 12 | |
| 23.12.6 | 9 / 12 | |
| 23.12.5 | 9 / 12 | |
| 23.12.4 | 9 / 12 | |
| 23.12.3 | 9 / 12 | |
| 23.12.2 | 9 / 12 | |
| 23.12.1 | 9 / 12 | |
| 23.12.0 | 9 / 12 | |
| 23.11.3 | 9 / 13 | |
| 23.11.2 | 9 / 13 | |
| 23.11.1 | 9 / 13 | |
| 23.11.0 | 9 / 13 | |
| 23.10.0 | 9 / 13 | |
| 23.9.0 | 9 / 13 | |
| 23.8.1 | 9 / 13 | |
| 23.8.0 | 9 / 13 | |
| 23.7.1 | 9 / 13 | |
| 23.7.0 | 9 / 13 | |
| 23.6.0 | 9 / 13 | |
| 23.5.1 | 9 / 13 | |
| 23.5.0 | 9 / 13 | |
| 23.4.0 | 9 / 13 | |
| 23.3.1 | 9 / 13 | |
| 23.3.0 | 9 / 13 | |
| 23.2.0 | 9 / 13 | |
| 23.1.0 | 9 / 13 | |
| 23.0.0 | 9 / 13 |
v23.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.3.1
2 findingsThis version was published by a different npm account than previous versions on 2025-10-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.3.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.