GraphCanon
Home/notion-qa/Trust report

Trust and health report

notion-qa - 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 673d ago

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 562678926
  • Not a fork
  • Personal account
  • Computed today

Security scan

Dependency advisory security scan when a lockfile is present. Not a full code audit.

Status
11 critical, 4 high, 3 medium, 22 low
Last scan
today
Scanner
osv@v1

Findings

langchain arbitrary code execution vulnerability
langchain@0.0.170 · CVE-2023-36258 · requirements.txt
LangSmith SDK: Public prompt pull deserializes untrusted manifests without trust boundary warning
langchain@0.0.170 · CVE-2026-45134 · requirements.txt
Denial of service in langchain-community
langchain@0.0.170 · CVE-2024-2965 · requirements.txt
Langchain SQL Injection vulnerability
langchain@0.0.170 · CVE-2024-8309 · requirements.txt
langchain vulnerable to arbitrary code execution
langchain@0.0.170 · CVE-2023-36188 · requirements.txt
LangChain Server Side Request Forgery vulnerability
langchain@0.0.170 · CVE-2023-46229 · requirements.txt
Langchain vulnerable to arbitrary code execution
langchain@0.0.170 · CVE-2023-34541 · requirements.txt
Langchain Server-Side Request Forgery vulnerability
langchain@0.0.170 · CVE-2023-32786 · requirements.txt
langchain vulnerable to arbitrary code execution
langchain@0.0.170 · CVE-2023-36281 · requirements.txt
langchain SQL Injection vulnerability
langchain@0.0.170 · CVE-2023-36189 · requirements.txt
Langchain SQL Injection vulnerability
langchain@0.0.170 · CVE-2023-32785 · requirements.txt
LangChain vulnerable to arbitrary code execution
langchain@0.0.170 · CVE-2023-38896 · requirements.txt
Langchain vulnerable to arbitrary code execution via the evaluate function in the numexpr library
langchain@0.0.170 · CVE-2023-39631 · requirements.txt
LangChain vulnerable to arbitrary code execution
langchain@0.0.170 · CVE-2023-38860 · requirements.txt
LangChain: Path traversal and sandbox escape in LangChain file-search middleware and loaders
langchain@0.0.170 · CVE-2026-55443 · requirements.txt
langchain Code Injection vulnerability
langchain@0.0.170 · CVE-2023-36095 · requirements.txt
LangChain directory traversal vulnerability
langchain@0.0.170 · CVE-2024-28088 · requirements.txt
langchain Server-Side Request Forgery vulnerability
langchain@0.0.170 · CVE-2024-0243 · requirements.txt
LangChain vulnerable to arbitrary code execution
langchain@0.0.170 · CVE-2023-39659 · requirements.txt
langchain vulnerable to path traversal
langchain@0.0.170 · CVE-2024-3571 · requirements.txt
Langchain OS Command Injection vulnerability
langchain@0.0.170 · CVE-2023-34540 · requirements.txt
PYSEC-2023-109
langchain@0.0.170 · CVE-2023-36188 · requirements.txt
PYSEC-2023-110
langchain@0.0.170 · CVE-2023-36189 · requirements.txt
PYSEC-2023-138
langchain@0.0.170 · CVE-2023-36095 · requirements.txt
PYSEC-2023-145
langchain@0.0.170 · CVE-2023-38860 · requirements.txt
PYSEC-2023-146
langchain@0.0.170 · CVE-2023-38896 · requirements.txt
PYSEC-2023-147
langchain@0.0.170 · CVE-2023-39659 · requirements.txt
PYSEC-2023-151
langchain@0.0.170 · CVE-2023-36281 · requirements.txt
PYSEC-2023-162
langchain@0.0.170 · CVE-2023-39631 · requirements.txt
PYSEC-2023-205
langchain@0.0.170 · CVE-2023-46229 · requirements.txt
PYSEC-2023-91
langchain@0.0.170 · CVE-2023-34540 · requirements.txt
PYSEC-2023-92
langchain@0.0.170 · CVE-2023-34541 · requirements.txt
PYSEC-2023-98
langchain@0.0.170 · CVE-2023-36258 · requirements.txt
PYSEC-2024-118
langchain@0.0.170 · CVE-2024-2965 · requirements.txt
PYSEC-2024-43
langchain@0.0.170 · CVE-2024-28088 · requirements.txt
Langchain SQL Injection vulnerability
langchain@0.0.170 · CVE-2024-8309 · requirements.txt
Langchain Server-Side Request Forgery vulnerability
langchain@0.0.170 · CVE-2023-32786 · requirements.txt
langchain Server-Side Request Forgery vulnerability
langchain@0.0.170 · CVE-2024-0243 · requirements.txt
langchain vulnerable to path traversal
langchain@0.0.170 · CVE-2024-3571 · requirements.txt
Langchain SQL Injection vulnerability
langchain@0.0.170 · CVE-2023-32785 · 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/hwchase17-notion-qa/trust.

Common questions

Is notion-qa maintained?
GraphCanon rates notion-qa "Dormant" (18% maintenance signal from public GitHub metadata, computed today). 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 today (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 today (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 today (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.
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 for full scope and limits.