Trust and health report
LLMFuzzer - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 2w · GitHub synced 2w · 33 views this month
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Dormant18% signal
last push 904d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 643275640
- Not a fork
- Personal account
- Computed 2w
Security intelligence
Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.
OSV dependency advisories
Published findings- Last query
- 1mo
- Scanner
- osv@v1
- Stored findings
- 31
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-248v-346w-9cwc
certifi@2023.5.7 · osv@v1
requirements.txt
GHSA-xqr8-7jwr-rhp7
certifi@2023.5.7 · osv@v1
requirements.txt
PYSEC-2023-135
certifi@2023.5.7 · osv@v1
requirements.txt
PYSEC-2024-230
certifi@2023.5.7 · osv@v1
requirements.txt
GHSA-65pc-fj4g-8rjx
idna@3.4 · osv@v1
requirements.txt
GHSA-jjg7-2v4v-x38h
idna@3.4 · osv@v1
requirements.txt
PYSEC-2024-60
idna@3.4 · osv@v1
requirements.txt
PYSEC-2026-215
idna@3.4 · osv@v1
requirements.txt
GHSA-9hjg-9r4m-mvj7
requests@2.30.0 · osv@v1
requirements.txt
GHSA-9wx4-h78v-vm56
requests@2.30.0 · osv@v1
requirements.txt
GHSA-gc5v-m9x4-r6x2
requests@2.30.0 · osv@v1
requirements.txt
GHSA-j8r2-6x86-q33q
requests@2.30.0 · osv@v1
requirements.txt
PYSEC-2023-74
requests@2.30.0 · osv@v1
requirements.txt
PYSEC-2026-1872
requests@2.30.0 · osv@v1
requirements.txt
PYSEC-2026-1873
requests@2.30.0 · osv@v1
requirements.txt
GHSA-2xpw-w6gg-jr37
urllib3@2.0.2 · osv@v1
requirements.txt
GHSA-34jh-p97f-mpxf
urllib3@2.0.2 · osv@v1
requirements.txt
GHSA-38jv-5279-wg99
urllib3@2.0.2 · osv@v1
requirements.txt
GHSA-g4mx-q9vg-27p4
urllib3@2.0.2 · osv@v1
requirements.txt
GHSA-gm62-xv2j-4w53
urllib3@2.0.2 · osv@v1
requirements.txt
GHSA-pq67-6m6q-mj2v
urllib3@2.0.2 · osv@v1
requirements.txt
GHSA-qccp-gfcp-xxvc
urllib3@2.0.2 · osv@v1
requirements.txt
GHSA-v845-jxx5-vc9f
urllib3@2.0.2 · osv@v1
requirements.txt
PYSEC-2023-192
urllib3@2.0.2 · osv@v1
requirements.txt
PYSEC-2023-212
urllib3@2.0.2 · osv@v1
requirements.txt
PYSEC-2026-141
urllib3@2.0.2 · osv@v1
requirements.txt
PYSEC-2026-1994
urllib3@2.0.2 · osv@v1
requirements.txt
PYSEC-2026-1995
urllib3@2.0.2 · osv@v1
requirements.txt
PYSEC-2026-1996
urllib3@2.0.2 · osv@v1
requirements.txt
PYSEC-2026-1998
urllib3@2.0.2 · osv@v1
requirements.txt
PYSEC-2026-1999
urllib3@2.0.2 · osv@v1
requirements.txt
Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/mnns-llmfuzzer/trust.
Common questions
- Is LLMFuzzer maintained?
- GraphCanon rates LLMFuzzer "Dormant" (18% maintenance signal from public GitHub metadata, computed 2w). Last push was 904 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is LLMFuzzer safe to use?
- Last scanned 1mo (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 1mo (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 2w (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.
- 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 for full scope and limits.