@arrirpc/client
This library is needed to use the typescript code generated by [ARRI-RPC](https://github.com/modiimedia/arri)
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:@joshmossas/ofetch | AI (dependencies): Same-maintainer fork of ofetch, consistent with package author identity. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; no provenance is a process gap, not a security signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped package in a monorepo; sparse README and no keywords are typical for internal/scoped packages. | ai |
Versions (showing 51 of 85)
| Version | Deps | Published |
|---|---|---|
| 0.83.0 | 3 / 0 | |
| 0.82.0 | 3 / 0 | |
| 0.81.4 | 3 / 0 | |
| 0.81.3 | 3 / 0 | |
| 0.81.2 | 3 / 0 | |
| 0.81.1 | 3 / 0 | |
| 0.81.0 | 3 / 0 | |
| 0.80.3 | 4 / 1 | |
| 0.80.2 | 4 / 1 | |
| 0.80.1 | 4 / 1 | |
| 0.80.0 | 4 / 1 | |
| 0.79.1 | 4 / 1 | |
| 0.79.0 | 4 / 1 | |
| 0.78.0 | 4 / 1 | |
| 0.77.1 | 4 / 1 | |
| 0.77.0 | 4 / 1 | |
| 0.76.4 | 4 / 1 | |
| 0.76.3 | 4 / 1 | |
| 0.76.0 | 4 / 1 | |
| 0.75.2 | 4 / 1 | |
| 0.75.1 | 4 / 1 | |
| 0.75.0 | 4 / 1 | |
| 0.74.1 | 4 / 1 | |
| 0.74.0 | 4 / 1 | |
| 0.73.0 | 4 / 1 | |
| 0.72.0 | 4 / 1 | |
| 0.71.1 | 4 / 1 | |
| 0.71.0 | 4 / 1 | |
| 0.70.1 | 4 / 1 | |
| 0.69.2 | 4 / 1 | |
| 0.69.1 | 4 / 1 | |
| 0.69.0 | 4 / 1 | |
| 0.68.0 | 4 / 1 | |
| 0.67.0 | 4 / 1 | |
| 0.66.0 | 4 / 1 | |
| 0.65.2 | 4 / 1 | |
| 0.65.1 | 4 / 1 | |
| 0.65.0 | 4 / 1 | |
| 0.64.0 | 4 / 1 | |
| 0.63.3 | 4 / 1 | |
| 0.63.2 | 4 / 1 | |
| 0.63.1 | 4 / 1 | |
| 0.63.0 | 4 / 1 | |
| 0.62.0 | 4 / 1 | |
| 0.61.1 | 4 / 1 | |
| 0.61.0 | 4 / 1 | |
| 0.60.3 | 4 / 1 | |
| 0.60.2 | 4 / 1 | |
| 0.60.1 | 4 / 1 | |
| 0.60.0 | 4 / 1 | |
| 0.59.0 | 4 / 1 |
v0.83.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.1
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.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.3
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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.74.1
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.73.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.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.70.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.