← Home

@vaultfire/a2a

npm Repository Homepage

Bridge Google's A2A (Agent-to-Agent) protocol with Vaultfire Protocol's on-chain trust

3
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

ghostkey316

Keywords

a2aagent-to-agentvaultfireblockchaintrustweb3ai-agentgoogle-a2abaseon-chain

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped package @vaultfire/a2a; 'a2a' suffix match to 'koa' is coincidental, not a typosquat. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped package @vaultfire/a2a; 'a2a' suffix match to 'ajv' is coincidental, not a typosquat. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.2 2 / 7
1.0.1 2 / 7
1.0.0 2 / 7

v1.0.2

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.

v1.0.1

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.

v1.0.0

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.