Home/llm-universe/Trust report

Trust and health report

llm-universe - trust report

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

GraphCanon updated 3d · GitHub synced 3d · 25 views this month

Maintenance

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

Active82% signal

last push 20d ago · last release 2y

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

Provenance

Repository identity and fork provenance (github_public_v1).

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
27
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-3644-q5cj-c5c7
langchain@0.3.0 · osv@v1
requirements.txt
GHSA-gr75-jv2w-4656
langchain@0.3.0 · osv@v1
requirements.txt
GHSA-pc6w-59fv-rh23
langchain-community@0.3.0 · osv@v1
requirements.txt
PYSEC-2026-1515
langchain-community@0.3.0 · osv@v1
requirements.txt
GHSA-fv5p-p927-qmxr
langchain-text-splitters@0.3.0 · osv@v1
requirements.txt
GHSA-m42m-m8cr-8m58
langchain-text-splitters@0.3.0 · osv@v1
requirements.txt
PYSEC-2026-1520
langchain-text-splitters@0.3.0 · osv@v1
requirements.txt
PYSEC-2026-77
langchain-text-splitters@0.3.0 · osv@v1
requirements.txt
GHSA-2g6r-c272-w58r
langchain-core@0.3.0 · osv@v1
requirements.txt
GHSA-5chr-fjjv-38qv
langchain-core@0.3.0 · osv@v1
requirements.txt
GHSA-6qv9-48xg-fc7f
langchain-core@0.3.0 · osv@v1
requirements.txt
GHSA-926x-3r5x-gfhw
langchain-core@0.3.0 · osv@v1
requirements.txt
GHSA-c67j-w6g6-q2cm
langchain-core@0.3.0 · osv@v1
requirements.txt
GHSA-pjwx-r37v-7724
langchain-core@0.3.0 · osv@v1
requirements.txt
GHSA-qh6h-p6c9-ff54
langchain-core@0.3.0 · osv@v1
requirements.txt
PYSEC-2026-1517
langchain-core@0.3.0 · osv@v1
requirements.txt
PYSEC-2026-1518
langchain-core@0.3.0 · osv@v1
requirements.txt
PYSEC-2026-373
langchain-core@0.3.0 · osv@v1
requirements.txt
GHSA-r7w7-9xr2-qq2r
langchain-openai@0.2.0 · osv@v1
requirements.txt
PYSEC-2026-76
langchain-openai@0.2.0 · osv@v1
requirements.txt
GHSA-mf9w-mj56-hr94
python-dotenv@1.0.1 · osv@v1
requirements.txt
GHSA-gm8q-m8mv-jj5m
unstructured@0.16.23 · osv@v1
requirements.txt
PYSEC-2026-558
unstructured@0.16.23 · osv@v1
requirements.txt
GHSA-5wmx-573v-2qwq
markdown@3.7 · osv@v1
requirements.txt
PYSEC-2026-89
markdown@3.7 · osv@v1
requirements.txt
GHSA-7p48-42j8-8846
streamlit@1.43.0 · osv@v1
requirements.txt
PYSEC-2026-212
streamlit@1.43.0 · 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/datawhalechina-llm-universe/trust.

Common questions

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