updated 2026-08-12 05:02 UTC

Lobehub

lobehub/lobehub

🤯 LobeHub is your Chief Agent Operator, organizing your agents into 7×24 operations by hiring, scheduling, and reporting

Agent Skills TypeScript Grade D Listed NOASSERTION Source-available
38.4/100
Rank #17 of 148
Compare Lobehub

How does it stack up against its Agent Skills 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-12 · 0d ago
Recent change
New

Is Lobehub safe? Lobehub scores 38.4/100 (Grade D), ranked #17 of 148 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 100% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#15 Superpowers Zh — 40.9 (D) → #16 Memsearch — 39.3 (D) → #18 Skill Seekers — 37.8 (D) → #19 Nagisanzenin Engram — 37.2 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-11
Newly Listed
First tracked at rank #17
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 Lobehub View Agent Skills Report missing data
99.0
Activity sub-score · out of 100
#17
In Agent Skills

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. 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 →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
81.5k
Forks
15.8k
Last Push
2026-08-12
today
Commits (4 wk)
735
Downloads (7d)
487
npm
HN mentions (30d)
—
Open Issues
270
Rank Change
=
was #17

Analysis

HVTrust Dimensions vs Agent Skills

38.4 / 100 · 67.0% confidence

Lobehub Agent Skills average (148 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
2.3 above avg 2.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.5
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.9 above avg 15.1
AdoptionLog-scaled stars · package downloads
15.4 / 20
6.2 above avg 9.2

Activity Inputs

99.0 / 100
StarsRepository reach
29.5 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
19.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
100%
of last 100 commits verified

Is Lobehub safe?

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Lobehub may have internal security practices not visible through public signals.
Public trust evidence for Lobehub 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 Lobehub publish package provenance?
No published build provenance is currently detected for Lobehub. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Lobehub have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Lobehub. 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 Lobehub actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Lobehub use?
Lobehub ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Lobehub's commits signed?
100% of the last 100 commits to Lobehub 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
high confidence
Implemented
Lobehub appears to expose MCP server capabilities.
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
Declared
Declared plugin/integration surface detected.
  • browser
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Lobehub?

For maintainers

HVTrust scores Lobehub 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
Listed 1
2026-08-11
Newly Listed
First tracked at rank #17
GitHub → npm: @lobehub/lobehub

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 38.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/lobehub.svg)](https://hvtracker.net/agents/lobehub)
HTML:
<a href="https://hvtracker.net/agents/lobehub"><img src="https://hvtracker.net/badge/lobehub.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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