---
title: "Applio trust report"
type: "trust-report"
slug: "iahispano-applio"
canonical_url: "https://www.graphcanon.com/tools/iahispano-applio/trust"
computed_at: "2026-07-11T12:07:50.852Z"
maintenance_label: "Very active"
security_status: "findings"
---

# Applio 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: 0
- Last release: 2026-06-28T13:21:11Z
- Releases (90d): 1
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 675859069
- Not a fork
- Owner type: Organization
- Computed at: 2026-07-11T12:07:50.852Z
- Methodology: github_public_v1

## Security scan

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

### Findings

- **low**: GHSA-4xh5-x5gv-qwph (pip@23.3 · requirements.txt)
- **low**: GHSA-58qw-9mgm-455v (pip@23.3 · requirements.txt)
- **low**: GHSA-6vgw-5pg2-w6jp (pip@23.3 · requirements.txt)
- **low**: GHSA-jp4c-xjxw-mgf9 (pip@23.3 · requirements.txt)
- **low**: GHSA-wf93-45jw-7689 (pip@23.3 · requirements.txt)
- **low**: PYSEC-2026-1795 (pip@23.3 · requirements.txt)
- **low**: PYSEC-2026-1796 (pip@23.3 · requirements.txt)
- **low**: PYSEC-2026-196 (pip@23.3 · requirements.txt)
- **low**: GHSA-887c-mr87-cxwp (torch@2.7.1 · requirements.txt)
- **low**: GHSA-qfhq-4f3w-5fph (torch@2.7.1 · requirements.txt)
- **low**: GHSA-rrmf-rvhw-rf47 (torch@2.7.1 · requirements.txt)
- **low**: GHSA-vgrw-7cvw-pwgx (torch@2.7.1 · requirements.txt)
- **low**: PYSEC-2025-203 (torch@2.7.1 · requirements.txt)
- **low**: PYSEC-2025-204 (torch@2.7.1 · requirements.txt)
- **low**: PYSEC-2025-206 (torch@2.7.1 · requirements.txt)
- **low**: PYSEC-2026-139 (torch@2.7.1 · requirements.txt)
- **low**: PYSEC-2026-1970 (torch@2.7.1 · requirements.txt)
- **low**: GHSA-39mp-8hj3-5c49 (gradio@5.50.0 · requirements.txt)
- **low**: GHSA-7hp7-4p35-3cx2 (gradio@5.50.0 · requirements.txt)
- **low**: GHSA-h3h8-3v2v-rg7m (gradio@5.50.0 · requirements.txt)
- **low**: GHSA-jmh7-g254-2cq9 (gradio@5.50.0 · requirements.txt)
- **low**: GHSA-pfjf-5gxr-995x (gradio@5.50.0 · requirements.txt)
- **low**: PYSEC-2026-211 (gradio@5.50.0 · requirements.txt)
- **low**: PYSEC-2026-63 (gradio@5.50.0 · requirements.txt)
- **low**: PYSEC-2026-64 (gradio@5.50.0 · requirements.txt)
- **low**: PYSEC-2026-65 (gradio@5.50.0 · requirements.txt)
- **low**: PYSEC-2026-66 (gradio@5.50.0 · 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 Applio maintained?

GraphCanon rates Applio "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 0 days ago. 1 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is Applio 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 Applio as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is Applio a fork?

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

### Does Applio 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 Applio 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 Applio?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for Applio. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology).

### How does GraphCanon assess trust for Applio?

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/iahispano-applio/trust`](/api/graphcanon/tools/iahispano-applio/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/_