GraphCanon
Home/upgini/Trust report

Trust and health report

upgini - trust report

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

GraphCanon updated today · GitHub synced today

Maintenance

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

Very active96% signal

last push 4d ago · last release 1y

Provenance

Repository identity and fork provenance (github_public_v1).

Security scan

Dependency advisory security scan when a lockfile is present. Not a full code audit.

Status
27 low
Last scan
today
Scanner
osv@v1

Findings

GHSA-9hjg-9r4m-mvj7
requests@2.8.0 · requirements.txt
GHSA-9wx4-h78v-vm56
requests@2.8.0 · requirements.txt
GHSA-gc5v-m9x4-r6x2
requests@2.8.0 · requirements.txt
GHSA-j8r2-6x86-q33q
requests@2.8.0 · requirements.txt
GHSA-x84v-xcm2-53pg
requests@2.8.0 · requirements.txt
PYSEC-2018-28
requests@2.8.0 · requirements.txt
PYSEC-2023-74
requests@2.8.0 · requirements.txt
PYSEC-2026-1872
requests@2.8.0 · requirements.txt
PYSEC-2026-1873
requests@2.8.0 · requirements.txt
GHSA-6p56-wp2h-9hxr
numpy@1.19.0 · requirements.txt
GHSA-fpfv-jqm9-f5jm
numpy@1.19.0 · requirements.txt
PYSEC-2021-856
numpy@1.19.0 · requirements.txt
GHSA-jw8x-6495-233v
scikit-learn@1.3.0 · requirements.txt
PYSEC-2024-110
scikit-learn@1.3.0 · requirements.txt
GHSA-752w-5fwx-jx9f
pyjwt@2.8.0 · requirements.txt
GHSA-993g-76c3-p5m4
pyjwt@2.8.0 · requirements.txt
GHSA-fhv5-28vv-h8m8
pyjwt@2.8.0 · requirements.txt
GHSA-w7vc-732c-9m39
pyjwt@2.8.0 · requirements.txt
GHSA-xgmm-8j9v-c9wx
pyjwt@2.8.0 · requirements.txt
PYSEC-2025-183
pyjwt@2.8.0 · requirements.txt
PYSEC-2026-120
pyjwt@2.8.0 · requirements.txt
PYSEC-2026-175
pyjwt@2.8.0 · requirements.txt
PYSEC-2026-177
pyjwt@2.8.0 · requirements.txt
PYSEC-2026-178
pyjwt@2.8.0 · requirements.txt
PYSEC-2026-179
pyjwt@2.8.0 · requirements.txt
GHSA-jj5c-hhrg-vv5h
xhtml2pdf@0.2.11 · requirements.txt
PYSEC-2026-2056
xhtml2pdf@0.2.11 · requirements.txt

Method and caveats:these are sourced, dated heuristics from public GitHub data and optional dependency scans. A status like "no criticals found on 2026-07-11" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/upgini-upgini/trust.

Common questions

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