@arrirpc/codegen-rust
```ts // arri.config.ts import { defineConfig, generators } from '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
Versions (showing 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 0.83.0 | 2 / 0 | |
| 0.82.0 | 2 / 0 | |
| 0.81.4 | 2 / 0 | |
| 0.81.3 | 2 / 0 | |
| 0.81.2 | 2 / 0 | |
| 0.81.1 | 2 / 0 | |
| 0.81.0 | 2 / 0 | |
| 0.80.3 | 2 / 0 | |
| 0.80.2 | 2 / 0 | |
| 0.80.1 | 2 / 0 | |
| 0.80.0 | 2 / 0 | |
| 0.79.1 | 2 / 0 | |
| 0.79.0 | 2 / 0 | |
| 0.78.0 | 2 / 0 | |
| 0.77.1 | 2 / 0 | |
| 0.77.0 | 2 / 0 | |
| 0.76.4 | 2 / 0 | |
| 0.76.3 | 2 / 0 | |
| 0.76.0 | 2 / 0 | |
| 0.75.2 | 2 / 0 | |
| 0.75.1 | 2 / 0 | |
| 0.75.0 | 2 / 0 | |
| 0.74.1 | 2 / 0 | |
| 0.74.0 | 2 / 0 | |
| 0.73.0 | 2 / 0 | |
| 0.72.0 | 2 / 0 | |
| 0.71.1 | 2 / 0 | |
| 0.71.0 | 2 / 0 | |
| 0.70.1 | 2 / 0 | |
| 0.69.2 | 2 / 0 | |
| 0.69.1 | 2 / 0 | |
| 0.69.0 | 2 / 0 | |
| 0.68.0 | 2 / 0 | |
| 0.67.0 | 2 / 0 | |
| 0.66.0 | 2 / 0 | |
| 0.65.2 | 2 / 0 | |
| 0.65.1 | 2 / 0 | |
| 0.65.0 | 2 / 0 | |
| 0.64.0 | 2 / 0 | |
| 0.63.3 | 2 / 0 | |
| 0.63.2 | 2 / 0 | |
| 0.63.1 | 2 / 0 | |
| 0.63.0 | 2 / 0 | |
| 0.62.0 | 2 / 0 | |
| 0.61.1 | 2 / 0 | |
| 0.61.0 | 2 / 0 | |
| 0.60.3 | 2 / 0 | |
| 0.60.2 | 2 / 0 | |
| 0.60.1 | 2 / 1 | |
| 0.60.0 | 2 / 1 | |
| 0.59.0 | 2 / 1 | |
| 0.58.1 | 2 / 1 | |
| 0.58.0 | 2 / 1 | |
| 0.57.8 | 2 / 1 | |
| 0.57.6 | 2 / 1 | |
| 0.57.5 | 2 / 1 | |
| 0.57.4 | 2 / 1 | |
| 0.57.3 | 2 / 1 | |
| 0.57.2 | 2 / 1 | |
| 0.57.0 | 2 / 1 | |
| 0.55.0 | 2 / 1 | |
| 0.54.0 | 2 / 1 | |
| 0.53.2 | 2 / 1 | |
| 0.53.1 | 2 / 1 | |
| 0.53.0 | 2 / 1 | |
| 0.52.0 | 2 / 1 |
v0.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.77.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.