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 5d · GitHub synced 5d

Maintenance

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

Dormant18% signal

last push 708d ago

+1 stars (30d) · -1 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

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

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
40
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)

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

Common questions

Is notion-qa maintained?
GraphCanon rates notion-qa "Dormant" (18% maintenance signal from public GitHub metadata, computed 5d). Last push was 708 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is notion-qa safe to use?
Last scanned 1mo (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 1mo (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 5d (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.

Was this helpful?

Anonymous feedback helps us improve pages and translations.