Is HippoRAG maintained?

GraphCanon rates HippoRAG "Active" (82% maintenance signal from public GitHub metadata, computed Sep 18, 2026). Last push was 14 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

Is HippoRAG safe to use?

Last scanned Sep 18, 2026 (deps profile). Status: 96 low - 96 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 HippoRAG as safe - review maintenance, provenance, and scan findings on this page before adopting.

No. HippoRAG is not flagged as a fork in GitHub metadata at the time of the last refresh.

Does HippoRAG have known security vulnerabilities?

Last scanned Sep 18, 2026 (deps profile). Status: 96 low - 96 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 HippoRAG trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Sep 18, 2026 (methodology github_public_v1).

What does GraphCanon never claim about HippoRAG?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for HippoRAG. Signals are sourced heuristics with explicit limits - see trust methodology (https://www.graphcanon.com/trust-methodology).

How does GraphCanon assess trust for HippoRAG?

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 (https://www.graphcanon.com/trust-methodology) for full scope and limits.

Home/HippoRAG/Trust report

Trust and health report

HippoRAG - trust report

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

GraphCanon updated Sep 20, 2026 · GitHub synced Sep 20, 2026

40views this month

Maintenance

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

Active82% signal

last push 14d ago · last release Feb 27, 2025

+110 stars (30d) · +2 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 805115184
Not a fork
Verified publisher: organization account
Computed Sep 18, 2026

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: Sep 18, 2026
Scanner: osv@v1
Stored findings: 96

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-4g5m-c9r5-49xf

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-4jcj-7x88-m979

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-4xpc-pv4p-pm3w

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-53mr-6c8q-9789

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-5jmr-gcrj-2c9q

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-69x8-hrgq-fjj8

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-6wvf-77m9-58rm

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-72m8-9m7m-h278

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-7488-6r32-c95q

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-c693-x898-5g4h

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-hx8v-g79f-8w5f

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-j37q-q7p9-vpwm

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-jjhc-v7c2-5hh6

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-m2v5-74w2-qhcj

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-mf52-j94g-746m

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-p897-vf7j-f5h8

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-qmf3-4767-5fg3

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-qrc4-49gv-mv9m

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-w2mh-qq9q-453x

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-wpfp-gwwc-vwq6

litellm@1.73.1 · osv@v1

requirements.txt

PYSEC-2026-2597

litellm@1.73.1 · osv@v1

requirements.txt

PYSEC-2026-2598

litellm@1.73.1 · osv@v1

requirements.txt

PYSEC-2026-2600

litellm@1.73.1 · osv@v1

requirements.txt

PYSEC-2026-3476

litellm@1.73.1 · osv@v1

requirements.txt

PYSEC-2026-3477

litellm@1.73.1 · osv@v1

requirements.txt

PYSEC-2026-3478

litellm@1.73.1 · osv@v1

requirements.txt

PYSEC-2026-3479

litellm@1.73.1 · osv@v1

requirements.txt

PYSEC-2026-3861

litellm@1.73.1 · osv@v1

requirements.txt

PYSEC-2026-388

litellm@1.73.1 · osv@v1

requirements.txt

PYSEC-2026-390

litellm@1.73.1 · osv@v1

requirements.txt

GHSA-3749-ghw9-m3mg

torch@2.5.1 · osv@v1

requirements.txt

GHSA-53q9-r3pm-6pq6

torch@2.5.1 · osv@v1

requirements.txt

GHSA-887c-mr87-cxwp

torch@2.5.1 · osv@v1

requirements.txt

GHSA-c678-jfcj-6jmf

torch@2.5.1 · osv@v1

requirements.txt

GHSA-f4hp-rmr7-r7v8

torch@2.5.1 · osv@v1

requirements.txt

GHSA-qfhq-4f3w-5fph

torch@2.5.1 · osv@v1

requirements.txt

GHSA-rrmf-rvhw-rf47

torch@2.5.1 · osv@v1

requirements.txt

GHSA-vgrw-7cvw-pwgx

torch@2.5.1 · osv@v1

requirements.txt

GHSA-x3gm-94wq-g975

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2025-191

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2025-198

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2025-203

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2025-204

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2025-205

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2025-206

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2025-207

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2025-208

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2025-209

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2025-41

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2026-139

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2026-1970

torch@2.5.1 · osv@v1

requirements.txt

PYSEC-2026-2286

torch@2.5.1 · osv@v1

requirements.txt

GHSA-29pf-2h5f-8g72

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-37mw-44qp-f5jm

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-4w7r-h757-3r74

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-59p9-h35m-wg4g

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-69w3-r845-3855

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-6rvg-6v2m-4j46

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-9356-575x-2w9m

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-fgcw-684q-jj6r

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-fpwr-67px-3qhx

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-hxxf-235m-72v3

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-jjph-296x-mrcr

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-phhr-52qp-3mj4

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-q2wp-rjmx-x6x9

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-qq3j-4f4f-9583

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-qxrp-vhvm-j765

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-rcv9-qm8p-9p6j

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-wrfc-pvp9-mr9g

transformers@4.45.2 · osv@v1

requirements.txt

GHSA-xrqw-3rrv-vx5w

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2024-227

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2024-228

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2024-229

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2025-211

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2025-212

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2025-213

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2025-214

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2025-215

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2025-216

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2025-217

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2025-218

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2025-40

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-1977

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-1980

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-1981

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-1982

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-1983

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-1984

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-1985

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-1986

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-1987

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-1988

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-2288

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-2289

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-2290

transformers@4.45.2 · osv@v1

requirements.txt

PYSEC-2026-3929

transformers@4.45.2 · 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/osu-nlp-group-hipporag/trust.

Common questions

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