@antv/s2
effective spreadsheet render core lib
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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/s2-extends.min.js | AI (source-diff): Long strings are standard minified tslib/rollup output; stable false positive for this build artifact. | ai | |
| source-diff | encoded-string-file:dist/s2.min.js | AI (source-diff): Long strings are standard minified tslib/rollup output; stable false positive for this build artifact. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @antv/s2 is an established AntV package; Levenshtein match to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @antv/s2 is an established AntV package; Levenshtein match to 'qs' is a false positive. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.7.2 | 9 / 4 | |
| 2.7.1 | 9 / 4 | |
| 2.7.0 | 9 / 4 | |
| 2.6.0 | 9 / 4 | |
| 2.5.0 | 9 / 4 | |
| 2.4.16 | 9 / 4 | |
| 2.4.15 | 9 / 4 | |
| 2.4.14 | 9 / 4 | |
| 2.4.13 | 9 / 4 | |
| 2.4.12 | 9 / 4 | |
| 2.4.11 | 9 / 4 | |
| 2.4.10 | 9 / 4 |
v2.6.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (alex_zjt) on 2026-02-09, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.13
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 (alex_zjt) than the most recent previously approved version (jinke.li) on 2025-12-26, but alex_zjt 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.4.12
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 (alex_zjt) than the most recent previously approved version (jinke.li) on 2025-12-25, but alex_zjt 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.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.