arri
Command line interface for ARRI-RPC
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@joshmossas/listhen | AI (dependencies): Same author as the package; consistent use across versions. | ai | |
| dependencies | unvetted-dep:esbuild-plugin-replace | AI (dependencies): Well-known esbuild utility plugin; stable dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): Package has 230 published versions without provenance; consistent pattern, not a new anomaly. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.82.0 | 21 / 1 | |
| 0.81.4 | 21 / 1 | |
| 0.81.3 | 21 / 1 | |
| 0.81.2 | 21 / 1 | |
| 0.81.1 | 21 / 1 | |
| 0.81.0 | 21 / 1 | |
| 0.80.3 | 21 / 1 | |
| 0.80.2 | 21 / 1 | |
| 0.80.1 | 21 / 1 | |
| 0.80.0 | 21 / 1 | |
| 0.79.1 | 21 / 1 |
v0.82.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.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.81.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.1
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.81.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.80.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.1
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.80.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.79.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.