@mescius/wijmo.grid.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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@mescius/wijmo | AI (dependencies): Same-org sibling package, pinned to matching version; stable pattern across all Wijmo releases. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.grid | AI (dependencies): Same-org sibling package, pinned to matching version; stable pattern across all Wijmo releases. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.xlsx | AI (dependencies): Same-org sibling package, pinned to matching version; stable pattern across all Wijmo releases. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.input | AI (dependencies): Same-org sibling package, pinned to matching version; stable pattern across all Wijmo releases. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.grid.detail | AI (dependencies): Same-org sibling package, pinned to matching version; stable pattern across all Wijmo releases. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.grid.multirow | AI (dependencies): Same-org sibling package, pinned to matching version; stable pattern across all Wijmo releases. | ai | |
| phantom-deps | phantom-dep:@mescius/wijmo.input | AI (phantom-deps): Same-org dep declared for transitive resolution; not directly imported but legitimately listed. | ai | |
| provenance | no-provenance | AI (provenance): Commercial closed-source publisher; no provenance is expected and consistent across all versions. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.20261.50 | 6 / 0 | |
| 5.20261.48 | 6 / 0 | |
| 5.20252.44 | 6 / 0 | |
| 5.20252.42 | 6 / 0 | |
| 5.20251.40 | 6 / 0 |
v5.20261.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20261.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20252.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20252.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20251.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.