--- title: "notion-qa trust report" type: "trust-report" slug: "hwchase17-notion-qa" canonical_url: "https://www.graphcanon.com/tools/hwchase17-notion-qa/trust" computed_at: "2026-07-11T10:50:44.590Z" maintenance_label: "Dormant" security_status: "findings" --- # notion-qa 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: 673 - Methodology: github_public_v1 ## Provenance - GitHub repo id: 562678926 - Not a fork - Owner type: User - Computed at: 2026-07-11T10:50:44.590Z - Methodology: github_public_v1 ## Security scan - Status: Findings present (11 critical, 4 high, 3 medium, 22 low) · last scan 2026-07-11T10:50:45.477Z ### Findings - **critical**: langchain arbitrary code execution vulnerability (langchain@0.0.170 · CVE-2023-36258 · requirements.txt) - **high**: LangSmith SDK: Public prompt pull deserializes untrusted manifests without trust boundary warning (langchain@0.0.170 · CVE-2026-45134 · requirements.txt) - **medium**: Denial of service in langchain-community (langchain@0.0.170 · CVE-2024-2965 · requirements.txt) - **low**: Langchain SQL Injection vulnerability (langchain@0.0.170 · CVE-2024-8309 · requirements.txt) - **critical**: langchain vulnerable to arbitrary code execution (langchain@0.0.170 · CVE-2023-36188 · requirements.txt) - **high**: LangChain Server Side Request Forgery vulnerability (langchain@0.0.170 · CVE-2023-46229 · requirements.txt) - **critical**: Langchain vulnerable to arbitrary code execution (langchain@0.0.170 · CVE-2023-34541 · requirements.txt) - **high**: Langchain Server-Side Request Forgery vulnerability (langchain@0.0.170 · CVE-2023-32786 · requirements.txt) - **critical**: langchain vulnerable to arbitrary code execution (langchain@0.0.170 · CVE-2023-36281 · requirements.txt) - **high**: langchain SQL Injection vulnerability (langchain@0.0.170 · CVE-2023-36189 · requirements.txt) - **critical**: Langchain SQL Injection vulnerability (langchain@0.0.170 · CVE-2023-32785 · requirements.txt) - **critical**: LangChain vulnerable to arbitrary code execution (langchain@0.0.170 · CVE-2023-38896 · requirements.txt) - **critical**: Langchain vulnerable to arbitrary code execution via the evaluate function in the numexpr library (langchain@0.0.170 · CVE-2023-39631 · requirements.txt) - **critical**: LangChain vulnerable to arbitrary code execution (langchain@0.0.170 · CVE-2023-38860 · requirements.txt) - **medium**: LangChain: Path traversal and sandbox escape in LangChain file-search middleware and loaders (langchain@0.0.170 · CVE-2026-55443 · requirements.txt) - **critical**: langchain Code Injection vulnerability (langchain@0.0.170 · CVE-2023-36095 · requirements.txt) - **low**: LangChain directory traversal vulnerability (langchain@0.0.170 · CVE-2024-28088 · requirements.txt) - **low**: langchain Server-Side Request Forgery vulnerability (langchain@0.0.170 · CVE-2024-0243 · requirements.txt) - **critical**: LangChain vulnerable to arbitrary code execution (langchain@0.0.170 · CVE-2023-39659 · requirements.txt) - **medium**: langchain vulnerable to path traversal (langchain@0.0.170 · CVE-2024-3571 · requirements.txt) - **critical**: Langchain OS Command Injection vulnerability (langchain@0.0.170 · CVE-2023-34540 · requirements.txt) - **low**: PYSEC-2023-109 (langchain@0.0.170 · CVE-2023-36188 · requirements.txt) - **low**: PYSEC-2023-110 (langchain@0.0.170 · CVE-2023-36189 · requirements.txt) - **low**: PYSEC-2023-138 (langchain@0.0.170 · CVE-2023-36095 · requirements.txt) - **low**: PYSEC-2023-145 (langchain@0.0.170 · CVE-2023-38860 · requirements.txt) - **low**: PYSEC-2023-146 (langchain@0.0.170 · CVE-2023-38896 · requirements.txt) - **low**: PYSEC-2023-147 (langchain@0.0.170 · CVE-2023-39659 · requirements.txt) - **low**: PYSEC-2023-151 (langchain@0.0.170 · CVE-2023-36281 · requirements.txt) - **low**: PYSEC-2023-162 (langchain@0.0.170 · CVE-2023-39631 · requirements.txt) - **low**: PYSEC-2023-205 (langchain@0.0.170 · CVE-2023-46229 · requirements.txt) - **low**: PYSEC-2023-91 (langchain@0.0.170 · CVE-2023-34540 · requirements.txt) - **low**: PYSEC-2023-92 (langchain@0.0.170 · CVE-2023-34541 · requirements.txt) - **low**: PYSEC-2023-98 (langchain@0.0.170 · CVE-2023-36258 · requirements.txt) - **low**: PYSEC-2024-118 (langchain@0.0.170 · CVE-2024-2965 · requirements.txt) - **low**: PYSEC-2024-43 (langchain@0.0.170 · CVE-2024-28088 · requirements.txt) - **low**: Langchain SQL Injection vulnerability (langchain@0.0.170 · CVE-2024-8309 · requirements.txt) - **low**: Langchain Server-Side Request Forgery vulnerability (langchain@0.0.170 · CVE-2023-32786 · requirements.txt) - **low**: langchain Server-Side Request Forgery vulnerability (langchain@0.0.170 · CVE-2024-0243 · requirements.txt) - **low**: langchain vulnerable to path traversal (langchain@0.0.170 · CVE-2024-3571 · requirements.txt) - **low**: Langchain SQL Injection vulnerability (langchain@0.0.170 · CVE-2023-32785 · 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 notion-qa maintained? GraphCanon rates notion-qa "Dormant" (18% maintenance signal from public GitHub metadata, computed 1d). Last push was 673 days ago. This is a recency heuristic, not a guarantee the project will stay maintained. ### Is notion-qa safe to use? Last scanned 1d (deps profile). Status: 11 critical, 4 high, 3 medium, 22 low - 11 critical, 4 high, 3 medium, 22 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 notion-qa as safe - review maintenance, provenance, and scan findings on this page before adopting. ### Is notion-qa a fork? No. notion-qa is not flagged as a fork in GitHub metadata at the time of the last refresh. ### Does notion-qa have known security vulnerabilities? Last scanned 1d (deps profile). Status: 11 critical, 4 high, 3 medium, 22 low - 11 critical, 4 high, 3 medium, 22 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 notion-qa trust report updated? Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 1d (methodology github_public_v1). ### What does GraphCanon never claim about notion-qa? We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for notion-qa. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology). ### How does GraphCanon assess trust for notion-qa? 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/hwchase17-notion-qa/trust`](/api/graphcanon/tools/hwchase17-notion-qa/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/_