@apimatic/http-query
This package provides utilities for encoding and formatting URL query parameters.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): APIMatic monorepo package; no provenance is consistent across all their published packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.3.9 | 3 / 13 | |
| 0.3.8 | 2 / 13 | |
| 0.3.7 | 2 / 13 | |
| 0.3.6 | 2 / 13 | |
| 0.3.5 | 2 / 13 | |
| 0.3.4 | 2 / 13 | |
| 0.3.3 | 2 / 13 | |
| 0.3.2 | 2 / 13 | |
| 0.3.1 | 2 / 13 | |
| 0.3.0 | 2 / 13 | |
| 0.2.0 | 2 / 16 | |
| 0.1.0 | 2 / 16 |
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.