address-sanitizer
No security findings. Scanned 1 time, most recently 2026-02-06.
Second scanner: NVIDIA SkillSpector
SkillSpector found no issues but could not fully inspect the package, usually because SKILL.md refers to a file that is not present, so it fails closed to CAUTION instead of SAFE. Read it as "not fully checked", not as a finding. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
AddressSanitizer detects memory errors during fuzzing. Use when fuzzing C/C++ code to find buffer overflows and use-after-free bugs.
- Package
- 1 file, 11 KB
- SKILL.md
- 1391 words, 12+ sections
- Code
- None. Instructions only.
SKILL.md covers: AddressSanitizer (ASan) · Overview · Key Concepts · When to Apply · Quick Reference · Step-by-Step · Step 1: Compile with ASan · Step 2: Configure ASan Options · Step 3: Run Your Program · Step 4: Adjust Fuzzer Memory Limits · Common Patterns · Pattern: Basic ASan Integration
Findings
No findings. SAFE
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 11 KB |
External hosts referenced
github.com clang.llvm.org gcc.gnu.org rust-fuzz.github.io www.usenix.org
Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.
Package contents recorded 2026-10-22 at commit a50696e20581. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Llm analyzer. A language model reads the skill and reports intent-level issues the rules cannot express.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
- Meta analyzer. A second model pass that validates, deduplicates and re-scores the other analyzers' findings.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://github.com/trailofbits/skills
- Raw scan result: plugins-testing-handbook-skills-skills-address-sanitizer-scan.json
- Badge for your README:
- Request a re-scan