@harnessio/react-har-service-client
Harness HAR Service APIs integrated with react hooks
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:@harnessio/oats-plugin-react-query-harness | AI (dependencies): Same-org codegen plugin from trusted Harness publisher. | ai | |
| phantom-deps | phantom-dep:@harnessio/oats-plugin-react-query-harness | AI (phantom-deps): Codegen plugin used at build time, not directly imported. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher is a known Harness org contributor with 9 approved packages; repo matches official Harness GitHub org. | ai | |
| provenance | no-provenance | AI (provenance): Harness org package with consistent publish history; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@harnessio/oats-cli | AI (phantom-deps): Same-org codegen tool invoked via build script, not imported at runtime; stable false positive for this package. | ai |
Versions (showing 100 of 105)
| Version | Deps | Published |
|---|---|---|
| 0.83.0 | 2 / 0 | |
| 0.82.0 | 2 / 0 | |
| 0.81.0 | 2 / 0 | |
| 0.80.0 | 2 / 0 | |
| 0.79.0 | 2 / 0 | |
| 0.78.0 | 2 / 0 | |
| 0.77.0 | 1 / 0 | |
| 0.76.0 | 1 / 0 | |
| 0.75.0 | 1 / 0 | |
| 0.74.0 | 1 / 0 | |
| 0.73.0 | 1 / 0 | |
| 0.72.0 | 1 / 0 | |
| 0.71.0 | 1 / 0 | |
| 0.70.0 | 1 / 0 | |
| 0.69.0 | 1 / 0 | |
| 0.68.0 | 1 / 0 | |
| 0.67.0 | 1 / 0 | |
| 0.66.0 | 1 / 0 | |
| 0.65.0 | 1 / 0 | |
| 0.64.0 | 1 / 0 | |
| 0.63.0 | 1 / 0 | |
| 0.62.0 | 1 / 0 | |
| 0.61.0 | 1 / 0 | |
| 0.60.0 | 1 / 0 | |
| 0.59.0 | 1 / 0 | |
| 0.58.0 | 1 / 0 | |
| 0.57.0 | 1 / 0 | |
| 0.56.0 | 1 / 0 | |
| 0.55.0 | 1 / 0 | |
| 0.54.0 | 1 / 0 | |
| 0.53.0 | 1 / 0 | |
| 0.52.0 | 1 / 0 | |
| 0.51.0 | 1 / 0 | |
| 0.50.0 | 1 / 0 | |
| 0.49.0 | 1 / 0 | |
| 0.48.0 | 1 / 0 | |
| 0.47.0 | 1 / 0 | |
| 0.46.0 | 1 / 0 | |
| 0.45.0 | 1 / 0 | |
| 0.44.0 | 1 / 0 | |
| 0.43.0 | 1 / 0 | |
| 0.42.0 | 1 / 0 | |
| 0.41.0 | 1 / 0 | |
| 0.40.0 | 1 / 0 | |
| 0.39.0 | 1 / 0 | |
| 0.38.0 | 1 / 0 | |
| 0.37.0 | 1 / 0 | |
| 0.36.0 | 1 / 0 | |
| 0.35.0 | 1 / 0 | |
| 0.34.0 | 1 / 0 | |
| 0.33.0 | 1 / 0 | |
| 0.32.0 | 1 / 0 | |
| 0.31.0 | 1 / 0 | |
| 0.30.0 | 1 / 0 | |
| 0.29.0 | 1 / 0 | |
| 0.28.0 | 1 / 0 | |
| 0.27.0 | 1 / 0 | |
| 0.26.0 | 1 / 0 | |
| 0.25.0 | 1 / 0 | |
| 0.24.0 | 1 / 0 | |
| 0.23.0 | 1 / 0 | |
| 0.22.0 | 1 / 0 | |
| 0.21.0 | 1 / 0 | |
| 0.20.0 | 1 / 0 | |
| 0.19.0 | 1 / 0 | |
| 0.18.0 | 1 / 0 | |
| 0.17.0 | 1 / 0 | |
| 0.16.0 | 1 / 0 | |
| 0.15.0 | 1 / 0 | |
| 0.14.0 | 1 / 0 | |
| 0.13.0 | 1 / 0 | |
| 0.12.0 | 1 / 0 | |
| 0.11.0 | 1 / 0 | |
| 0.10.0 | 1 / 0 | |
| 0.9.0 | 1 / 0 | |
| 0.8.0 | 1 / 0 | |
| 0.7.0 | 1 / 0 | |
| 0.6.0 | 1 / 0 | |
| 0.5.0 | 1 / 0 | |
| 0.4.0 | 1 / 0 | |
| 0.3.0 | 1 / 0 | |
| 0.2.0 | 1 / 0 | |
| 0.1.0 | 0 / 0 | |
| 0.0.25 | 0 / 0 | |
| 0.0.24 | 0 / 0 | |
| 0.0.23 | 0 / 0 | |
| 0.0.22 | 0 / 0 | |
| 0.0.21 | 0 / 0 | |
| 0.0.20 | 0 / 0 | |
| 0.0.19 | 0 / 0 | |
| 0.0.18 | 0 / 0 | |
| 0.0.17 | 0 / 0 | |
| 0.0.16 | 0 / 0 | |
| 0.0.15 | 0 / 0 | |
| 0.0.14 | 0 / 0 | |
| 0.0.13 | 0 / 0 | |
| 0.0.12 | 0 / 0 | |
| 0.0.11 | 0 / 0 | |
| 0.0.10 | 0 / 0 | |
| 0.0.9 | 0 / 0 |
v0.83.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.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.17.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.16.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.15.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.14.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.13.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.12.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.11.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.10.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.9.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.8.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.7.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.6.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.5.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.4.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.3.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.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.
v0.0.25
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.0.24
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.0.23
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.0.22
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.0.21
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.0.20
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.0.19
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.0.18
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.0.17
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.0.16
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.0.15
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.0.14
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.0.13
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.0.12
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.0.11
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.0.10
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.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.