@antv/l7
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 an established AntV org publisher with 150 approved packages; transition appears legitimate. | ai | |
| dependencies | unvetted-dep:@antv/l7-scene | AI (dependencies): First-party sibling package in the @antv/l7 monorepo, pinned to matching version. | ai | |
| phantom-deps | phantom-dep:@antv/l7-maps | AI (phantom-deps): Umbrella package re-exports same-org sub-packages; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@antv/l7-scene | AI (phantom-deps): Umbrella package re-exports same-org sub-packages; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@antv/l7-utils | AI (phantom-deps): Umbrella package re-exports same-org sub-packages; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@antv/l7-core | AI (phantom-deps): Umbrella package re-exports same-org sub-packages; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@antv/l7-layers | AI (phantom-deps): Umbrella package re-exports same-org sub-packages; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@antv/l7-source | AI (phantom-deps): Umbrella package re-exports same-org sub-packages; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@antv/l7-component | AI (phantom-deps): Umbrella package re-exports same-org sub-packages; not directly imported by design. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @antv/l7 package; Levenshtein match to 'pg' is a false positive for this well-known org. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @antv/l7 package; Levenshtein match to 'qs' is a false positive for this well-known org. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a standard runtime dep loaded by convention in transpiled packages; stable false positive. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.28.11 | 8 / 0 | |
| 2.28.10 | 8 / 0 | |
| 2.25.10 | 8 / 0 | |
| 2.25.9 | 8 / 0 | |
| 2.25.7 | 8 / 0 | |
| 2.25.6 | 8 / 0 | |
| 2.25.5 | 8 / 0 | |
| 2.25.4 | 8 / 0 | |
| 2.25.3 | 8 / 0 | |
| 2.25.2 | 8 / 0 | |
| 2.25.1 | 8 / 0 | |
| 2.25.0 | 8 / 0 | |
| 2.24.3 | 8 / 0 | |
| 2.24.2 | 8 / 0 | |
| 2.24.1 | 8 / 0 | |
| 2.24.0 | 8 / 0 | |
| 2.23.2 | 8 / 0 | |
| 2.23.1 | 8 / 0 | |
| 2.23.0 | 8 / 0 | |
| 2.22.7 | 8 / 0 | |
| 2.22.6 | 8 / 0 |
v2.28.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.10
1 findingPackage 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
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 (lzxue) than the most recent previously approved version (yanxiong) on 2026-03-12, but lzxue 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.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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
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 (lzxue) than the most recent previously approved version (lvisei) on 2026-03-10, but lzxue 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.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.1
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 (lvisei) than the most recent previously approved version (lzxue) on 2025-11-14, but lvisei 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.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.