Home/LLM-As-Chatbot/Trust report

Trust and health report

LLM-As-Chatbot - trust report

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

GraphCanon updated 3w · GitHub synced 3w

Maintenance

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

Dormant18% signal

last push 985d ago

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 607233462
  • Not a fork
  • Personal account
  • Computed 3w

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
9
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-7gcm-g887-7qv7
protobuf@3.20.* · osv@v1
requirements.txt
GHSA-8gq9-2x98-w8hf
protobuf@3.20.* · osv@v1
requirements.txt
GHSA-8qvm-5x2c-j2w7
protobuf@3.20.* · osv@v1
requirements.txt
GHSA-jwvw-v7c5-m82h
protobuf@3.20.* · osv@v1
requirements.txt
PYSEC-2017-65
protobuf@3.20.* · osv@v1
requirements.txt
PYSEC-2022-48
protobuf@3.20.* · osv@v1
requirements.txt
PYSEC-2026-1805
protobuf@3.20.* · osv@v1
requirements.txt
PYSEC-2026-1806
protobuf@3.20.* · osv@v1
requirements.txt
PYSEC-2026-899
protobuf@3.20.* · 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/deep-diver-llm-as-chatbot/trust.

Common questions

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