Home/ChatAbstractions/Trust report

Trust and health report

ChatAbstractions - trust report

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

GraphCanon updated 2w · GitHub synced 2w

Maintenance

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

Dormant18% signal

last push 921d ago

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 716340652
  • Not a fork
  • Personal account
  • Computed 2w

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
16
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-3644-q5cj-c5c7
langchain@0.0.350 · osv@v1
requirements.txt
GHSA-3hjh-jh2h-vrg6
langchain@0.0.350 · osv@v1
requirements.txt
GHSA-45pg-36p6-83v9
langchain@0.0.350 · osv@v1
requirements.txt
GHSA-gr75-jv2w-4656
langchain@0.0.350 · osv@v1
requirements.txt
GHSA-h9j7-5xvc-qhg5
langchain@0.0.350 · osv@v1
requirements.txt
GHSA-rgp8-pm28-3759
langchain@0.0.350 · osv@v1
requirements.txt
PYSEC-2024-118
langchain@0.0.350 · osv@v1
requirements.txt
PYSEC-2024-43
langchain@0.0.350 · osv@v1
requirements.txt
PYSEC-2026-1507
langchain@0.0.350 · osv@v1
requirements.txt
PYSEC-2026-1509
langchain@0.0.350 · osv@v1
requirements.txt
PYSEC-2026-1510
langchain@0.0.350 · osv@v1
requirements.txt
GHSA-9hjg-9r4m-mvj7
requests@2.31.0 · osv@v1
requirements.txt
GHSA-9wx4-h78v-vm56
requests@2.31.0 · osv@v1
requirements.txt
GHSA-gc5v-m9x4-r6x2
requests@2.31.0 · osv@v1
requirements.txt
PYSEC-2026-1872
requests@2.31.0 · osv@v1
requirements.txt
PYSEC-2026-1873
requests@2.31.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/andrewnguonly-chatabstractions/trust.

Common questions

Is ChatAbstractions maintained?
GraphCanon rates ChatAbstractions "Dormant" (18% maintenance signal from public GitHub metadata, computed 2w). Last push was 921 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is ChatAbstractions safe to use?
Last scanned 1mo (deps profile). Status: 16 low - 16 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 ChatAbstractions as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is ChatAbstractions a fork?
No. ChatAbstractions is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does ChatAbstractions have known security vulnerabilities?
Last scanned 1mo (deps profile). Status: 16 low - 16 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 ChatAbstractions trust report updated?
Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 2w (methodology github_public_v1).
What does GraphCanon never claim about ChatAbstractions?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for ChatAbstractions. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for ChatAbstractions?
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.