🔎 Evidence browser

Search the skill radar

Search by skill, publisher, category, or trust summary — then use the runtime filters to find cards with live test evidence. The two main lanes are baseline safety checks first and deeper follow-on functionality checks after that.

⚙️ Filters · 3 active
✨ Quick picks
🏷 Categories · catalog-only

🧾 Evidence level: source-scanned means local source evidence; catalog-only means thinner metadata-first coverage.

🧪 Runtime status: cards can show only the baseline safety lane or the deeper follow-on functionality lane, depending on how far the skill got.

📏 Depth cue: tells you whether the evidence stops at baseline checks, includes follow-on functionality checks, or includes richer fixture/example proof.

⏱ Freshness cue: tells you whether the latest runtime evidence is from the last 24 hours, the last 7 days, or is older and therefore less current.

🩺 Failure confidence: distinguishes a first seen failure from a repeated failure or a regression after an earlier pass, so not every red row means the same thing.

Results

Showing 3 of 3 results for “github · runtime: failed · category: catalog-only · sort: relevance
This snapshot is for the current page of results, not the whole filtered universe.
Browse hint: slices with zero failures plus some source-scanned or reviewed entries deserve more attention first; fresh runtime evidence helps too, because old clean receipts can still hide current drift.

deai-image

swaylq · vsource-scanned
49
overall

Detect and remove AI fingerprints from AI-generated images. Strip metadata, add film grain, recompress, and bypass AI image detectors. Works with Midjourney, DALL-E, Stable Diffusion, Flux output.

High Riskfollow-on functionality checks failed · 9/10confidence: source evidence
+ 2 more
source-scannedsuspicious
Runtime receipts + what failed2026-03-15 15:00 UTC
functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hoursfirst failed run seen for this lanepassed, runtime_failedoutput 171 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 3499 msbaseline-v3 8/8
🕵️ expected proof signal was missing🚫 skill exited with an error
RatioDaemon muttered: deai-image made it to runtime and then fell apart on contact.9/10 functionality-v2 checks passed before the stumble. The python help is the part that made this interesting.
Observed: skill-structure-ok
Take: Potentially suspicious implementation signals detected: rm -rf, sudo .
Decision cue: Review first — functionality-v2 already found trouble.

odoo-connector

nullnaveen · vsource-scanned
61
overall

repository: https://github.com/NullNaveen/openclaw-odoo-skill

High Riskfollow-on functionality checks failed · 8/9confidence: source evidence
+ 2 more
source-scannedsuspicious
Runtime receipts + what failed2026-03-16 11:45 UTC
functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hoursfirst failed run seen for this lanepassed, expectation_failedoutput 154 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 3049 msbaseline-v3 8/8
🕵️ expected proof signal was missing
RatioDaemon muttered: The runtime lane gave odoo-connector a chance to act normal. It declined and talked a big game, then missed its own proof signal.8/9 functionality-v2 checks passed before the stumble. The requirements txt shape is the part that made this interesting.
Observed: skill-structure-ok
Take: Potentially suspicious implementation signals detected: password.
Decision cue: Review first — functionality-v2 already found trouble.

odoo-erp-connector

nullnaveen · vsource-scanned
61
overall

repository: https://github.com/NullNaveen/openclaw-odoo-skill

High Riskfollow-on functionality checks failed · 8/9confidence: source evidence
+ 2 more
source-scannedsuspicious
Runtime receipts + what failed2026-03-16 08:30 UTC
functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hoursfirst failed run seen for this lanepassed, expectation_failedoutput 154 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 3073 msbaseline-v3 8/8
🕵️ expected proof signal was missing
RatioDaemon muttered: The runtime lane gave odoo-erp-connector a chance to act normal. It declined and talked a big game, then missed its own proof signal.8/9 functionality-v2 checks passed before the stumble. The requirements txt shape is the part that made this interesting.
Observed: skill-structure-ok
Take: Potentially suspicious implementation signals detected: password.
Decision cue: Review first — functionality-v2 already found trouble.