← Home

@livequery/client

npm
46
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

duongvanba

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Established scoped package in active ecosystem; sparse metadata is a style choice, not spam indicator. ai
provenance no-provenance AI (provenance): Long-lived package predating provenance attestation; no CI/CD provenance is consistent with prior versions. ai
phantom-deps phantom-dep:uuidv7 AI (phantom-deps): uuidv7 is a declared runtime dependency; phantom-dep heuristic is a false positive here. ai

Versions (showing 46 of 46)

Version Deps Published
2.0.144 2 / 3
2.0.136 2 / 3
2.0.135 2 / 3
2.0.134 2 / 3
2.0.130 2 / 3
2.0.128 2 / 3
2.0.127 2 / 3
2.0.126 2 / 3
2.0.125 2 / 3
2.0.124 2 / 3
2.0.123 2 / 3
2.0.122 2 / 3
2.0.121 2 / 3
2.0.120 2 / 3
2.0.119 2 / 3
2.0.118 2 / 3
2.0.117 2 / 3
2.0.116 2 / 3
2.0.115 2 / 3
2.0.114 2 / 3
2.0.113 2 / 3
2.0.112 2 / 3
2.0.111 2 / 3
2.0.110 2 / 3
2.0.109 2 / 3
2.0.108 2 / 3
2.0.107 2 / 3
2.0.106 2 / 3
2.0.105 2 / 3
2.0.104 2 / 3
2.0.30 1 / 3
2.0.25 1 / 3
2.0.24 1 / 3
2.0.23 1 / 3
2.0.22 1 / 3
2.0.20 1 / 3
2.0.15 1 / 3
2.0.11 1 / 3
2.0.7 1 / 3
2.0.6 1 / 3
2.0.5 1 / 3
2.0.4 1 / 3
2.0.3 1 / 3
2.0.2 1 / 3
2.0.1 1 / 3
2.0.0 1 / 3

v2.0.30

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

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

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

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

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

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

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

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

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

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