@antv/l7-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): lzxue is a trusted publisher (150 approved) within the AntV org; transition appears legitimate. | ai | |
| phantom-deps | phantom-dep:@antv/l7-core | AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive for monorepo bundled output. | ai | |
| phantom-deps | phantom-dep:@antv/l7-utils | AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive for monorepo bundled output. | ai | |
| phantom-deps | phantom-dep:@antv/g-device-api | AI (phantom-deps): Same-org dep; phantom detection is a false positive for monorepo bundled output. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Thin stub/re-export is expected for this monorepo sub-package; not a spam indicator. | ai | |
| phantom-deps | phantom-dep:regl | AI (phantom-deps): Monorepo build artifact; regl is a real runtime dep bundled by the build tool. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a declared dependency used as a runtime helper by transpiled output; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established AntV package; lack of provenance is consistent across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): AntV L7 monorepo packages consistently ship with empty descriptions; not a malware indicator. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.28.12 | 5 / 1 | |
| 2.28.11 | 5 / 1 | |
| 2.28.10 | 5 / 1 | |
| 2.25.10 | 5 / 1 | |
| 2.25.9 | 5 / 1 | |
| 2.25.7 | 5 / 1 | |
| 2.25.6 | 5 / 1 | |
| 2.25.5 | 5 / 1 | |
| 2.25.4 | 5 / 1 | |
| 2.25.3 | 5 / 1 | |
| 2.25.2 | 5 / 1 | |
| 2.25.1 | 5 / 1 | |
| 2.25.0 | 5 / 1 | |
| 2.24.3 | 5 / 1 | |
| 2.24.2 | 5 / 1 | |
| 2.24.1 | 5 / 1 | |
| 2.24.0 | 5 / 1 | |
| 2.23.2 | 5 / 1 | |
| 2.23.1 | 5 / 1 | |
| 2.23.0 | 5 / 1 | |
| 2.22.7 | 5 / 1 | |
| 2.22.6 | 5 / 1 |
v2.28.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.