@mescius/wijmo.angular.chart.finance.analytics
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Stable for this publisher; no provenance attestation is consistent across versions. | ai | |
| phantom-deps | phantom-dep:@mescius/wijmo | AI (phantom-deps): Same-org sibling package; declared as peer/transitive dep, not a direct import by design. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo | AI (dependencies): Same-org sibling package at matching pinned version; stable pattern across all Wijmo releases. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.angular.base | AI (dependencies): Same-org sibling package at matching pinned version. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.angular.chart | AI (dependencies): Same-org sibling package at matching pinned version. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.chart.finance.analytics | AI (dependencies): Same-org sibling package at matching pinned version. | 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 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. Consider requesting the maintainer enable provenance via CI/CD.
v5.20252.44
1 findingPackage 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.