How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-06 18:03 UTC·Repo last pushed 2 days ago
Activity & Reach
Stars
2.3k
Forks
235
Last Push
2026-06-04
2 days ago
Commits (4 wk)
0?
Downloads (7d)
691
pypi
HN mentions (30d)
—
Open Issues
22
Rank Change
NEW
Analysis
HVTrust Dimensions
32.0 / 100 · 67.0% confidence
Safety / IntegrityOSSF, provenance, signatures
5.0 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
11.9 / 20
AdoptionStars and downloads
11.8 / 20
Activity Inputs
55.8 / 100
StarsRepository reach
20.1 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
11.0 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
100%
of last 100 commits verified
Is Lagent safe?
Public trust evidence for Lagent 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 Lagent publish package provenance?
No published build provenance is currently detected for Lagent. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Lagent have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Lagent. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Lagent actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Lagent use?
Lagent ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Lagent's commits signed?
100% of the last 100 commits to Lagent 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
HVTrust currently does not score runtime-trust fields yet. This public view shows a compact runtime snapshot from repo docs and manifests. An experimental ranking preview is available in Score Lab →, and progress is tracked on the roadmap →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
OpenAI
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
2 tags
Broad capability areas detected.
code
search
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
MCP support live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain Lagent?
HVTrust scores Lagent 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.
