@antv/gpt-vis-ssr
SSR(Server Side Render) for AntV GPT-Vis.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is an in-org @antv scoped package consistent with the project's rendering stack. | ai | |
| source-diff | obfuscated-file:dist/esm/vis/waterfall.js | AI (source-diff): Long lines are standard minified bundle output (regenerator-runtime); not obfuscation. | ai | |
| dependencies | unvetted-dep:canvas | AI (dependencies): canvas is a well-known native Node.js binding; expected dependency for SSR rendering in this package. | ai | |
| dependencies | unvetted-dep:@antv/gpt-vis | AI (dependencies): First-party AntV org dependency; same publisher org as this package. | ai | |
| provenance | no-provenance | AI (provenance): AntV org package; no provenance is common and not a risk signal here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.3.7 | 7 / 10 | |
| 0.3.6 | 6 / 10 | |
| 0.3.4 | 6 / 10 | |
| 0.3.3 | 5 / 11 | |
| 0.3.0 | 5 / 11 | |
| 0.1.10 | 5 / 11 | |
| 0.1.6 | 4 / 11 |
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atool) than the most recent previously approved version (duxinyue023) on 2025-07-23, but atool 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.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.