@antv/l7-map
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:gl-matrix | AI (phantom-deps): Bundled monorepo package; deps referenced in config/re-exports, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:eventemitter3 | AI (phantom-deps): Same bundled monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:@antv/l7-utils | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo re-exports. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dep loaded by convention; stable FP. | ai | |
| phantom-deps | phantom-dep:@mapbox/unitbezier | AI (phantom-deps): Referenced in config files; stable FP for this bundled package. | ai | |
| phantom-deps | phantom-dep:@mapbox/point-geometry | AI (phantom-deps): Referenced in config files; stable FP for this bundled package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.28.12 | 6 / 1 | |
| 2.28.11 | 6 / 1 | |
| 2.28.10 | 6 / 1 | |
| 2.25.10 | 6 / 1 | |
| 2.25.9 | 6 / 1 | |
| 2.25.7 | 6 / 1 | |
| 2.25.6 | 6 / 1 | |
| 2.25.5 | 6 / 1 | |
| 2.25.4 | 6 / 1 | |
| 2.25.2 | 6 / 1 | |
| 2.25.1 | 6 / 1 | |
| 2.24.2 | 6 / 1 | |
| 2.24.1 | 6 / 1 | |
| 2.24.0 | 6 / 1 | |
| 2.23.2 | 6 / 1 | |
| 2.23.1 | 6 / 1 | |
| 2.23.0 | 6 / 1 | |
| 2.22.7 | 6 / 1 | |
| 2.22.6 | 6 / 1 |
v2.28.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.4
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.2
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.