Home/DataChad/Trust report

Trust and health report

DataChad - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated 1w · GitHub synced 1w

Maintenance

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Dormant18% signal

last push 917d ago · last release 2y

0 stars (30d) · 0 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 638977082
  • Not a fork
  • Personal account
  • Computed 1w

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
31
View source evidence

deps.dev advisories

Not queried
Scanner
deps.dev@v1
View source evidence

OpenSSF Scorecard

Not queried
Scanner
openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-7p48-42j8-8846
streamlit@1.31.0 · osv@v1
requirements.txt
GHSA-rxff-vr5r-8cj5
streamlit@1.31.0 · osv@v1
requirements.txt
PYSEC-2024-153
streamlit@1.31.0 · osv@v1
requirements.txt
PYSEC-2026-212
streamlit@1.31.0 · osv@v1
requirements.txt
GHSA-3644-q5cj-c5c7
langchain@0.1.6 · osv@v1
requirements.txt
GHSA-3hjh-jh2h-vrg6
langchain@0.1.6 · osv@v1
requirements.txt
GHSA-45pg-36p6-83v9
langchain@0.1.6 · osv@v1
requirements.txt
GHSA-gr75-jv2w-4656
langchain@0.1.6 · osv@v1
requirements.txt
PYSEC-2024-118
langchain@0.1.6 · osv@v1
requirements.txt
PYSEC-2024-43
langchain@0.1.6 · osv@v1
requirements.txt
PYSEC-2026-1507
langchain@0.1.6 · osv@v1
requirements.txt
GHSA-32r8-54hf-c9p3
unstructured@0.6.5 · osv@v1
requirements.txt
GHSA-gm8q-m8mv-jj5m
unstructured@0.6.5 · osv@v1
requirements.txt
PYSEC-2026-1993
unstructured@0.6.5 · osv@v1
requirements.txt
PYSEC-2026-558
unstructured@0.6.5 · osv@v1
requirements.txt
GHSA-mf9w-mj56-hr94
python-dotenv@1.0.0 · osv@v1
requirements.txt
GHSA-g7vv-2v7x-gj9p
tqdm@4.65.0 · osv@v1
requirements.txt
PYSEC-2026-1976
tqdm@4.65.0 · osv@v1
requirements.txt
GHSA-2mqj-m65w-jghx
GitPython@3.1.31 · osv@v1
requirements.txt
GHSA-7545-fcxq-7j24
GitPython@3.1.31 · osv@v1
requirements.txt
GHSA-cwvm-v4w8-q58c
GitPython@3.1.31 · osv@v1
requirements.txt
GHSA-mv93-w799-cj2w
GitPython@3.1.31 · osv@v1
requirements.txt
GHSA-pr76-5cm5-w9cj
GitPython@3.1.31 · osv@v1
requirements.txt
GHSA-rpm5-65cw-6hj4
GitPython@3.1.31 · osv@v1
requirements.txt
GHSA-v87r-6q3f-2j67
GitPython@3.1.31 · osv@v1
requirements.txt
GHSA-wfm5-v35h-vwf4
GitPython@3.1.31 · osv@v1
requirements.txt
GHSA-x2qx-6953-8485
GitPython@3.1.31 · osv@v1
requirements.txt
PYSEC-2023-137
GitPython@3.1.31 · osv@v1
requirements.txt
PYSEC-2023-161
GitPython@3.1.31 · osv@v1
requirements.txt
PYSEC-2023-165
GitPython@3.1.31 · osv@v1
requirements.txt
PYSEC-2024-4
GitPython@3.1.31 · 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/gustavz-datachad/trust.

Common questions

Is DataChad maintained?
GraphCanon rates DataChad "Dormant" (18% maintenance signal from public GitHub metadata, computed 1w). Last push was 917 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is DataChad safe to use?
Last scanned 1mo (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 1mo (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 1w (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.
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 for full scope and limits.

Was this helpful?

Anonymous feedback helps us improve pages and translations.