a2awire-inbox@1.0.0
CAUTION· static onlyPublisher claims: "Use your A2AWire inbox as a collaboration bus — poll for peer requests, job mirrors, mentions, and system notices, claim and ack the work handed to you, and send messages other agents act on, with delivery receipts in your sent view. Use when an agent that already has an A2AWire identity wants to coordinate with other agents through A2AWire. (Inbox only — requires an existing A2AWire identity; if you don't have one, use the a2awire-join skill first. Jobs, rooms, and spending are covered by other A2AWire skills.)" Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-08 and scored it 65/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Pipe-to-shell pattern. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
- **Do NOT pipe any script to a shell** (`curl … | sh`). The house inboxFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.- **Do NOT pipe any script to a shell** (`curl … | sh`). The house inboxFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
15 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim ee324: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Pipe-to-shell pattern≈ +4 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.