GraphCanon
Home/OuteTTS/Trust report

Trust and health report

OuteTTS - 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.

Slowing36% signal

last push 110d ago · last release 1y

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 883037083
  • Not a fork
  • Personal account
  • Computed today

Security scan

Dependency advisory security scan when a lockfile is present. Not a full code audit.

Status
18 low
Last scan
today
Scanner
osv@v1

Findings

GHSA-29pf-2h5f-8g72
transformers@4.52.3 · requirements.txt
GHSA-4w7r-h757-3r74
transformers@4.52.3 · requirements.txt
GHSA-59p9-h35m-wg4g
transformers@4.52.3 · requirements.txt
GHSA-69w3-r845-3855
transformers@4.52.3 · requirements.txt
GHSA-9356-575x-2w9m
transformers@4.52.3 · requirements.txt
GHSA-rcv9-qm8p-9p6j
transformers@4.52.3 · requirements.txt
PYSEC-2025-211
transformers@4.52.3 · requirements.txt
PYSEC-2025-212
transformers@4.52.3 · requirements.txt
PYSEC-2025-213
transformers@4.52.3 · requirements.txt
PYSEC-2025-214
transformers@4.52.3 · requirements.txt
PYSEC-2025-215
transformers@4.52.3 · requirements.txt
PYSEC-2025-216
transformers@4.52.3 · requirements.txt
PYSEC-2025-217
transformers@4.52.3 · requirements.txt
PYSEC-2025-218
transformers@4.52.3 · requirements.txt
PYSEC-2026-1980
transformers@4.52.3 · requirements.txt
PYSEC-2026-1981
transformers@4.52.3 · requirements.txt
PYSEC-2026-1983
transformers@4.52.3 · requirements.txt
PYSEC-2026-1988
transformers@4.52.3 · 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/edwko-outetts/trust.

Common questions

Is OuteTTS maintained?
GraphCanon rates OuteTTS "Slowing" (36% maintenance signal from public GitHub metadata, computed today). Last push was 110 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is OuteTTS safe to use?
Last scanned today (deps profile). Status: 18 low - 18 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 OuteTTS as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is OuteTTS a fork?
No. OuteTTS is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does OuteTTS have known security vulnerabilities?
Last scanned today (deps profile). Status: 18 low - 18 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 OuteTTS 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 OuteTTS?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for OuteTTS. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for OuteTTS?
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.