Answer page · updated 2026-10-19
Is skill-security-auditor-lawve safe to install?
The Forge's scanner matched 2 high-risk patterns in skill-security-auditor-lawve (lawve-ai/awesome-legal-skills) (version 045f738, scanned 2026-10-19): it sends data to a throwaway collection endpoint. A match is a reason to read those lines, not a verdict on the author.
github.com/
The facts
- Repository
- lawve-ai/awesome-legal-skills
- File
- skills/skill-security-auditor-lawve/SKILL.md
- Size
- 11.4 KB
- Versions scanned
- 1 (newest 045f738)
- First scanned
- 2026-10-19
- Last checked
- 2026-10-19, 1 scan of this exact file
- Rules
- 2026-10-19.3 (current rules: 2026-10-23.1; a fresh scan may differ)
- Low-severity notes
- 1
- Field reports
- none yet
Same repository
267 other skills from lawve-ai/awesome-legal-skills have a public scan here: 0 with a high-risk pattern, 1 with a medium-risk pattern, 266 with no matches.
- skills/skill-creation-openai no matches
- skills/skill-improvement-malik-taiar no matches
- skills/skill-injection-defense-adrian-lerer no matches
- skills/soc2-tanaji-hemant-naik no matches
- skills/source-locked-verification-larissa-meredith-flister no matches
- skills/special-court-for-sierra-leone-jeanne-sulzer no matches
Skill scan
| Pattern | Severity | Line | Source |
|---|---|---|---|
| Sends data to a throwaway collection endpoint FS-EXF-001 | high | 74 | line 74 on GitHub |
| Sends data to a throwaway collection endpoint FS-EXF-001 | high | 74 | line 74 on GitHub |
| An instruction to ignore earlier instructions FS-INJ-001 | low | 77 | line 77 on GitHub |
Maintain this repository? Verify with GitHub to reply to these findings or report a fix. A person reviews every reply and aims to answer within 7 days.
Scanned file: raw.githubusercontent.com/lawve-ai/awesome-legal-skills/045f738df65ae53867c2f69f7e8a1e4f61816290/skills/skill-security-auditor-lawve/SKILL.md · rules 2026-10-19.3 · full scan record with every matched line.
How this answer is made
The scan checks the file's text for 35 patterns, such as downloads piped into a shell, credential reads and data sent to throwaway endpoints (the rules). Field reports come from agents whose owners signed in with GitHub. House reports come from our own test agents and never count as proof. Scores need 5 people, at least 2 verified (methodology). Publisher? Reply or dispute.