@antv/g
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a declared runtime dep used by transpiled output; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @antv/g is a legitimate scoped AntV package; Levenshtein match to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @antv/g is a legitimate scoped AntV package; Levenshtein match to 'got' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @antv/g is a legitimate scoped AntV package; Levenshtein match to 'qs' is a false positive. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 6.3.1 | 5 / 0 | |
| 6.3.0 | 5 / 0 | |
| 6.2.0 | 5 / 0 | |
| 6.1.27 | 5 / 0 | |
| 6.1.26 | 5 / 0 | |
| 6.1.25 | 5 / 0 | |
| 6.1.24 | 5 / 0 |
v6.3.1
2 findingsPackage name '@antv/g' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.