← Home

@mescius/wijmo.react.chart.annotation

npm Homepage
5
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mescius

Keywords

controlcomponentuicontrol librarycomponent libraryui librarycontrol-librarycomponent-libraryui-librarygriddata griddata-griddatagridangular gridreact gridvue gridangular-gridreact-gridvue-grid

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@mescius/wijmo AI (dependencies): Sibling package from same org/publisher; expected dependency for Wijmo suite. ai
dependencies unvetted-dep:@mescius/wijmo.chart AI (dependencies): Sibling package from same org/publisher; expected dependency for Wijmo suite. ai
dependencies unvetted-dep:@mescius/wijmo.react.base AI (dependencies): Sibling package from same org/publisher; expected dependency for Wijmo suite. ai
dependencies unvetted-dep:@mescius/wijmo.react.chart AI (dependencies): Sibling package from same org/publisher; expected dependency for Wijmo suite. ai
dependencies unvetted-dep:@mescius/wijmo.chart.annotation AI (dependencies): Sibling package from same org/publisher; expected dependency for Wijmo suite. ai
phantom-deps phantom-dep:@mescius/wijmo.react.chart AI (phantom-deps): Declared sibling dep in same org scope; stable false positive for this package. ai
provenance no-provenance AI (provenance): Commercial SDK publisher; no provenance is consistent across all Wijmo packages. 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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.20261.48

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.20252.44

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.20252.42

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.20251.40

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.