Trust and health report
vits - 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 · 26 views this month
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Dormant18% signal
last push 966d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 371194369
- 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
- 37
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-5545-2q6w-2gh6
numpy@1.18.5 · osv@v1
requirements.txt
GHSA-6p56-wp2h-9hxr
numpy@1.18.5 · osv@v1
requirements.txt
GHSA-f7c7-j99h-c22f
numpy@1.18.5 · osv@v1
requirements.txt
GHSA-fpfv-jqm9-f5jm
numpy@1.18.5 · osv@v1
requirements.txt
PYSEC-2021-856
numpy@1.18.5 · osv@v1
requirements.txt
PYSEC-2021-857
numpy@1.18.5 · osv@v1
requirements.txt
PYSEC-2023-102
scipy@1.5.2 · osv@v1
requirements.txt
PYSEC-2023-114
scipy@1.5.2 · osv@v1
requirements.txt
GHSA-3749-ghw9-m3mg
torch@1.6.0 · osv@v1
requirements.txt
GHSA-47fc-vmwq-366v
torch@1.6.0 · osv@v1
requirements.txt
GHSA-53q9-r3pm-6pq6
torch@1.6.0 · osv@v1
requirements.txt
GHSA-5pcm-hx3q-hm94
torch@1.6.0 · osv@v1
requirements.txt
GHSA-887c-mr87-cxwp
torch@1.6.0 · osv@v1
requirements.txt
GHSA-c678-jfcj-6jmf
torch@1.6.0 · osv@v1
requirements.txt
GHSA-f4hp-rmr7-r7v8
torch@1.6.0 · osv@v1
requirements.txt
GHSA-pg7h-5qx3-wjr3
torch@1.6.0 · osv@v1
requirements.txt
GHSA-qfhq-4f3w-5fph
torch@1.6.0 · osv@v1
requirements.txt
GHSA-rrmf-rvhw-rf47
torch@1.6.0 · osv@v1
requirements.txt
GHSA-vgrw-7cvw-pwgx
torch@1.6.0 · osv@v1
requirements.txt
GHSA-x3gm-94wq-g975
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2022-43015
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2024-250
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2024-251
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2024-252
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2024-259
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2025-191
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2025-198
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2025-203
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2025-204
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2025-205
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2025-206
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2025-207
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2025-208
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2025-209
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2025-41
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2026-139
torch@1.6.0 · osv@v1
requirements.txt
PYSEC-2026-1970
torch@1.6.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/jaywalnut310-vits/trust.
Common questions
- Is vits maintained?
- GraphCanon rates vits "Dormant" (18% maintenance signal from public GitHub metadata, computed 3w). Last push was 966 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is vits safe to use?
- Last scanned 1mo (deps profile). Status: 37 low - 37 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 vits as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is vits a fork?
- No. vits is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does vits have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 37 low - 37 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 vits 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 vits?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for vits. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for vits?
- 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.