mizcausevic-dev/agent-card-diff

A2Acommunity
mizcausevic-devAGPL-3.0Updated 21d agoGitHub

Diff two A2A AgentCard documents — classify changes (autonomy escalation, memory escalation, tool/model removal, incident-response URI removal, etc.), surface a breaking flag. The agent-cards counterpart to mcp-tools-diff. Library + CLI.

Diff two A2A Agent Card documents and classify the changes. The agent-cards counterpart to . Status: v0.1.0 — Node 20/22 supported, library + CLI. Agent cards declare an agent's autonomy level, memory persistence, models, tools, refusal taxonomy, evaluations, and incident-response posture. Many of those are load-bearing for procurement and security review. When the card changes between two…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
21d agoLast update
Package
Authormizcausevic-dev
LicenseAGPL-3.0
Sourcegithub
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/25
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/10
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
CVE scan · not run+0/30
Not yet scanned — package must be on npm
Static analysis · clean+20/20
npm provenance (Sigstore)+0/5
Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
DependenciesNot audited
Tool surface
Security scan✓ CleanvHEAD · 19d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Diff two A2A Agent Card documents and classify the changes. The agent-cards counterpart to . Status: v0.1.0 — Node 20/22 supported, library + CLI. Agent cards declare an agent's autonomy level, memory persistence, models, tools, refusal taxonomy, evaluations, and incident-response posture. Many of those are load-bearing for procurement and security review. When the card changes between two versions, which changes break the trust assumptions downstream operators already approved? This library…

Keywords
a2aagent-cardsagent-to-agentai-governancebreaking-changediffgovernancetypescript