@antv/g-plugin-canvas-renderer
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:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript-compiled packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:@antv/g-math | AI (phantom-deps): Same-org dep used transitively; phantom-dep heuristic fires but this is a stable false positive for this monorepo package. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 2.5.1 | 8 / 0 | |
| 2.5.0 | 8 / 0 | |
| 2.3.2 | 8 / 0 | |
| 2.3.0 | 8 / 0 | |
| 2.2.23 | 8 / 0 | |
| 2.2.22 | 8 / 0 | |
| 2.2.21 | 8 / 0 | |
| 2.2.20 | 8 / 0 | |
| 2.2.19 | 8 / 0 | |
| 2.2.18 | 8 / 0 | |
| 2.2.17 | 8 / 0 | |
| 2.2.16 | 8 / 0 | |
| 2.2.15 | 8 / 0 | |
| 2.2.14 | 8 / 0 | |
| 2.2.13 | 8 / 0 | |
| 2.2.12 | 8 / 0 | |
| 2.2.11 | 8 / 0 | |
| 2.2.10 | 8 / 0 | |
| 2.2.9 | 8 / 0 | |
| 2.2.8 | 8 / 0 | |
| 2.2.7 | 8 / 0 | |
| 2.2.6 | 8 / 0 | |
| 2.2.5 | 8 / 0 | |
| 2.2.4 | 8 / 0 | |
| 2.2.3 | 8 / 0 | |
| 2.2.2 | 8 / 0 | |
| 2.2.1 | 8 / 0 | |
| 2.2.0 | 8 / 0 | |
| 2.1.4 | 8 / 0 | |
| 2.1.3 | 8 / 0 | |
| 2.1.2 | 8 / 0 | |
| 2.1.1 | 8 / 0 | |
| 2.1.0 | 7 / 0 | |
| 2.0.12 | 7 / 0 | |
| 2.0.11 | 7 / 0 | |
| 2.0.10 | 7 / 0 | |
| 2.0.9 | 7 / 0 | |
| 2.0.8 | 7 / 0 | |
| 2.0.7 | 7 / 0 | |
| 2.0.6 | 7 / 0 | |
| 2.0.5 | 7 / 0 | |
| 2.0.4 | 7 / 0 | |
| 2.0.3 | 7 / 0 |
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
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 (iaaron) than the most recent previously approved version (panyuqi) on 2024-07-18, 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.
v2.0.7
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 (iaaron) than the most recent previously approved version (panyuqi) on 2024-07-09, 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.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.