Trust and health report
repochat - 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 681d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 661847690
- Not a fork
- Personal account
- Computed today
Security scan
Dependency advisory security scan when a lockfile is present. Not a full code audit.
- Status
- 27 low
- Last scan
- today
- Scanner
- osv@v1
Findings
GHSA-9hjg-9r4m-mvj7
requests@2.31.0 · requirements.txt
GHSA-9wx4-h78v-vm56
requests@2.31.0 · requirements.txt
GHSA-gc5v-m9x4-r6x2
requests@2.31.0 · requirements.txt
PYSEC-2026-1872
requests@2.31.0 · requirements.txt
PYSEC-2026-1873
requests@2.31.0 · requirements.txt
GHSA-7p48-42j8-8846
streamlit@1.28.0 · requirements.txt
GHSA-8qw9-gf7w-42x5
streamlit@1.28.0 · requirements.txt
GHSA-rxff-vr5r-8cj5
streamlit@1.28.0 · requirements.txt
PYSEC-2024-153
streamlit@1.28.0 · requirements.txt
PYSEC-2026-212
streamlit@1.28.0 · requirements.txt
GHSA-3644-q5cj-c5c7
langchain@0.0.313 · requirements.txt
GHSA-3hjh-jh2h-vrg6
langchain@0.0.313 · requirements.txt
GHSA-45pg-36p6-83v9
langchain@0.0.313 · requirements.txt
GHSA-655w-fm8m-m478
langchain@0.0.313 · requirements.txt
GHSA-6h8p-4hx9-w66c
langchain@0.0.313 · requirements.txt
GHSA-gr75-jv2w-4656
langchain@0.0.313 · requirements.txt
GHSA-h59x-p739-982c
langchain@0.0.313 · requirements.txt
GHSA-h9j7-5xvc-qhg5
langchain@0.0.313 · requirements.txt
GHSA-prgp-w7vf-ch62
langchain@0.0.313 · requirements.txt
GHSA-rgp8-pm28-3759
langchain@0.0.313 · requirements.txt
PYSEC-2023-205
langchain@0.0.313 · requirements.txt
PYSEC-2024-118
langchain@0.0.313 · requirements.txt
PYSEC-2024-43
langchain@0.0.313 · requirements.txt
PYSEC-2026-1507
langchain@0.0.313 · requirements.txt
PYSEC-2026-1508
langchain@0.0.313 · requirements.txt
PYSEC-2026-1509
langchain@0.0.313 · requirements.txt
PYSEC-2026-1510
langchain@0.0.313 · 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/pnkvalavala-repochat/trust.
Common questions
- Is repochat maintained?
- GraphCanon rates repochat "Dormant" (18% maintenance signal from public GitHub metadata, computed today). Last push was 681 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is repochat safe to use?
- Last scanned today (deps profile). Status: 27 low - 27 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 repochat as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is repochat a fork?
- No. repochat is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does repochat have known security vulnerabilities?
- Last scanned today (deps profile). Status: 27 low - 27 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 repochat 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 repochat?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for repochat. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for repochat?
- 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.