antemortem-cli@0.12.5
CAUTION· not startedPublisher claims: "Local code-citation checks, source-evidence grounding, and fail-closed review tools for AI coding agents." 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: Caution 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
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try antemortem-cli` runs it now and prints the full answer.
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-07 and scored it 72/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: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
list ``.env`` in the Recon protocol and it would get sent to the LLM.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.ship `.env`, credential fixtures, or customer dumps to an external LLMFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Takes a ``<doc>.json`` audit artifact (the output of ``antemortem run``)Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.commit = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# called ``read_text()`` directly, which let an agent ship ``.env``Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."**/.env.*",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose..env file was excluded by deny-glob (good) or never even triedFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."or GOOGLE_API_KEY, or pass api_key explicitly."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.status = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."**/.env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.".env.*",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.contract as ``antemortem run`` — deny-globs for .env / credentials /Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.doc.with_suffix(".json").write_text(output.model_dump_json(), encoding="utf-8")Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.pattern are skipped with a warning. Default covers .env,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.> **Purpose: kill the false positives before they make it to the spec.**Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."PEM keys). The default deny-list covers .env, .ssh, *.pem, "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- You want the Skeptic pass to kill false positivesFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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.
What would make this Verified
8 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim hibou04-ops: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Credential pass-through configuration≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.