Home/TTS-WebUI/Trust report

Trust and health report

TTS-WebUI - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated 3w · GitHub synced 3w · 29 views this month

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 3mo · 2 releases (90d)

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 633546245
  • Not a fork
  • Personal account
  • Computed 3w

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
20
View source evidence

deps.dev advisories

Not queried
Scanner
deps.dev@v1
View source evidence

OpenSSF Scorecard

Not queried
Scanner
openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-mf9w-mj56-hr94
python-dotenv@1.0.0 · osv@v1
requirements.txt
PYSEC-2024-38
fastapi@0.109.0 · osv@v1
requirements.txt
GHSA-39mp-8hj3-5c49
gradio@5.49.1 · osv@v1
requirements.txt
GHSA-7hp7-4p35-3cx2
gradio@5.49.1 · osv@v1
requirements.txt
GHSA-h3h8-3v2v-rg7m
gradio@5.49.1 · osv@v1
requirements.txt
GHSA-jmh7-g254-2cq9
gradio@5.49.1 · osv@v1
requirements.txt
GHSA-pfjf-5gxr-995x
gradio@5.49.1 · osv@v1
requirements.txt
PYSEC-2026-211
gradio@5.49.1 · osv@v1
requirements.txt
PYSEC-2026-63
gradio@5.49.1 · osv@v1
requirements.txt
PYSEC-2026-64
gradio@5.49.1 · osv@v1
requirements.txt
PYSEC-2026-65
gradio@5.49.1 · osv@v1
requirements.txt
PYSEC-2026-66
gradio@5.49.1 · osv@v1
requirements.txt
GHSA-cfh3-3jmp-rvhc
pillow@10.3.0 · osv@v1
requirements.txt
GHSA-pwv6-vv43-88gr
pillow@10.3.0 · osv@v1
requirements.txt
GHSA-r73j-pqj5-w3x7
pillow@10.3.0 · osv@v1
requirements.txt
GHSA-whj4-6x5x-4v2j
pillow@10.3.0 · osv@v1
requirements.txt
GHSA-wjx4-4jcj-g98j
pillow@10.3.0 · osv@v1
requirements.txt
PYSEC-2026-165
pillow@10.3.0 · osv@v1
requirements.txt
GHSA-4gg8-gxpx-9rph
uv@0.11.0 · osv@v1
requirements.txt
GHSA-pjjw-68hj-v9mw
uv@0.11.0 · 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/rsxdalv-tts-webui/trust.

Common questions

Is TTS-WebUI maintained?
GraphCanon rates TTS-WebUI "Very active" (96% maintenance signal from public GitHub metadata, computed 3w). Last push was 1 days ago. 2 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
Is TTS-WebUI safe to use?
Last scanned 1mo (deps profile). Status: 20 low - 20 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 TTS-WebUI as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is TTS-WebUI a fork?
No. TTS-WebUI is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does TTS-WebUI have known security vulnerabilities?
Last scanned 1mo (deps profile). Status: 20 low - 20 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 TTS-WebUI trust report updated?
Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 3w (methodology github_public_v1).
What does GraphCanon never claim about TTS-WebUI?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for TTS-WebUI. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for TTS-WebUI?
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.

Was this helpful?

Anonymous feedback helps us improve pages and translations.