← Home

@antv/l7-core

28
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

lviseiiaaronjinke.lilzxuearmy8735dengfupingafc163chenlulikn9117bbsqqbanxuanyanxiongatoolpearl_wangalex_zjtduxinyue023wang1212gaofuhong

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Established monorepo package; empty description is a consistent pattern across versions, not a malware indicator. ai
phantom-deps phantom-dep:viewport-mercator-project AI (phantom-deps): Declared as a dependency and devDependency for types; used in config/type context, not a malicious phantom dep. ai
provenance no-provenance AI (provenance): Consistent across all versions of this monorepo package; not a risk indicator for this publisher. ai

Versions (showing 28 of 28)

Version Deps Published
2.29.1 9 / 3
2.29.0 9 / 3
2.28.14 9 / 3
2.28.13 9 / 3
2.28.12 9 / 3
2.28.11 9 / 3
2.28.10 9 / 3
2.25.10 9 / 3
2.25.9 9 / 3
2.25.7 9 / 3
2.25.6 9 / 3
2.25.5 9 / 3
2.25.4 9 / 3
2.25.3 9 / 3
2.25.2 9 / 3
2.25.1 8 / 3
2.25.0 8 / 3
2.24.1 8 / 3
2.24.0 8 / 3
2.23.0 11 / 4
2.22.7 11 / 4
2.22.6 11 / 4
2.22.5 11 / 4
2.22.4 11 / 4
2.22.3 11 / 4
2.22.2 11 / 4
2.22.1 11 / 4
2.22.0 11 / 4

v2.29.1

1 finding
INFO No provenance attestation provenance

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

v2.29.0

1 finding
INFO No provenance attestation provenance

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

v2.22.5

1 finding
INFO No provenance attestation provenance

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

v2.22.4

1 finding
INFO No provenance attestation provenance

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

v2.22.3

1 finding
INFO No provenance attestation provenance

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

v2.22.2

1 finding
INFO No provenance attestation provenance

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

v2.22.1

1 finding
INFO No provenance attestation provenance

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

v2.22.0

1 finding
INFO No provenance attestation provenance

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