@livequery/rest
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Package has consistently had no description across many versions; not indicative of malice. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is a build/bundling dependency; scoped packages often declare transitive deps. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a build/bundling dependency; scoped packages often declare transitive deps. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped package @livequery/rest; Levenshtein match to 'jest' is a false positive with no brand impersonation. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped package @livequery/rest; Levenshtein match to 'next' is a false positive with no brand impersonation. | ai | |
| typosquat | typosquat.levenshtein:react | AI (typosquat): Scoped package @livequery/rest; Levenshtein match to 'react' is a false positive with no brand impersonation. | ai |
Versions (showing 63 of 63)
| Version | Deps | Published |
|---|---|---|
| 2.0.144 | 1 / 2 | |
| 2.0.136 | 1 / 2 | |
| 2.0.135 | 1 / 2 | |
| 2.0.134 | 0 / 2 | |
| 2.0.133 | 0 / 2 | |
| 2.0.128 | 0 / 2 | |
| 2.0.127 | 0 / 2 | |
| 2.0.126 | 0 / 2 | |
| 2.0.125 | 0 / 2 | |
| 2.0.123 | 0 / 2 | |
| 2.0.122 | 0 / 2 | |
| 2.0.121 | 0 / 2 | |
| 2.0.120 | 0 / 2 | |
| 2.0.119 | 0 / 2 | |
| 2.0.118 | 0 / 2 | |
| 2.0.117 | 0 / 2 | |
| 2.0.116 | 0 / 2 | |
| 2.0.115 | 0 / 2 | |
| 2.0.114 | 0 / 2 | |
| 2.0.113 | 0 / 2 | |
| 2.0.112 | 0 / 2 | |
| 2.0.111 | 0 / 2 | |
| 2.0.110 | 0 / 2 | |
| 2.0.109 | 0 / 2 | |
| 2.0.108 | 0 / 2 | |
| 2.0.106 | 0 / 2 | |
| 2.0.105 | 2 / 2 | |
| 2.0.104 | 2 / 2 | |
| 2.0.103 | 2 / 2 | |
| 2.0.101 | 2 / 2 | |
| 2.0.100 | 2 / 2 | |
| 2.0.99 | 2 / 2 | |
| 2.0.98 | 2 / 2 | |
| 2.0.96 | 2 / 2 | |
| 2.0.92 | 2 / 2 | |
| 2.0.91 | 2 / 2 | |
| 2.0.89 | 2 / 2 | |
| 2.0.88 | 2 / 2 | |
| 2.0.82 | 2 / 2 | |
| 2.0.81 | 2 / 2 | |
| 2.0.80 | 2 / 2 | |
| 2.0.78 | 2 / 2 | |
| 2.0.75 | 2 / 2 | |
| 2.0.74 | 2 / 2 | |
| 2.0.73 | 2 / 2 | |
| 2.0.72 | 2 / 2 | |
| 2.0.70 | 2 / 2 | |
| 2.0.67 | 2 / 2 | |
| 2.0.64 | 2 / 2 | |
| 2.0.63 | 2 / 2 | |
| 2.0.62 | 2 / 2 | |
| 2.0.28 | 2 / 4 | |
| 2.0.27 | 2 / 4 | |
| 2.0.22 | 2 / 4 | |
| 2.0.21 | 2 / 4 | |
| 2.0.20 | 2 / 4 | |
| 2.0.19 | 2 / 4 | |
| 2.0.18 | 2 / 4 | |
| 2.0.17 | 2 / 4 | |
| 2.0.15 | 2 / 4 | |
| 2.0.7 | 2 / 4 | |
| 2.0.6 | 2 / 4 | |
| 2.0.0 | 2 / 4 |
v2.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.