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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 7 days ago
Rank Trend
2026-06-012026-06-04
Activity & Reach
Stars
2.0k
Forks
190
Last Push
2026-05-28
7 days ago
Commits (4 wk)
1?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
64
Rank Change
▼10
was #130
Analysis
HVTrust Dimensions
53.8 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
9.8 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.2 / 17
MaintenanceFreshness and commits
12.1 / 20
AdoptionStars and downloads
7.9 / 20
Activity Inputs
58.2 / 100
StarsRepository reach
19.8 / 30
FreshnessLast push recency
24.0 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
10.6 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.5 / 10
via deps.dev · OpenSSF
Signed Commits
59%
of last 100 commits verified
Binary-Artifacts9
Branch-Protection6
CI-Tests9
CII-Best-Practices0
Code-Review3
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained5
Packaging-1
Pinned-Dependencies2
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions10
Vulnerabilities0
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.5/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?
Actively maintained. The repository was pushed to within the last 7 day(s).
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?
59% 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Verl Agent?
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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
