Is Verl Agent safe to use?

Verl Agent has an HVTrust score of 53.6/100 (Grade C), ranked #589 of 1316 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Verl Agent?

Verl Agent scores 53.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.3k GitHub stars and is categorized under Agent Frameworks.

Verl Agent

langfengQ/verl-agent

verl-agent is an extension of veRL, designed for training LLM/VLM agents via RL. verl-agent is also the official code fo

Agent Frameworks Python Grade C Listed Apache-2.0

53.6/100

Rank #589 of 1316

Compare Verl Agent

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-06-09 · 85d ago

Recent change

Rank +4

Is Verl Agent safe? Verl Agent scores 53.6/100 (Grade C), ranked #589 of 1316 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.3/10; 60% of recent commits are signed; last pushed 2026-06-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#68 SandBase Harness — 54.4 (C) → #69 LazyLLM — 54.0 (C) → #71 Agently — 53.1 (C) → #72 ouroboros — 53.0 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-01

Rank Moved

Rank dropped 19 spots (#564 → #583)

2026-08-31

Rank Moved

Rank dropped 27 spots (#537 → #564)

2026-08-29

Rank Moved

Rank dropped 31 spots (#504 → #535)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.3/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Refresh maintenance signals The repo was last pushed 85 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Verl Agent View Agent Frameworks Report missing data

44.3

Activity sub-score · out of 100

#70

In Agent Frameworks

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-02

Activity & Reach

Stars

2.3k

Forks

219

Last Push

2026-06-09

85 days ago

Commits (4 wk)

Downloads (7d)

22,847

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼6

was #583

Analysis

HVTrust Dimensions vs Agent Frameworks

53.6 / 100 · 100.0% confidence

Verl Agent Agent Frameworks average (119 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

9.6 / 25

0.5 above avg 9.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

13.0 / 17

0.8 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

6.3 / 20

7.8 below avg 14.1

AdoptionLog-scaled stars · package downloads

13.9 / 20

2.6 above avg 11.3

Activity Inputs

44.3 / 100

StarsRepository reach

20.1 / 30

FreshnessLast push recency

13.2 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.3 / 10

OpenSSF Scorecard · scanned Aug 26, 2026

Signed Commits

60%

of last 100 commits verified

Binary-Artifacts 9

Branch-Protection 6

CI-Tests 7

CII-Best-Practices 0

Code-Review 3

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 4

Packaging -1

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0

Is Verl Agent safe?

Public trust evidence for Verl Agent is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Verl Agent publish package provenance?

No published build provenance is currently detected for Verl Agent. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Verl Agent have an OpenSSF Scorecard?

Verl Agent has an OpenSSF Scorecard score of 5.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Verl Agent actively maintained?

Slowing down. Last push was 85 days ago — keep an eye on whether activity resumes.

What license does Verl Agent use?

Verl Agent ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Verl Agent's commits signed?

60% of the last 100 commits to Verl Agent are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Verl Agent's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-07

Drift Warning Cleared

Provenance drift warning cleared (now: not_applicable)

2026-06-05

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

Maintain Verl Agent?

For maintainers

HVTrust scores Verl Agent from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-01

Rank Moved

Rank dropped 19 spots (#564 → #583)

2026-08-31

Rank Moved

Rank dropped 27 spots (#537 → #564)

2026-08-29

Rank Moved

Rank dropped 31 spots (#504 → #535)

2026-08-27

Rank Moved

Rank dropped 13 spots (#489 → #502)

2026-08-26

Rank Moved

Rank dropped 56 spots (#433 → #489)

2026-08-24

Rank Moved

Rank dropped 18 spots (#416 → #434)

2026-08-22

Rank Moved

Rank rose 17 spots (#435 → #418)

2026-08-19

Rank Moved

Rank dropped 13 spots (#418 → #431)

2026-08-17

Rank Moved

Rank rose 11 spots (#428 → #417)

2026-08-16

Rank Moved

Rank dropped 10 spots (#418 → #428)

2026-08-13

Rank Moved

Rank dropped 14 spots (#397 → #411)

2026-08-12

Rank Moved

Rank rose 10 spots (#407 → #397)

2026-08-10

Rank Moved

Rank dropped 16 spots (#389 → #405)

2026-08-08

Rank Moved

Rank dropped 94 spots (#291 → #385)

2026-08-07

Drift Warning Cleared

Provenance drift warning cleared (now: not_applicable)

2026-07-29

Rank Moved

Rank dropped 10 spots (#313 → #323)

2026-07-16

Grade Changed

Trust grade C → D

2026-07-15

Rank Moved

Rank dropped 22 spots (#279 → #301)

2026-07-14

Rank Moved

Rank dropped 14 spots (#265 → #279)

2026-07-13

Rank Moved

Rank dropped 32 spots (#233 → #265)

2026-06-24

Rank Moved

Rank dropped 15 spots (#156 → #171)

2026-06-05

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

GitHub → PyPI: verl

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/verl-agent.svg)](https://hvtracker.net/agents/verl-agent)
            
HTML:
            <a href="https://hvtracker.net/agents/verl-agent"><img src="https://hvtracker.net/badge/verl-agent.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON