@arrirpc/server
Typescript implementation of [Arri RPC](/README.md). It's built on top of [H3](https://github.com/unjs/h3) and uses [esbuild](https://esbuild.github.io/) for bundling.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped package @arrirpc/server is part of the arri RPC framework; Levenshtein match to 'semver' is coincidental. | ai | |
| phantom-deps | phantom-dep:arri | AI (phantom-deps): arri is the parent framework package; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:crossws | AI (phantom-deps): WebSocket adapter loaded by framework convention, not direct import. | ai | |
| phantom-deps | phantom-dep:uncrypto | AI (phantom-deps): Crypto utility loaded by framework convention, not direct import. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): Source map support loaded by convention at runtime, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/source-map-support | AI (phantom-deps): Type-only package; framework-scoped, loaded by convention. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.82.0 | 9 / 1 | |
| 0.81.4 | 9 / 1 | |
| 0.81.3 | 9 / 1 | |
| 0.81.2 | 9 / 1 | |
| 0.81.1 | 9 / 1 | |
| 0.81.0 | 9 / 1 | |
| 0.80.3 | 9 / 1 | |
| 0.80.2 | 9 / 1 | |
| 0.80.1 | 9 / 1 | |
| 0.80.0 | 9 / 1 | |
| 0.79.1 | 9 / 1 |
v0.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.4
2 findingsPackage name '@arrirpc/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.80.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.