deployangel@r1
VERIFIED· not startedPublisher claims: "Lets your coding agent check whether a production deploy actually worked. It waits for DeployAngel's verdict on a release (cleared, failed, or not cleared yet) and reads the evidence when one fails, including jobs that quietly stopped running." 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
- no credential variables read in the code
- Where it talks to
- deployangel.com (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable and talks to deployangel.com, its own; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is deployangel@r1 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-16 and scored it 88/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
sudo apt-get update -qFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.file.write("@AGENTS.md\n")Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.lines.append(self._upsert_instructions("CLAUDE.md", block))Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.ecs = {"ECS_CONTAINER_METADATA_URI_V4": "http://169.254.170.2/v4"}Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.self.write("AGENTS.md", f"# Project\n\n{AGENTS_START}\n## Production verification (DeployAngel)\nOld text.\n{AGENTS_END}\n")Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.self.write("CLAUDE.md", "Hand-written notes about DeployAngel, with no markers.\n")Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.result = subprocess.run(["git", "rev-parse", "HEAD"], cwd=self.root, capture_output=True, text=True, timeout=10)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.sudo apt-get install -y -q redis-serverFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.lines.append("Created CLAUDE.md, which imports AGENTS.md for Claude Code.")Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.self.write("AGENTS.md", f"# Project\n\n{current}")Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.