@antv/l7-source No license 22 versions

@antv/l7-source

npm Repository Homepage

22

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

lviseiiaaronjinke.lilzxuearmy8735dengfupingafc163chenlulikn9117bbsqqbanxuanyanxiongatoolalex_zjtduxinyue023wang1212gaofuhong

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): yanxiong is an established AntV org publisher with 164 approved packages; transition within same org is expected.	ai	2026/05/31
npm-metadata	no-description	AI (npm-metadata): AntV L7 monorepo packages consistently have empty descriptions; not a malware indicator here.	ai	2026/05/30
phantom-deps	phantom-dep:@antv/async-hook	AI (phantom-deps): Same-org package; phantom-dep heuristic is a stable false positive for this package.	ai	2026/05/20
phantom-deps	phantom-dep:pbf	AI (phantom-deps): Geo/tile processing dep; likely used in compiled output. Stable false positive.	ai	2026/05/20
phantom-deps	phantom-dep:@turf/meta	AI (phantom-deps): Turf.js geo utility; used in compiled output. Stable false positive.	ai	2026/05/20
phantom-deps	phantom-dep:geojson-vt	AI (phantom-deps): Tile processing dep; used in compiled output. Stable false positive.	ai	2026/05/20
phantom-deps	phantom-dep:supercluster	AI (phantom-deps): Clustering dep; used in compiled output. Stable false positive.	ai	2026/05/20
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	2026/05/20
phantom-deps	phantom-dep:eventemitter3	AI (phantom-deps): Event emitter dep; used in compiled output. Stable false positive.	ai	2026/05/20
phantom-deps	phantom-dep:@babel/runtime	AI (phantom-deps): Framework-scoped Babel runtime; loaded by convention in compiled output.	ai	2026/05/20
phantom-deps	phantom-dep:@turf/invariant	AI (phantom-deps): Turf.js geo utility; used in compiled output. Stable false positive.	ai	2026/05/20
phantom-deps	phantom-dep:@mapbox/vector-tile	AI (phantom-deps): Mapbox tile dep; used in compiled output. Stable false positive.	ai	2026/05/20
phantom-deps	phantom-dep:@mapbox/geojson-rewind	AI (phantom-deps): Mapbox geo dep; used in compiled output. Stable false positive.	ai	2026/05/20
phantom-deps	phantom-dep:@turf/helpers	AI (phantom-deps): Turf.js geo utility; used in compiled output. Stable false positive.	ai	2026/05/20
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	2026/05/20

Versions (showing 22 of 22)

Version	Deps	Published
2.28.12	13 / 4	2026-05-31
2.28.11	13 / 4	2026-05-28
2.28.10	13 / 4	2026-05-21
2.25.10	13 / 4	2026-05-11
2.25.9	13 / 4	2026-05-11
2.25.7	13 / 4	2026-05-11
2.25.6	13 / 4	2026-05-11
2.25.5	13 / 4	2026-05-11
2.25.4	13 / 4	2026-03-24
2.25.3	13 / 4	2026-03-24
2.25.2	13 / 4	2026-03-13
2.25.1	13 / 4	2026-03-12
2.25.0	13 / 4	2026-03-12
2.24.3	13 / 4	2026-03-11
2.24.2	13 / 4	2026-03-11
2.24.1	13 / 4	2026-03-10
2.24.0	13 / 4	2026-03-10
2.23.2	15 / 6	2026-01-22
2.23.1	15 / 6	2025-11-14
2.23.0	15 / 6	2025-07-10
2.22.7	15 / 6	2025-07-03
2.22.6	15 / 6	2025-07-03

v2.28.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.28.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.28.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.25.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.25.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.25.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.25.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.25.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.25.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.25.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.25.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.25.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.24.3

2 findings

HIGH Publisher changed: lzxue → yanxiong (on 2026-03-11) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.24.2

2 findings

HIGH Publisher changed: lzxue → yanxiong (on 2026-03-11) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.24.1

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.