Trust and health report
mukh - 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.
Dormant18% signal
last push 376d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 936811955
- Not a fork
- Personal account
- Computed today
Security scan
Dependency advisory security scan when a lockfile is present. Not a full code audit.
- Status
- 29 low
- Last scan
- today
- Scanner
- osv@v1
Findings
GHSA-qr4w-53vh-m672
opencv-python@4.8.0 · requirements.txt
PYSEC-2023-183
opencv-python@4.8.0 · requirements.txt
GHSA-3749-ghw9-m3mg
torch@2.0.0 · requirements.txt
GHSA-53q9-r3pm-6pq6
torch@2.0.0 · requirements.txt
GHSA-5pcm-hx3q-hm94
torch@2.0.0 · requirements.txt
GHSA-887c-mr87-cxwp
torch@2.0.0 · requirements.txt
GHSA-c678-jfcj-6jmf
torch@2.0.0 · requirements.txt
GHSA-f4hp-rmr7-r7v8
torch@2.0.0 · requirements.txt
GHSA-pg7h-5qx3-wjr3
torch@2.0.0 · requirements.txt
GHSA-qfhq-4f3w-5fph
torch@2.0.0 · requirements.txt
GHSA-rrmf-rvhw-rf47
torch@2.0.0 · requirements.txt
GHSA-vgrw-7cvw-pwgx
torch@2.0.0 · requirements.txt
GHSA-x3gm-94wq-g975
torch@2.0.0 · requirements.txt
PYSEC-2024-250
torch@2.0.0 · requirements.txt
PYSEC-2024-251
torch@2.0.0 · requirements.txt
PYSEC-2024-252
torch@2.0.0 · requirements.txt
PYSEC-2024-259
torch@2.0.0 · requirements.txt
PYSEC-2025-191
torch@2.0.0 · requirements.txt
PYSEC-2025-198
torch@2.0.0 · requirements.txt
PYSEC-2025-203
torch@2.0.0 · requirements.txt
PYSEC-2025-204
torch@2.0.0 · requirements.txt
PYSEC-2025-205
torch@2.0.0 · requirements.txt
PYSEC-2025-206
torch@2.0.0 · requirements.txt
PYSEC-2025-207
torch@2.0.0 · requirements.txt
PYSEC-2025-208
torch@2.0.0 · requirements.txt
PYSEC-2025-209
torch@2.0.0 · requirements.txt
PYSEC-2025-41
torch@2.0.0 · requirements.txt
PYSEC-2026-139
torch@2.0.0 · requirements.txt
PYSEC-2026-1970
torch@2.0.0 · 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/ishandutta0098-mukh/trust.
Common questions
- Is mukh maintained?
- GraphCanon rates mukh "Dormant" (18% maintenance signal from public GitHub metadata, computed today). Last push was 376 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is mukh safe to use?
- Last scanned today (deps profile). Status: 29 low - 29 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 mukh as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is mukh a fork?
- No. mukh is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does mukh have known security vulnerabilities?
- Last scanned today (deps profile). Status: 29 low - 29 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 mukh 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 mukh?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for mukh. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for mukh?
- 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.