pyunto-agent@0.3.0
VERIFIED· not startedPublisher claims: "Make an external agent (Claude, Claude Code, any CLI/HTTP agent) the partner of a Pyunto exchange diary" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
ANTHROPIC_API_KEYPYUNTO_AGENT_SECRETPYUNTO_PASSWORDConfiguration, not credentials: PYUNTO_AGENT_DIR, PYUNTO_AGENT_LISTEN, PYUNTO_AGENT_NAME, PYUNTO_BACKEND, PYUNTO_BACKEND_URL, PYUNTO_BASE_URL, PYUNTO_COMMAND, PYUNTO_EMAIL, PYUNTO_HISTORY, PYUNTO_MODEL, PYUNTO_PERSONA- Where it talks to
- no vendor host named in the codeAlso pyunto.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names pyunto.com as well as its own vendor. The guard injects ANTHROPIC_API_KEY, PYUNTO_AGENT_SECRET, PYUNTO_PASSWORD only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 85/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.except Exception: # noqa: BLE001 - a handler crash must not kill the listenerFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.duration = float(subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Configuration (env or .env in the working directory; PYUNTO_AGENT_DIR defaults toFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.subprocess.run([ffmpeg, "-v", "error", "-y", "-ss", f"{at:.2f}", "-i", str(path),Fix: 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. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for pyunto-agent@0.3.0 as of 17 h ago. This is the package itself, not its dependencies.