---
title: "verl trust report"
type: "trust-report"
slug: "verl-project-verl"
canonical_url: "https://www.graphcanon.com/tools/verl-project-verl/trust"
computed_at: "2026-07-11T10:36:00.693Z"
maintenance_label: "Very active"
security_status: "findings"
---

# verl 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-01T11:24:51Z
- Releases (90d): 1
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 881221486
- Not a fork
- Owner type: Organization
- Computed at: 2026-07-11T10:36:00.693Z
- Methodology: github_public_v1

## Security scan

- Status: Findings present (0 critical, 0 high, 0 medium, 2 low) · last scan 2026-07-11T10:36:01.538Z

### Findings

- **low**: GHSA-rgxp-2hwp-jwgg (pyarrow@19.0.0 · requirements.txt)
- **low**: PYSEC-2026-113 (pyarrow@19.0.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 verl maintained?

GraphCanon rates verl "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 verl safe to use?

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

### Is verl a fork?

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

### Does verl have known security vulnerabilities?

Last scanned today (deps profile). Status: 2 low - 2 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 verl 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 verl?

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

### How does GraphCanon assess trust for verl?

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