---
title: "Fun-ASR trust report"
type: "trust-report"
slug: "funaudiollm-fun-asr"
canonical_url: "https://www.graphcanon.com/tools/funaudiollm-fun-asr/trust"
computed_at: "2026-07-11T12:19:20.280Z"
maintenance_label: "Very active"
security_status: "findings"
---

# Fun-ASR 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: Very active (96% recency signal)
- Days since last push: 4
- Last release: 2026-06-29T13:24:05Z
- Releases (90d): 5
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 1116516142
- Not a fork
- Owner type: Organization
- Computed at: 2026-07-11T12:19:20.280Z
- Methodology: github_public_v1

## Security scan

- Status: Findings present (0 critical, 0 high, 0 medium, 26 low) · last scan 2026-07-11T12:19:24.723Z

### Findings

- **low**: GHSA-qfhq-4f3w-5fph (torch@2.9.0 · requirements.txt)
- **low**: GHSA-rrmf-rvhw-rf47 (torch@2.9.0 · requirements.txt)
- **low**: GHSA-vgrw-7cvw-pwgx (torch@2.9.0 · requirements.txt)
- **low**: PYSEC-2026-139 (torch@2.9.0 · requirements.txt)
- **low**: GHSA-29pf-2h5f-8g72 (transformers@4.51.3 · requirements.txt)
- **low**: GHSA-37mw-44qp-f5jm (transformers@4.51.3 · requirements.txt)
- **low**: GHSA-4w7r-h757-3r74 (transformers@4.51.3 · requirements.txt)
- **low**: GHSA-59p9-h35m-wg4g (transformers@4.51.3 · requirements.txt)
- **low**: GHSA-69w3-r845-3855 (transformers@4.51.3 · requirements.txt)
- **low**: GHSA-9356-575x-2w9m (transformers@4.51.3 · requirements.txt)
- **low**: GHSA-phhr-52qp-3mj4 (transformers@4.51.3 · requirements.txt)
- **low**: GHSA-rcv9-qm8p-9p6j (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2025-211 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2025-212 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2025-213 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2025-214 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2025-215 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2025-216 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2025-217 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2025-218 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2026-1977 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2026-1980 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2026-1981 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2026-1983 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2026-1986 (transformers@4.51.3 · requirements.txt)
- **low**: PYSEC-2026-1988 (transformers@4.51.3 · 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 Fun-ASR maintained?

GraphCanon rates Fun-ASR "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 4 days ago. 5 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is Fun-ASR safe to use?

Last scanned today (deps profile). Status: 26 low - 26 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 Fun-ASR as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is Fun-ASR a fork?

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

### Does Fun-ASR have known security vulnerabilities?

Last scanned today (deps profile). Status: 26 low - 26 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 Fun-ASR 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 Fun-ASR?

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

### How does GraphCanon assess trust for Fun-ASR?

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/funaudiollm-fun-asr/trust`](/api/graphcanon/tools/funaudiollm-fun-asr/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/_
