---
title: "upgini trust report"
type: "trust-report"
slug: "upgini-upgini"
canonical_url: "https://www.graphcanon.com/tools/upgini-upgini/trust"
computed_at: "2026-07-11T23:28:30.856Z"
maintenance_label: "Very active"
security_status: "findings"
---

# upgini trust report

_Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and optional dependency [security scans](/glossary/trust-and-signals/security-scan). Not a security guarantee._

## Maintenance

- Label: Very active (96% recency signal)
- Days since last push: 4
- Last release: 2024-09-04T17:23:34Z
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 436402751
- Not a fork
- Owner type: Organization
- Computed at: 2026-07-11T23:28:30.856Z
- Methodology: github_public_v1

## Security scan

- Status: Findings present (0 critical, 0 high, 0 medium, 27 low) · last scan 2026-07-11T23:28:31.488Z

### Findings

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

## Method and caveats

These are heuristics from public GitHub data and optional dependency scans, sourced and dated. 
"No criticals found on 2026-07-11" is not a guarantee of safety.
See the full methodology: [/trust-methodology](/trust-methodology.md).

## 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](/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](/trust-methodology) for full scope and limits.

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/tools/upgini-upgini/trust`](/api/graphcanon/tools/upgini-upgini/trust)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_