@mescius/wijmo.react.olap
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:@mescius/wijmo.grid | AI (phantom-deps): Same-org sibling dep; declared as dependency and used transitively within the Wijmo suite. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo | AI (dependencies): Same-org Wijmo core package; stable sibling dependency pattern across all versions. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.grid | AI (dependencies): Same-org Wijmo sibling; consistent pinned versioning pattern. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.olap | AI (dependencies): Same-org Wijmo sibling; consistent pinned versioning pattern. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.chart | AI (dependencies): Same-org Wijmo sibling; consistent pinned versioning pattern. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.react.base | AI (dependencies): Same-org Wijmo sibling; consistent pinned versioning pattern. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.react.grid | AI (dependencies): Same-org Wijmo sibling; consistent pinned versioning pattern. | 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20252.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.