← Home

@kybernesis/arp

npm Repository Homepage

ARP CLI (`arpc`) — one command to connect local agents (KyberBot, OpenClaw, Hermes, etc.) to ARP Cloud. Auto-detects each framework + handoff. Includes a daemon supervisor for running many agents in one background process.

22
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kybernesis

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Likely CI/CD environment change; no other risk signals present and publisher has clean track record. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped package @kybernesis/arp is an ARP CLI tool, not a typosquat of yup; name similarity is coincidental. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped package @kybernesis/arp is an ARP CLI tool, not a typosquat of ajv; name similarity is coincidental. ai

Versions (showing 22 of 22)

Version Deps Published
0.10.4 3 / 5
0.10.3 3 / 5
0.10.2 3 / 5
0.10.1 3 / 5
0.10.0 2 / 5
0.9.9 2 / 5
0.9.8 2 / 5
0.9.7 2 / 5
0.9.6 2 / 5
0.9.5 2 / 5
0.9.4 2 / 5
0.9.3 2 / 5
0.9.2 2 / 5
0.9.1 2 / 5
0.9.0 2 / 5
0.8.0 2 / 5
0.6.1 2 / 5
0.6.0 2 / 5
0.5.0 2 / 5
0.4.0 2 / 5
0.3.0 2 / 5
0.2.0 1 / 4

v0.10.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.2

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kybernesis.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kybernesis.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.9

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kybernesis.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.