Trust and health report
gpt-researcher - 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.
Active82% signal
last push 21d ago · last release 1mo · 3 releases (90d)
+737 stars (30d) · -18 open issues (30d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 639835356
- 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
- 63
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
PYSEC-2024-38
fastapi@0.104.1 · osv@v1
requirements.txt
GHSA-mf9w-mj56-hr94
python-dotenv@1.0.0 · osv@v1
requirements.txt
GHSA-gr75-jv2w-4656
langchain@1.0.0 · osv@v1
requirements.txt
GHSA-3644-q5cj-c5c7
langchain-classic@1.0.0 · osv@v1
requirements.txt
GHSA-2g6r-c272-w58r
langchain-core@1.0.0 · osv@v1
requirements.txt
GHSA-6qv9-48xg-fc7f
langchain-core@1.0.0 · osv@v1
requirements.txt
GHSA-926x-3r5x-gfhw
langchain-core@1.0.0 · osv@v1
requirements.txt
GHSA-c67j-w6g6-q2cm
langchain-core@1.0.0 · osv@v1
requirements.txt
GHSA-pjwx-r37v-7724
langchain-core@1.0.0 · osv@v1
requirements.txt
GHSA-qh6h-p6c9-ff54
langchain-core@1.0.0 · osv@v1
requirements.txt
PYSEC-2026-1518
langchain-core@1.0.0 · osv@v1
requirements.txt
PYSEC-2026-373
langchain-core@1.0.0 · osv@v1
requirements.txt
GHSA-r7w7-9xr2-qq2r
langchain-openai@1.0.0 · osv@v1
requirements.txt
PYSEC-2026-76
langchain-openai@1.0.0 · osv@v1
requirements.txt
GHSA-fv5p-p927-qmxr
langchain-text-splitters@1.0.0 · osv@v1
requirements.txt
PYSEC-2026-77
langchain-text-splitters@1.0.0 · osv@v1
requirements.txt
GHSA-g48c-2wqr-h844
langgraph@0.2.76 · osv@v1
requirements.txt
PYSEC-2026-83
langgraph@0.2.76 · osv@v1
requirements.txt
GHSA-4xpc-pv4p-pm3w
litellm@1.71.0 · osv@v1
requirements.txt
GHSA-53mr-6c8q-9789
litellm@1.71.0 · osv@v1
requirements.txt
GHSA-69x8-hrgq-fjj8
litellm@1.71.0 · osv@v1
requirements.txt
GHSA-jjhc-v7c2-5hh6
litellm@1.71.0 · osv@v1
requirements.txt
GHSA-qrc4-49gv-mv9m
litellm@1.71.0 · osv@v1
requirements.txt
GHSA-wpfp-gwwc-vwq6
litellm@1.71.0 · osv@v1
requirements.txt
PYSEC-2026-388
litellm@1.71.0 · osv@v1
requirements.txt
PYSEC-2026-390
litellm@1.71.0 · osv@v1
requirements.txt
GHSA-32r8-54hf-c9p3
unstructured@0.13 · osv@v1
requirements.txt
GHSA-gm8q-m8mv-jj5m
unstructured@0.13 · osv@v1
requirements.txt
PYSEC-2026-1993
unstructured@0.13 · osv@v1
requirements.txt
PYSEC-2026-558
unstructured@0.13 · osv@v1
requirements.txt
GHSA-vfmq-68hx-4jfw
lxml@4.9.2 · osv@v1
requirements.txt
PYSEC-2026-87
lxml@4.9.2 · 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
GHSA-58cw-g322-p94v
mistune@3.0.2 · osv@v1
requirements.txt
GHSA-8g87-j6q8-g93x
mistune@3.0.2 · osv@v1
requirements.txt
GHSA-8mp2-v27r-99xp
mistune@3.0.2 · osv@v1
requirements.txt
GHSA-qcq2-496w-v96p
mistune@3.0.2 · osv@v1
requirements.txt
GHSA-v87v-83h2-53w7
mistune@3.0.2 · osv@v1
requirements.txt
PYSEC-2026-168
mistune@3.0.2 · osv@v1
requirements.txt
GHSA-3qhf-m339-9g5v
mcp@1.9.1 · osv@v1
requirements.txt
GHSA-9h52-p55h-vw2f
mcp@1.9.1 · osv@v1
requirements.txt
GHSA-j975-95f5-7wqh
mcp@1.9.1 · osv@v1
requirements.txt
PYSEC-2026-1616
mcp@1.9.1 · osv@v1
requirements.txt
PYSEC-2026-1617
mcp@1.9.1 · osv@v1
requirements.txt
PYSEC-2026-1618
mcp@1.9.1 · osv@v1
requirements.txt
GHSA-2jv5-9r88-3w3p
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-59g5-xgcq-4qw3
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-5rvq-cxj2-64vf
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-6jv3-5f52-599m
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-mj87-hwqh-73pj
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-pp6c-gr5w-3c5g
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-v9pg-7xvm-68hf
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-vffw-93wf-4j4q
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-wp53-j4wj-2cfg
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-1850
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-1851
python-multipart@0.0.6 · osv@v1
requirements.txt
PYSEC-2026-1852
python-multipart@0.0.6 · osv@v1
requirements.txt
GHSA-5wmx-573v-2qwq
markdown@3.5.1 · osv@v1
requirements.txt
PYSEC-2026-89
markdown@3.5.1 · 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/assafelovic-gpt-researcher/trust.
Common questions
- Is gpt-researcher maintained?
- GraphCanon rates gpt-researcher "Active" (82% maintenance signal from public GitHub metadata, computed 1w). Last push was 21 days ago. 3 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is gpt-researcher safe to use?
- Last scanned 1mo (deps profile). Status: 63 low - 63 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 gpt-researcher as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is gpt-researcher a fork?
- No. gpt-researcher is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does gpt-researcher have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 63 low - 63 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 gpt-researcher 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 gpt-researcher?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for gpt-researcher. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for gpt-researcher?
- 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.