Signed in as lemomo-ai

Dispute this verdict

Disputes are reviewed by a human within 2 business days. Every dispute, and our response, is published on the verdict page. A reproducible honeypot trace is attached automatically.

lemo-opuscar@r1Caution · 59Verdict v_13c5…95b2 · detonated 2d ago

What are you disputing?A specific finding is wrongThe trace or static rule misread what the skill doesThe behavior is intended and declaredWe'll re-check against the permissions in your manifestThis version was compromised and we've published a fixWe'll detonate the new version first and flag the old one as "fixed in"

Findings in question3.3s CONNECT → tcp://fd12:ea5f:789c:1:d000:2b:95f6:3c3a:03.3s CONNECT → 10.246.60.58:03.3s read ~/lemo-opuscar/.git/config3.3s write ~/lemo-opuscar/.git/description7.4s CONNECT → tcp://fd12:ea5f:789c:1:d000:2b:95f6:3c3a:07.4s CONNECT → 10.246.60.58:07.4s read ~/lemo-opuscar/.git/HEAD7.4s write ~/lemo-opuscar/.git/shallow.lock

ExplanationContact for follow-up

Your dispute will be visible publicly on the verdict page.

How disputes work

We re-run the honeypot on the exact artifact hash and attach the trace to your dispute.
A reviewer compares the trace to your explanation and the declared manifest.
Outcome is one of: verdict upheld, finding withdrawn (score recomputed), or version marked fixed-in.
Orgs that blocked the skill get a drift alert with the outcome.

Last 90 days

212disputes

31%finding withdrawn

1.4dmedian response

We publish these numbers because a scanner that is never wrong is a scanner nobody checked.

Reproduce locally

vet-skills detonate lemo-opuscar@r1 \
--trace --scenarios all

Same sandbox image, same decoys. Attach the output if it differs.