Is LazyLLM safe to use?

LazyLLM has an HVTrust score of 54.0/100 (Grade C), ranked #287 of 468 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for LazyLLM?

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

LazyLLM

LazyAGI/LazyLLM

Easiest and laziest way for building multi-agent LLMs applications.

Agent Frameworks Python Grade C Listed Apache-2.0

54.0/100

Rank #287 of 468

Compare LazyLLM

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 C · 2/5 signals

Last push

2026-08-06 · 0d ago

Recent change

No recent signal change

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

Ranked neighbours in Agent Frameworks

#58 Skales — 54.5 (C) → #59 OpenEvolve — 54.2 (C) → #61 ControlFlow — 53.9 (C) → #62 agentUniverse — 53.4 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-07-15

Rank Moved

Rank dropped 16 spots (#258 → #274)

2026-07-14

Rank Moved

Rank dropped 14 spots (#244 → #258)

2026-07-13

Rank Moved

Rank dropped 26 spots (#218 → #244)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.1/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.

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

79.1

Activity sub-score · out of 100

#60

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars

3.9k

Forks

402

Last Push

2026-08-06

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #288

Analysis

HVTrust Dimensions vs Agent Frameworks

54.0 / 100 · 100.0% confidence

LazyLLM Agent Frameworks average (103 agents)

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

8.9 / 25

in line with avg 9.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

11.1 / 17

0.9 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

18.6 / 20

4.0 above avg 14.6

AdoptionLog-scaled stars · package downloads

8.6 / 20

3.3 below avg 11.9

Activity Inputs

79.1 / 100

StarsRepository reach

21.5 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

20.5 / 25

CommunityFork signal

12.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.1 / 10

OpenSSF Scorecard · scanned Aug 5, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 0

CII-Best-Practices 0

Code-Review 7

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is LazyLLM safe?

Public trust evidence for LazyLLM 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 LazyLLM publish package provenance?

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

Does LazyLLM have an OpenSSF Scorecard?

LazyLLM has an OpenSSF Scorecard score of 3.1/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 LazyLLM actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does LazyLLM use?

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

Are LazyLLM's commits signed?

100% of the last 100 commits to LazyLLM 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

high confidence

4 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Extensions

Extension based plugin/integration surface detected.

code
database
search

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

Maintain LazyLLM?

For maintainers

HVTrust scores LazyLLM 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-07-15

Rank Moved

Rank dropped 16 spots (#258 → #274)

2026-07-14

Rank Moved

Rank dropped 14 spots (#244 → #258)

2026-07-13

Rank Moved

Rank dropped 26 spots (#218 → #244)

2026-06-24

Rank Moved

Rank dropped 22 spots (#169 → #191)

2026-06-23

Scorecard Added

OSSF Scorecard: 3.1/10

2026-06-23

Grade Changed

Trust grade D → C

2026-06-23

Rank Moved

Rank rose 93 spots (#262 → #169)

2026-06-23

HVTrust Changed

HVTrust up 32.6pts (25.4 → 58.0)

2026-06-21

Newly Listed

First tracked at rank #258

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

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