@mescius/wijmo.undo
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): Sibling package in the same @mescius/wijmo suite; pinned to matching version, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.nav | AI (dependencies): Sibling package in the same @mescius/wijmo suite; pinned to matching version. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.grid | AI (dependencies): Sibling package in the same @mescius/wijmo suite; pinned to matching version. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.gauge | AI (dependencies): Sibling package in the same @mescius/wijmo suite; pinned to matching version. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.input | AI (dependencies): Sibling package in the same @mescius/wijmo suite; pinned to matching version. | ai | |
| provenance | no-provenance | AI (provenance): Commercial library; provenance attestation not expected for this publisher's release pipeline. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.20261.50 | 5 / 0 | |
| 5.20261.48 | 5 / 0 | |
| 5.20252.44 | 5 / 0 | |
| 5.20252.42 | 5 / 0 | |
| 5.20251.40 | 5 / 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 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.