Home/SenseVoice/Trust report

Trust and health report

SenseVoice - 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 1w · 5 releases (90d)

Provenance

Repository identity and fork provenance (github_public_v1).

Security scan

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

Status
No criticals
Last scan
today
Scanner
osv@v1

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/funaudiollm-sensevoice/trust.

Common questions

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