← Home

@mescius/wijmo.angular.chart.hierarchical

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): Same-org sibling dependency; standard for the Wijmo modular package family. ai
dependencies unvetted-dep:@mescius/wijmo.angular.base AI (dependencies): Same-org sibling dependency; standard for the Wijmo modular package family. ai
dependencies unvetted-dep:@mescius/wijmo.chart.hierarchical AI (dependencies): Same-org sibling dependency; standard for the Wijmo modular package family. ai
phantom-deps phantom-dep:@mescius/wijmo AI (phantom-deps): Same-org scope dependency; stable false positive for this package family. ai
provenance no-provenance AI (provenance): Commercial closed-source package; no provenance is expected and consistent across all versions. ai

Versions (showing 5 of 5)

Version Deps Published
5.20261.50 4 / 0
5.20261.48 4 / 0
5.20252.44 4 / 0
5.20252.42 4 / 0
5.20251.40 4 / 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
INFO No provenance attestation provenance

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

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.