--- title: "DataChad trust report" type: "trust-report" slug: "gustavz-datachad" canonical_url: "https://www.graphcanon.com/tools/gustavz-datachad/trust" computed_at: "2026-07-11T10:48:59.329Z" maintenance_label: "Dormant" security_status: "findings" --- # DataChad trust report _Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and optional dependency [security scans](/glossary/trust-and-signals/security-scan). Not a security guarantee._ ## Maintenance - Label: Dormant (18% recency signal) - Days since last push: 882 - Last release: 2023-11-24T13:15:11Z - Methodology: github_public_v1 ## Provenance - GitHub repo id: 638977082 - Not a fork - Owner type: User - Computed at: 2026-07-11T10:48:59.329Z - Methodology: github_public_v1 ## Security scan - Status: Findings present (0 critical, 0 high, 0 medium, 31 low) · last scan 2026-07-11T10:49:00.084Z ### Findings - **low**: GHSA-7p48-42j8-8846 (streamlit@1.31.0 · requirements.txt) - **low**: GHSA-rxff-vr5r-8cj5 (streamlit@1.31.0 · requirements.txt) - **low**: PYSEC-2024-153 (streamlit@1.31.0 · requirements.txt) - **low**: PYSEC-2026-212 (streamlit@1.31.0 · requirements.txt) - **low**: GHSA-3644-q5cj-c5c7 (langchain@0.1.6 · requirements.txt) - **low**: GHSA-3hjh-jh2h-vrg6 (langchain@0.1.6 · requirements.txt) - **low**: GHSA-45pg-36p6-83v9 (langchain@0.1.6 · requirements.txt) - **low**: GHSA-gr75-jv2w-4656 (langchain@0.1.6 · requirements.txt) - **low**: PYSEC-2024-118 (langchain@0.1.6 · requirements.txt) - **low**: PYSEC-2024-43 (langchain@0.1.6 · requirements.txt) - **low**: PYSEC-2026-1507 (langchain@0.1.6 · requirements.txt) - **low**: GHSA-32r8-54hf-c9p3 (unstructured@0.6.5 · requirements.txt) - **low**: GHSA-gm8q-m8mv-jj5m (unstructured@0.6.5 · requirements.txt) - **low**: PYSEC-2026-1993 (unstructured@0.6.5 · requirements.txt) - **low**: PYSEC-2026-558 (unstructured@0.6.5 · requirements.txt) - **low**: GHSA-mf9w-mj56-hr94 (python-dotenv@1.0.0 · requirements.txt) - **low**: GHSA-g7vv-2v7x-gj9p (tqdm@4.65.0 · requirements.txt) - **low**: PYSEC-2026-1976 (tqdm@4.65.0 · requirements.txt) - **low**: GHSA-2mqj-m65w-jghx (GitPython@3.1.31 · requirements.txt) - **low**: GHSA-7545-fcxq-7j24 (GitPython@3.1.31 · requirements.txt) - **low**: GHSA-cwvm-v4w8-q58c (GitPython@3.1.31 · requirements.txt) - **low**: GHSA-mv93-w799-cj2w (GitPython@3.1.31 · requirements.txt) - **low**: GHSA-pr76-5cm5-w9cj (GitPython@3.1.31 · requirements.txt) - **low**: GHSA-rpm5-65cw-6hj4 (GitPython@3.1.31 · requirements.txt) - **low**: GHSA-v87r-6q3f-2j67 (GitPython@3.1.31 · requirements.txt) - **low**: GHSA-wfm5-v35h-vwf4 (GitPython@3.1.31 · requirements.txt) - **low**: GHSA-x2qx-6953-8485 (GitPython@3.1.31 · requirements.txt) - **low**: PYSEC-2023-137 (GitPython@3.1.31 · requirements.txt) - **low**: PYSEC-2023-161 (GitPython@3.1.31 · requirements.txt) - **low**: PYSEC-2023-165 (GitPython@3.1.31 · requirements.txt) - **low**: PYSEC-2024-4 (GitPython@3.1.31 · requirements.txt) ## Method and caveats These are heuristics from public GitHub data and optional dependency scans, sourced and dated. "No criticals found on 2026-07-11" is not a guarantee of safety. See the full methodology: [/trust-methodology](/trust-methodology.md). ## Common questions ### Is DataChad maintained? GraphCanon rates DataChad "Dormant" (18% maintenance signal from public GitHub metadata, computed today). Last push was 882 days ago. This is a recency heuristic, not a guarantee the project will stay maintained. ### Is DataChad safe to use? Last scanned today (deps profile). Status: 31 low - 31 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 DataChad as safe - review maintenance, provenance, and scan findings on this page before adopting. ### Is DataChad a fork? No. DataChad is not flagged as a fork in GitHub metadata at the time of the last refresh. ### Does DataChad have known security vulnerabilities? Last scanned today (deps profile). Status: 31 low - 31 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 DataChad 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 DataChad? We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for DataChad. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology). ### How does GraphCanon assess trust for DataChad? 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](/trust-methodology) for full scope and limits. --- **Machine-readable endpoints** - JSON: [`/api/graphcanon/tools/gustavz-datachad/trust`](/api/graphcanon/tools/gustavz-datachad/trust) - LLM index: [/llms.txt](/llms.txt) - Full corpus: [/llms-full.txt](/llms-full.txt) _GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_