@antv/g2
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/g2.lite.min.js | AI (source-diff): Minified rollup/terser bundle output; long strings are build artifacts, stable for this package. | ai | |
| source-diff | encoded-string-file:dist/g2.min.js | AI (source-diff): Minified rollup/terser bundle output; long strings are build artifacts, stable for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size jump consistent with lib/esm/dist rebuild, no malicious content found. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large monorepo rebuild artifact, not injected payload, for this established package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Normal AntV org maintainer roster update. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @antv/g2 is the canonical AntV charting lib, not a typosquat of 'pg'. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @antv/g2 is the canonical AntV charting lib, not a typosquat of 'qs'. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @antv/g2 is the canonical AntV charting lib, not a typosquat of 'got'. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.4.8 | 12 / 49 | |
| 5.4.7 | 12 / 49 | |
| 5.4.6 | 12 / 49 | |
| 5.4.5 | 12 / 49 | |
| 5.4.4 | 12 / 49 | |
| 5.4.3 | 12 / 49 | |
| 5.3.1 | 13 / 47 |
v5.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.7
4 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (interstellarmt) than the most recent previously approved version (moayuisuda) on 2025-12-09, but interstellarmt 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.
v5.4.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (moayuisuda) than the most recent previously approved version (kn9117) on 2025-11-26, but moayuisuda 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.
v5.4.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (moayuisuda) than the most recent previously approved version (kn9117) on 2025-11-21, but moayuisuda 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.
v5.4.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (moayuisuda) than the most recent previously approved version (interstellarmt) on 2025-11-12, but moayuisuda 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.
v5.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.