ossfuzz

SAFE max severity LOWSkillSpector Caution 35 registry trailofbits last scanned 1 scan

Verdict safe, but 3 findings (3 low), mainly data exfiltration, policy violation. Most recent scan 2026-02-08.

This skill is SAFE for use. It provides educational documentation about OSS-Fuzz, Google's continuous fuzzing infrastructure for open-source projects. The skill contains only markdown documentation with no executable code, no network calls, no data exfiltration, and no prompt injection attempts. It serves as a reference guide for developers who want to use OSS-Fuzz for fuzzing their projects. The only minor issues are missing optional metadata fields and references to external example files that are not included in the package. These are informational concerns that do not pose security risks.

Scanner's overall assessment (LLM analyzer)

Second scanner: NVIDIA SkillSpector

Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.

What this skill does

OSS-Fuzz provides free continuous fuzzing for open source projects. Use when setting up continuous fuzzing infrastructure or enrolling projects.

Package
1 file, 16 KB
SKILL.md
1843 words, 12+ sections
Code
None. Instructions only.

SKILL.md covers: OSS-Fuzz · Overview · Key Concepts · When to Apply · Quick Reference · OSS-Fuzz Project Components · Bug Tracker · Build Status System · Fuzz Introspector · Step-by-Step: Running a Single Harness · Step 1: Clone OSS-Fuzz · Step 2: Build Project Image

Findings

LOW Skill does not specify a license Policy Violationstatic

Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.

SKILL.md

Remediation: Add 'license' field to SKILL.md frontmatter (e.g., MIT, Apache-2.0)
LOW Missing Optional Metadata Fields Data Exfiltrationllm

The skill manifest is missing optional metadata fields including 'license', 'compatibility', and 'allowed-tools'. While these fields are optional per the agent skills specification, their absence makes it harder to assess the skill's intended usage constraints and compatibility requirements.

SKILL.md

YAML frontmatter missing: license, compatibility, allowed-tools fields
Remediation: Add optional metadata fields to improve transparency: specify license (e.g., Apache-2.0), compatibility (e.g., 'Works in Claude.ai, Claude Code, API'), and allowed-tools (e.g., [Read, Bash, Python]) to clarify intended tool usage.
LOW Referenced Files Not Found in Package Data Exfiltrationllm

The skill instructions reference four Python files (atheris.py, fuzzing.py, cbor2.py, specific.py) that are not included in the skill package. These appear to be example harness files from OSS-Fuzz documentation. While not a direct security threat, missing referenced files could cause confusion or errors if users expect these files to be present.

Referenced files not found: atheris.py, fuzzing.py, cbor2.py, specific.py
Remediation: Either include the referenced example files in the skill package, or clarify in the documentation that these are external examples from OSS-Fuzz projects that users should reference from the official OSS-Fuzz repository.

What is in the package

FileKindSize
SKILL.mddoc16 KB

External hosts referenced

github.com google.github.io appsec.guide blog.trailofbits.com cloud.google.com issues.oss-fuzz.com oss-fuzz-build-logs.storage.googleapis.com oss-fuzz-introspector.storage.googleapis.com

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

What we did not check

Sources