@antv/util
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 | missing-githead | AI (provenance): Known maintainer manual publish on a trusted high-download package; not tampering. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Standard src/lib/esm/dist output for this build-tool package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): husky install git-hook setup; no network or code exec. Stable for this package. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @antv/util is a legitimate AntV utility package; Levenshtein match to 'uuid' is a false positive. | ai | |
| phantom-deps | phantom-dep:fast-deep-equal | AI (phantom-deps): fast-deep-equal is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.3.11 | 3 / 26 | |
| 3.3.10 | 3 / 25 | |
| 3.3.9 | 3 / 25 | |
| 3.3.8 | 3 / 23 |
v3.3.10
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: iaaron.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (iaaron) than the most recent previously approved version (atool) on 2024-09-19, but iaaron is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.3.9
3 findingsScript: husky install
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (iaaron) than the most recent previously approved version (atool) on 2024-09-19, but iaaron is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.