@antv/l7-component
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@antv/l7-layers | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@antv/l7-core | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@antv/l7-utils | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped Babel runtime; loaded by convention, stable false positive. | ai | |
| phantom-deps | phantom-dep:supercluster | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eventemitter3 | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Large AntV monorepo; provenance not part of their publish workflow across all versions. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.28.12 | 6 / 2 | |
| 2.28.11 | 6 / 2 | |
| 2.28.10 | 6 / 2 | |
| 2.25.10 | 6 / 2 | |
| 2.25.9 | 6 / 2 | |
| 2.25.7 | 6 / 2 | |
| 2.25.6 | 6 / 2 | |
| 2.25.5 | 6 / 2 | |
| 2.25.4 | 6 / 2 | |
| 2.25.3 | 6 / 2 | |
| 2.25.2 | 6 / 2 | |
| 2.24.3 | 6 / 2 | |
| 2.24.1 | 6 / 2 | |
| 2.24.0 | 6 / 2 | |
| 2.23.2 | 6 / 2 | |
| 2.23.1 | 6 / 2 | |
| 2.23.0 | 6 / 2 | |
| 2.22.7 | 6 / 2 | |
| 2.22.6 | 6 / 2 |
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 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 finding[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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.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.24.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.23.2
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.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.