@hypequery/serve
Declarative HTTP server for exposing hypequery analytics endpoints
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/protocol | AI (dependencies): First-party sibling package under same @hypequery org/monorepo. | ai | |
| provenance | missing-githead | AI (provenance): No behavior change vs prior version; metadata-only regression. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): jose and first-party @hypequery/datasets are legitimate, non-hostile additions. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Consistent with feature/test expansion, no injected-code evidence. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dep likely used in bundled dist output; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): zod-to-json-schema is a declared runtime dep likely used in bundled dist output; phantom-dep false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped package @hypequery/serve is an HTTP server; name similarity to semver is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:openapi-typescript | AI (phantom-deps): openapi-typescript is a declared runtime dep used in build/type generation; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.14.0 | 6 / 5 | |
| 0.13.7 | 6 / 5 | |
| 0.13.6 | 6 / 5 | |
| 0.13.5 | 6 / 5 | |
| 0.13.4 | 6 / 5 | |
| 0.13.3 | 6 / 5 | |
| 0.13.2 | 6 / 5 | |
| 0.13.1 | 6 / 5 | |
| 0.13.0 | 6 / 5 | |
| 0.12.0 | 6 / 5 | |
| 0.11.0 | 6 / 5 | |
| 0.10.0 | 5 / 5 | |
| 0.9.2 | 5 / 5 | |
| 0.9.1 | 5 / 5 | |
| 0.9.0 | 5 / 5 | |
| 0.8.1 | 5 / 5 | |
| 0.8.0 | 5 / 5 | |
| 0.7.0 | 5 / 5 | |
| 0.6.1 | 5 / 5 | |
| 0.6.0 | 5 / 5 | |
| 0.5.0 | 5 / 5 | |
| 0.4.0 | 5 / 5 | |
| 0.3.0 | 5 / 5 | |
| 0.2.1 | 3 / 5 | |
| 0.2.0 | 3 / 5 | |
| 0.1.1 | 3 / 5 | |
| 0.1.0 | 3 / 5 | |
| 0.0.9 | 3 / 5 | |
| 0.0.8 | 3 / 5 | |
| 0.0.5 | 3 / 5 | |
| 0.0.2 | 3 / 5 | |
| 0.0.1 | 3 / 5 |
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.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.
v0.6.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.
v0.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.
v0.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.
v0.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.
v0.1.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.
v0.1.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.
v0.0.9
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.
v0.0.8
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.