@omegagrid/plugin-xlsx
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 | url-dep:xlsx | AI (npm-metadata): xlsx URL dep is devDependencies-only; SheetJS CDN is their documented distribution channel, not shipped to consumers. | ai | |
| phantom-deps | phantom-dep:lit | AI (phantom-deps): lit is a runtime dep declared in package.json; phantom-dep heuristic fires because it's referenced via config, not direct import. | ai | |
| phantom-deps | phantom-dep:lit-html | AI (phantom-deps): Same as lit — declared runtime dep, config-referenced pattern is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ts-debounce | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic is a stable false positive for this package. | ai |
Versions (showing 27 of 229)
| Version | Deps | Published |
|---|---|---|
| 0.6.60 | 6 / 21 | |
| 0.6.59 | 6 / 21 | |
| 0.6.58 | 6 / 21 | |
| 0.6.57 | 6 / 21 | |
| 0.6.56 | 6 / 21 | |
| 0.6.55 | 6 / 21 | |
| 0.6.54 | 6 / 21 | |
| 0.6.53 | 6 / 21 | |
| 0.6.52 | 6 / 21 | |
| 0.6.51 | 6 / 21 | |
| 0.6.50 | 6 / 21 | |
| 0.6.49 | 6 / 21 | |
| 0.6.48 | 6 / 21 | |
| 0.6.47 | 6 / 21 | |
| 0.6.46 | 6 / 21 | |
| 0.6.45 | 6 / 21 | |
| 0.6.44 | 6 / 21 | |
| 0.6.43 | 6 / 21 | |
| 0.6.42 | 6 / 21 | |
| 0.6.41 | 6 / 21 | |
| 0.6.40 | 6 / 21 | |
| 0.6.39 | 6 / 21 | |
| 0.6.38 | 6 / 21 | |
| 0.6.37 | 6 / 21 | |
| 0.6.36 | 6 / 21 | |
| 0.6.35 | 6 / 21 | |
| 0.6.34 | 6 / 21 |
v0.6.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.