Trust and health report
GPT-SoVITS - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated today · GitHub synced today
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Very active96% signal
last push 1d ago · last release 1y
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 743230067
- Not a fork
- Personal account
- Computed today
Security scan
Dependency advisory security scan when a lockfile is present. Not a full code audit.
- Status
- 39 low
- Last scan
- today
- Scanner
- osv@v1
Findings
GHSA-75m9-98v2-hjpm
pytorch-lightning@2.4 · requirements.txt
GHSA-29pf-2h5f-8g72
transformers@4.43 · requirements.txt
GHSA-37mw-44qp-f5jm
transformers@4.43 · requirements.txt
GHSA-4w7r-h757-3r74
transformers@4.43 · requirements.txt
GHSA-59p9-h35m-wg4g
transformers@4.43 · requirements.txt
GHSA-69w3-r845-3855
transformers@4.43 · requirements.txt
GHSA-6rvg-6v2m-4j46
transformers@4.43 · requirements.txt
GHSA-9356-575x-2w9m
transformers@4.43 · requirements.txt
GHSA-fpwr-67px-3qhx
transformers@4.43 · requirements.txt
GHSA-hxxf-235m-72v3
transformers@4.43 · requirements.txt
GHSA-jjph-296x-mrcr
transformers@4.43 · requirements.txt
GHSA-phhr-52qp-3mj4
transformers@4.43 · requirements.txt
GHSA-q2wp-rjmx-x6x9
transformers@4.43 · requirements.txt
GHSA-qq3j-4f4f-9583
transformers@4.43 · requirements.txt
GHSA-qxrp-vhvm-j765
transformers@4.43 · requirements.txt
GHSA-rcv9-qm8p-9p6j
transformers@4.43 · requirements.txt
GHSA-wrfc-pvp9-mr9g
transformers@4.43 · requirements.txt
PYSEC-2024-227
transformers@4.43 · requirements.txt
PYSEC-2024-228
transformers@4.43 · requirements.txt
PYSEC-2024-229
transformers@4.43 · requirements.txt
PYSEC-2025-211
transformers@4.43 · requirements.txt
PYSEC-2025-212
transformers@4.43 · requirements.txt
PYSEC-2025-213
transformers@4.43 · requirements.txt
PYSEC-2025-214
transformers@4.43 · requirements.txt
PYSEC-2025-215
transformers@4.43 · requirements.txt
PYSEC-2025-216
transformers@4.43 · requirements.txt
PYSEC-2025-217
transformers@4.43 · requirements.txt
PYSEC-2025-218
transformers@4.43 · requirements.txt
PYSEC-2025-40
transformers@4.43 · requirements.txt
PYSEC-2026-1977
transformers@4.43 · requirements.txt
PYSEC-2026-1980
transformers@4.43 · requirements.txt
PYSEC-2026-1981
transformers@4.43 · requirements.txt
PYSEC-2026-1982
transformers@4.43 · requirements.txt
PYSEC-2026-1983
transformers@4.43 · requirements.txt
PYSEC-2026-1984
transformers@4.43 · requirements.txt
PYSEC-2026-1985
transformers@4.43 · requirements.txt
PYSEC-2026-1986
transformers@4.43 · requirements.txt
PYSEC-2026-1987
transformers@4.43 · requirements.txt
PYSEC-2026-1988
transformers@4.43 · requirements.txt
Method and caveats:these are sourced, dated heuristics from public GitHub data and optional dependency scans. A status like "no criticals found on 2026-07-11" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/rvc-boss-gpt-sovits/trust.
Common questions
- Is GPT-SoVITS maintained?
- GraphCanon rates GPT-SoVITS "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 1 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is GPT-SoVITS safe to use?
- Last scanned today (deps profile). Status: 39 low - 39 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 GPT-SoVITS as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is GPT-SoVITS a fork?
- No. GPT-SoVITS is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does GPT-SoVITS have known security vulnerabilities?
- Last scanned today (deps profile). Status: 39 low - 39 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 GPT-SoVITS 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 GPT-SoVITS?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for GPT-SoVITS. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for GPT-SoVITS?
- 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.