updated 2026-11-10 04:07 UTC

Lobehub

Repository Website

🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.

Agent Skills TypeScript Listed NOASSERTION Source-available

CRITICAL3 unfixed advisories in the release you'd install

LobeHub: Unauthenticated SSRF in `/webapi/proxy`. It affects @lobehub/lobehub 2.1.26, the latest published release.

GHSA-xmwj-c75x-6346 · CVE-2026-54157 · published 2026-06-16 · all 3

Is Lobehub safe? Promising trust profile, but some evidence still deserves review. 3 published advisories affect its latest release.

OSSF Scorecard 4.3 / 10
Provenance None
Signed commits 100%
Last push today
Advisories 3, worst critical
Compare Lobehub

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Lobehub scores 64.9/100 (Grade C), ranked #64 of 384 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 4.3/10; 100% of recent commits are signed; 3 published advisories affect its latest release (@lobehub/lobehub); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Known advisories

Published advisories (from OSV) that affect the release you'd install today: @lobehub/lobehub 2.1.26. An unfixed critical advisory caps the HVTrust score at 64.9 (Grade C) and a high one at 79.9 (Grade B), until a fixed release ships; moderate, low and unrated ones are shown, not scored. Checked 2026-11-09.

  • CRITICAL LobeHub: Unauthenticated SSRF in `/webapi/proxy` GHSA-xmwj-c75x-6346 · CVE-2026-54157 · @lobehub/lobehub 2.1.26 · published 2026-06-16
  • MODERATE LobeHub has a Cross-Site Scripting issue that escalates to Remote Code Execution GHSA-xq4x-622m-q8fq · CVE-2026-42045 · @lobehub/lobehub 2.1.26 · published 2026-05-05
  • MODERATE LobeHub: Unauthenticated authentication bypass on `webapi` routes via forgeable `X-lobe-chat-auth` header GHSA-5mwj-v5jw-5c97 · CVE-2026-39411 · @lobehub/lobehub 2.1.26 · published 2026-04-08

How Lobehub could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Lobehub and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Signed

    github.com/lobehub/lobehub, NOASSERTION, last pushed 2026-11-10. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.3/10 (scanned Nov 6, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow0
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 2
    Contributors 10
    Dangerous-Workflow 0
    Dependency-Update-Tool 10
    Fuzzing 0
    License 9
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 9
    Security-Policy 4
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Not linked

    • npm @lobehub/lobehub Source link points to lobehub/lobe-chat, same owner No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today 3 advisories

    Latest release checked: @lobehub/lobehub 2.1.26. 3 published advisories affect it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-04 OSSF Scorecard: 4.9/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Lobehub’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Lobehub compares in Agent Skills

  1. #62 Text To Cad 65.1 +0.2
  2. #63 Voyager 64.9 ±0
  3. #64 Lobehub 64.9 this agent
  4. #65 Universal Modder 64.8 −0.1
  5. #66 Deepchat 64.5 −0.4

Bars show each HVTrust score; the tick marks Lobehub’s 64.9.

Where the 64.9 comes from

HVTrust dimensions vs the Agent Skills average

64.9 / 100 · 100.0% confidence

Lobehub Agent Skills average (384 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.4 / 25
2.2 above avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.0 above avg 14.0
AdoptionLog-scaled stars · package downloads
16.0 / 20
6.9 above avg 9.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.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.
Compare with another agent
View Agent Skills Report missing data
99.2
Activity sub-score · out of 100
#64
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 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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
84.6k
Forks
16.2k
Last Push
2026-11-10
today
Commits (4 wk)
1384
Downloads (7d)
1,328
npm
HN mentions (30d)
—
Open Issues
460
Rank Change
▼1
was #63

Analysis

Activity Inputs

99.2 / 100
StarsRepository reach
29.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
19.6 / 20

Common questions about Lobehub

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.
Lobehub has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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?
Lobehub has an OpenSSF Scorecard score of 4.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 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
How this surface has changed

Detected changes to Lobehub'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-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI, Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

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
Rank 12HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1Surface 1
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI, Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 170 spots (#216 → #46)
2026-09-23
HVTrust Changed
HVTrust up 32.6pts (34.1 → 66.7)
2026-09-22
Newly Listed
First tracked at rank #216
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-05
Rank Moved
Rank dropped 10 spots (#23 → #33)
2026-09-04
Scorecard Added
OSSF Scorecard: 4.9/10
2026-09-04
Grade Changed
Trust grade D → B
2026-09-04
Rank Moved
Rank rose 221 spots (#244 → #23)
2026-09-04
HVTrust Changed
HVTrust up 29.9pts (37.8 → 67.7)
2026-09-03
Rank Moved
Rank dropped 15 spots (#229 → #244)
2026-09-02
Rank Moved
Rank dropped 12 spots (#217 → #229)
2026-09-01
Rank Moved
Rank dropped 13 spots (#204 → #217)
2026-08-31
Rank Moved
Rank dropped 16 spots (#188 → #204)
2026-08-30
Rank Moved
Rank dropped 32 spots (#156 → #188)
2026-08-29
Rank Moved
Rank dropped 36 spots (#120 → #156)
2026-08-28
Rank Moved
Rank dropped 26 spots (#94 → #120)
2026-08-27
Rank Moved
Rank dropped 22 spots (#72 → #94)
2026-08-26
Rank Moved
Rank dropped 50 spots (#22 → #72)
GitHub → Website → npm: @lobehub/lobehub

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.9 Grade C
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON