Trust and health report
rags - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 1d · GitHub synced 1d
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Dormant18% signal
last push 865d ago
+6 stars (30d) · -1 open issues (30d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 719455172
- Not a fork
- Verified publisher: organization account
- Computed 1d
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
- 38
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-2jxw-4hm4-6w87
llama-index@0.9.7 · osv@v1
requirements.txt
GHSA-2xxc-73fv-36f7
llama-index@0.9.7 · osv@v1
requirements.txt
GHSA-5hq9-5r78-2gjh
llama-index@0.9.7 · osv@v1
requirements.txt
GHSA-jmgm-gx32-vp4w
llama-index@0.9.7 · osv@v1
requirements.txt
GHSA-jvpf-xf32-2w4q
llama-index@0.9.7 · osv@v1
requirements.txt
GHSA-pw38-xv9x-h8ch
llama-index@0.9.7 · osv@v1
requirements.txt
GHSA-rg9h-vx28-xxp5
llama-index@0.9.7 · osv@v1
requirements.txt
GHSA-v3c8-3pr6-gr7p
llama-index@0.9.7 · osv@v1
requirements.txt
PYSEC-2024-12
llama-index@0.9.7 · osv@v1
requirements.txt
PYSEC-2024-192
llama-index@0.9.7 · osv@v1
requirements.txt
PYSEC-2025-11
llama-index@0.9.7 · osv@v1
requirements.txt
PYSEC-2026-1555
llama-index@0.9.7 · osv@v1
requirements.txt
PYSEC-2026-1556
llama-index@0.9.7 · osv@v1
requirements.txt
PYSEC-2026-394
llama-index@0.9.7 · osv@v1
requirements.txt
PYSEC-2026-85
llama-index@0.9.7 · osv@v1
requirements.txt
PYSEC-2026-86
llama-index@0.9.7 · osv@v1
requirements.txt
GHSA-297x-2qf3-jrj3
llama-hub@0.0.44 · osv@v1
requirements.txt
PYSEC-2026-393
llama-hub@0.0.44 · osv@v1
requirements.txt
GHSA-3644-q5cj-c5c7
langchain@0.0.305 · osv@v1
requirements.txt
GHSA-3hjh-jh2h-vrg6
langchain@0.0.305 · osv@v1
requirements.txt
GHSA-45pg-36p6-83v9
langchain@0.0.305 · osv@v1
requirements.txt
GHSA-655w-fm8m-m478
langchain@0.0.305 · osv@v1
requirements.txt
GHSA-6h8p-4hx9-w66c
langchain@0.0.305 · osv@v1
requirements.txt
GHSA-7gfq-f96f-g85j
langchain@0.0.305 · osv@v1
requirements.txt
GHSA-f73w-4m7g-ch9x
langchain@0.0.305 · osv@v1
requirements.txt
GHSA-gr75-jv2w-4656
langchain@0.0.305 · osv@v1
requirements.txt
GHSA-h59x-p739-982c
langchain@0.0.305 · osv@v1
requirements.txt
GHSA-h9j7-5xvc-qhg5
langchain@0.0.305 · osv@v1
requirements.txt
GHSA-prgp-w7vf-ch62
langchain@0.0.305 · osv@v1
requirements.txt
GHSA-rgp8-pm28-3759
langchain@0.0.305 · osv@v1
requirements.txt
PYSEC-2023-162
langchain@0.0.305 · osv@v1
requirements.txt
PYSEC-2023-205
langchain@0.0.305 · osv@v1
requirements.txt
PYSEC-2024-118
langchain@0.0.305 · osv@v1
requirements.txt
PYSEC-2024-43
langchain@0.0.305 · osv@v1
requirements.txt
PYSEC-2026-1507
langchain@0.0.305 · osv@v1
requirements.txt
PYSEC-2026-1508
langchain@0.0.305 · osv@v1
requirements.txt
PYSEC-2026-1509
langchain@0.0.305 · osv@v1
requirements.txt
PYSEC-2026-1510
langchain@0.0.305 · 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/run-llama-rags/trust.
Common questions
- Is rags maintained?
- GraphCanon rates rags "Dormant" (18% maintenance signal from public GitHub metadata, computed 1d). Last push was 865 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is rags safe to use?
- Last scanned 1mo (deps profile). Status: 38 low - 38 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 rags as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is rags a fork?
- No. rags is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does rags have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 38 low - 38 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 rags 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 rags?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for rags. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for rags?
- 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.