Is Remediation safe and trustworthy?

tashan scores Remediation on public evidence — it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Remediation?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Remediation?

3 GitHub contributors, source: DryRunSecurity/external-plugin-marketplace.

‹ The Index

Remediation

skill

- Helps fix security vulnerabilities identified by DryRunSecurity. Activates when the user shares a DryRunSecurity comment (from a GitHub PR or GitLab MR) or asks for help fixing any security finding including SQL injection, XSS, CSRF, SSRF, path traversal, command injection, authentication bypass, authorization flaws, and prompt injection. Researches authoritative sources and applies fixes grounded in the user's specific codebase context.

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Category: Security — see all ranked ›

Install (Claude Code):

cp -r remediation ~/.claude/skills/

Adoption: 1 repos
Upkeep: 97.0
Freshness: 94.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 3

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

source ↗ · skill:DryRunSecurity/remediation

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-09 · scorer s5 · how · something wrong here?