@stenajs-webui/grid-export
This package adds ability to export Excel (.xlsx) documents.
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Scoped package with stable history; empty description is benign metadata gap. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is uncommon; not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:zipcelx | AI (dependencies): zipcelx is a legitimate Excel export library; its use is consistent with this grid-export package's purpose. | ai | |
| dependencies | unvetted-dep:@types/zipcelx | AI (dependencies): Type definitions for zipcelx; benign companion to the accepted zipcelx dependency. | ai | |
| phantom-deps | phantom-dep:@types/zipcelx | AI (phantom-deps): Type-only package; not directly imported but used for type resolution — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@stenajs-webui/core | AI (phantom-deps): Same-org monorepo sibling; indirect usage via re-exports is expected — stable false positive. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 23.18.0 | 8 / 6 | |
| 23.17.3 | 8 / 6 | |
| 23.17.2 | 8 / 6 | |
| 23.17.1 | 8 / 6 | |
| 23.17.0 | 8 / 6 | |
| 23.16.3 | 8 / 6 | |
| 23.16.2 | 8 / 6 | |
| 23.16.1 | 8 / 6 | |
| 23.16.0 | 8 / 6 | |
| 23.15.3 | 8 / 6 | |
| 23.15.2 | 8 / 6 | |
| 23.15.0 | 8 / 6 | |
| 23.13.2 | 8 / 6 | |
| 23.13.0 | 8 / 6 | |
| 23.12.11 | 8 / 6 | |
| 23.12.10 | 8 / 6 | |
| 23.12.9 | 8 / 6 | |
| 23.12.7 | 8 / 6 | |
| 23.12.5 | 8 / 6 | |
| 23.12.2 | 8 / 6 | |
| 23.12.1 | 8 / 6 | |
| 23.11.1 | 8 / 6 | |
| 23.10.0 | 8 / 6 | |
| 23.9.0 | 8 / 6 | |
| 23.8.0 | 8 / 6 | |
| 23.6.0 | 8 / 6 | |
| 23.5.1 | 8 / 6 | |
| 23.4.0 | 8 / 6 | |
| 23.3.0 | 8 / 6 | |
| 23.0.0 | 8 / 6 |
v23.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.16.0
1 finding[Accepted risk] Package 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.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.