@mescius/wijmo.angular2.chart.hierarchical
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:es2022-fesm.mjs | AI (source-diff): Standard Angular FESM bundle output with Wijmo copyright header; not obfuscation. | ai | |
| phantom-deps | phantom-dep:@mescius/wijmo | AI (phantom-deps): Same-org modular package; declared as peer/transitive dep, not directly imported by design. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo | AI (dependencies): Same-org @mescius scoped dependency; stable pattern across all Wijmo package versions. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.chart.hierarchical | AI (dependencies): Same-org @mescius scoped dependency; stable pattern across all Wijmo package versions. | ai | |
| dependencies | unvetted-dep:@mescius/wijmo.angular2.directivebase | AI (dependencies): Same-org @mescius scoped dependency; stable pattern across all Wijmo package versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 5.20261.52 | 4 / 0 | |
| 5.20261.50 | 3 / 0 | |
| 5.20261.48 | 3 / 0 | |
| 5.20252.44 | 3 / 0 | |
| 5.20252.42 | 3 / 0 | |
| 5.20251.40 | 3 / 0 | |
| 5.20251.34 | 3 / 0 | |
| 5.20242.30 | 3 / 0 | |
| 5.20242.21 | 3 / 0 | |
| 5.20241.19 | 3 / 0 |
v5.20261.52
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20251.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20242.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20242.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20241.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.