---
title: "LLMFuzzer trust report"
type: "trust-report"
slug: "mnns-llmfuzzer"
canonical_url: "https://www.graphcanon.com/tools/mnns-llmfuzzer/trust"
computed_at: "2026-07-11T23:42:42.410Z"
maintenance_label: "Dormant"
security_status: "findings"
---

# LLMFuzzer trust report

_Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and optional dependency [security scans](/glossary/trust-and-signals/security-scan). Not a security guarantee._

## Maintenance

- Label: Dormant (18% recency signal)
- Days since last push: 880
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 643275640
- Not a fork
- Owner type: User
- Computed at: 2026-07-11T23:42:42.410Z
- Methodology: github_public_v1

## Security scan

- Status: Findings present (0 critical, 0 high, 0 medium, 31 low) · last scan 2026-07-11T23:42:42.745Z

### Findings

- **low**: GHSA-248v-346w-9cwc (certifi@2023.5.7 · requirements.txt)
- **low**: GHSA-xqr8-7jwr-rhp7 (certifi@2023.5.7 · requirements.txt)
- **low**: PYSEC-2023-135 (certifi@2023.5.7 · requirements.txt)
- **low**: PYSEC-2024-230 (certifi@2023.5.7 · requirements.txt)
- **low**: GHSA-65pc-fj4g-8rjx (idna@3.4 · requirements.txt)
- **low**: GHSA-jjg7-2v4v-x38h (idna@3.4 · requirements.txt)
- **low**: PYSEC-2024-60 (idna@3.4 · requirements.txt)
- **low**: PYSEC-2026-215 (idna@3.4 · requirements.txt)
- **low**: GHSA-9hjg-9r4m-mvj7 (requests@2.30.0 · requirements.txt)
- **low**: GHSA-9wx4-h78v-vm56 (requests@2.30.0 · requirements.txt)
- **low**: GHSA-gc5v-m9x4-r6x2 (requests@2.30.0 · requirements.txt)
- **low**: GHSA-j8r2-6x86-q33q (requests@2.30.0 · requirements.txt)
- **low**: PYSEC-2023-74 (requests@2.30.0 · requirements.txt)
- **low**: PYSEC-2026-1872 (requests@2.30.0 · requirements.txt)
- **low**: PYSEC-2026-1873 (requests@2.30.0 · requirements.txt)
- **low**: GHSA-2xpw-w6gg-jr37 (urllib3@2.0.2 · requirements.txt)
- **low**: GHSA-34jh-p97f-mpxf (urllib3@2.0.2 · requirements.txt)
- **low**: GHSA-38jv-5279-wg99 (urllib3@2.0.2 · requirements.txt)
- **low**: GHSA-g4mx-q9vg-27p4 (urllib3@2.0.2 · requirements.txt)
- **low**: GHSA-gm62-xv2j-4w53 (urllib3@2.0.2 · requirements.txt)
- **low**: GHSA-pq67-6m6q-mj2v (urllib3@2.0.2 · requirements.txt)
- **low**: GHSA-qccp-gfcp-xxvc (urllib3@2.0.2 · requirements.txt)
- **low**: GHSA-v845-jxx5-vc9f (urllib3@2.0.2 · requirements.txt)
- **low**: PYSEC-2023-192 (urllib3@2.0.2 · requirements.txt)
- **low**: PYSEC-2023-212 (urllib3@2.0.2 · requirements.txt)
- **low**: PYSEC-2026-141 (urllib3@2.0.2 · requirements.txt)
- **low**: PYSEC-2026-1994 (urllib3@2.0.2 · requirements.txt)
- **low**: PYSEC-2026-1995 (urllib3@2.0.2 · requirements.txt)
- **low**: PYSEC-2026-1996 (urllib3@2.0.2 · requirements.txt)
- **low**: PYSEC-2026-1998 (urllib3@2.0.2 · requirements.txt)
- **low**: PYSEC-2026-1999 (urllib3@2.0.2 · requirements.txt)

## Method and caveats

These are heuristics from public GitHub data and optional dependency scans, sourced and dated. 
"No criticals found on 2026-07-11" is not a guarantee of safety.
See the full methodology: [/trust-methodology](/trust-methodology.md).

## Common questions

### Is LLMFuzzer maintained?

GraphCanon rates LLMFuzzer "Dormant" (18% maintenance signal from public GitHub metadata, computed today). Last push was 880 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is LLMFuzzer safe to use?

Last scanned today (deps profile). Status: 31 low - 31 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify LLMFuzzer as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is LLMFuzzer a fork?

No. LLMFuzzer is not flagged as a fork in GitHub metadata at the time of the last refresh.

### Does LLMFuzzer have known security vulnerabilities?

Last scanned today (deps profile). Status: 31 low - 31 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.

### How often is the LLMFuzzer trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).

### What does GraphCanon never claim about LLMFuzzer?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for LLMFuzzer. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology).

### How does GraphCanon assess trust for LLMFuzzer?

Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read [trust methodology](/trust-methodology) for full scope and limits.

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/tools/mnns-llmfuzzer/trust`](/api/graphcanon/tools/mnns-llmfuzzer/trust)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_
