@hypequery/cli
Command-line interface for hypequery
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@hypequery/deployment | AI (dependencies): First-party sibling package in the hypequery monorepo, same publisher/org. | ai | |
| provenance | missing-githead | AI (provenance): Metadata gap from publish env, no behavioral indicator; publisher has strong track record. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party sibling package in same monorepo/org. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @hypequery package; Levenshtein match to 'joi' is coincidental, not a typosquat. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.10.3 | 10 / 7 | |
| 1.10.2 | 10 / 7 | |
| 1.10.1 | 10 / 7 | |
| 1.10.0 | 10 / 7 | |
| 1.9.5 | 10 / 7 | |
| 1.9.4 | 10 / 7 | |
| 1.9.3 | 10 / 7 | |
| 1.9.2 | 10 / 7 | |
| 1.9.1 | 10 / 7 | |
| 1.9.0 | 9 / 7 | |
| 1.8.0 | 9 / 7 | |
| 1.7.0 | 9 / 7 | |
| 1.6.0 | 9 / 7 | |
| 1.5.0 | 9 / 7 | |
| 1.4.0 | 8 / 7 | |
| 1.3.1 | 8 / 7 | |
| 1.3.0 | 8 / 7 | |
| 1.2.1 | 8 / 7 | |
| 1.2.0 | 8 / 7 | |
| 1.1.2 | 8 / 8 | |
| 1.1.1 | 8 / 7 | |
| 1.1.0 | 8 / 7 | |
| 1.0.0 | 8 / 7 | |
| 0.0.9 | 8 / 7 | |
| 0.0.8 | 8 / 7 | |
| 0.0.7 | 8 / 7 | |
| 0.0.6 | 8 / 7 | |
| 0.0.5 | 8 / 7 | |
| 0.0.4 | 8 / 7 | |
| 0.0.3 | 8 / 7 | |
| 0.0.2 | 8 / 7 | |
| 0.0.1 | 5 / 8 |
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lureilly2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lureilly2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lureilly2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lureilly2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lureilly2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lureilly2.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lureilly2.
v0.0.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lureilly2.
v0.0.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lureilly2.
v0.0.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lureilly2.
v0.0.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lureilly2.