Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 07:30 UTC

lobu-ai / lobu

Open-source control plane and runtime for organisational agents: shared company context, isolated execution, approvals and MCP.

TypeScriptApache-2.0★ 220 stars⑂ 30 forkssince Jul 2025View on GitHub ↗
KindNetwork serviceLibraryChat bothow this is determined

lobu-ai/lobu holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on Community & Adoption (53/100). It was last updated today. A single contributor accounts for most of its recent work.

81
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

81
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 69 is calibrated to 81 on the published index scale (record calibration 2026-08-02).

Ownership

LobuOrganization
7 followers7 public repossince Jan 2026

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmlobu-monorepo3.0.8191155 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 3,424 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year3,424
human_commit_share1
days_since_last_push0
active_weeks_last_year43
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~1.8 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_taglobu-v19.2.0
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases1.8

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

53Moderate · 17% of overall
How it's scored
38/60Stars — 220 stars
12.2/25Forks — 30 forks
0/15Watchers — 0 watchers
Inputs used
forks30
stars220
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

56Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1/22.5Commit distribution — top contributor authored 96% of commits
13.5/13.5Contributor breadth — 37 contributors
10/10OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled37
top_contributor_share0.955
How it's scored
36.4/42Issue resolution — 87% of issues closed
27.3/30PR acceptance — 2,854/3,140 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs2,854
open_issues48
closed_issues313
prs_merged_7d54
prs_decided_7d57
prs_merged_30d54
prs_decided_30d57
issue_closed_ratio0.867
closed_unmerged_prs286
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
6.5/25Owner reach — 7 followers of lobu-ai
7.9/25Track record — 7 public repos, account ~0 yr old
Inputs used
followers7
owner_typeOrganization
is_verifiedno
owner_loginlobu-ai
public_repos7
account_age_days239
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 155 days ago
4/20Version history — 1 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageslobu-monorepo
ecosystemsnpm
any_deprecatedno
min_days_since_publish155

Engineering Quality

Are baseline engineering and documentation practices in place?

81Excellent · 19% of overall
How it's scored
24/24CI workflows — 21 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://lobu.ai
10/10Repository description
10/10Topics — 16 topics
10/10Wiki
Inputs used
topicsagent, chatbot, clawdbot, openclaw, personal-assistant, agent-infrastructure, agent-memory, ai-agents, event-sourcing, knowledge-graph, mcp, model-context-protocol, multi-agent, self-hosted, slack-bot, typescript
has_wikiyes
homepagehttps://lobu.ai
docs_sitehttps://lobu.ai
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

59Moderate · 16% of overall
How it's scored
4.5/7.5Binary-Artifacts — binaries present in source code
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 9 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5SAST — SAST tool is run on all commits
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 115 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.9

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories9
affected_packages1
assessed_packages17
unassessed_packages88
affected_by_severitycritical 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 17 resolved dependencies against OSV. 88 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

84Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md, packages/cli/AGENTS.md, packages/connector-sdk/AGENTS.md, packages/connector-worker/AGENTS.md, packages/connectors/AGENTS.md, packages/core/AGENTS.md, packages/server/AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://lobu.ai/llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://lobu.ai/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md, packages/cli/AGENTS.md, packages/connector-sdk/AGENTS.md, packages/connector-worker/AGENTS.md, packages/connectors/AGENTS.md, packages/core/AGENTS.md, packages/server/AGENTS.md
agent_instruction_max_bytes14,448
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — examples/agent-community/tsconfig.json, examples/brand-intelligence/tsconfig.json, examples/context-layer/tsconfig.json, examples/delivery/tsconfig.json, examples/ecommerce/tsconfig.json, examples/finance/tsconfig.json, examples/leadership/tsconfig.json, examples/legal/tsconfig.json, examples/lobu-crm/tsconfig.json, examples/lobu-team/tsconfig.json, examples/market/tsconfig.json, examples/personal-agent/tsconfig.json, examples/personal-finance/tsconfig.json, examples/sales/tsconfig.json, packages/cli/tsconfig.json, packages/client/tsconfig.json, packages/connector-sdk/tsconfig.json, packages/connector-worker/tsconfig.json, packages/connectors/tsconfig.json, packages/core/tsconfig.json, packages/device-connectors/tsconfig.json, packages/embeddings/tsconfig.json, packages/pgvector-embedded/tsconfig.json, packages/plugin-api/tsconfig.json, packages/plugin-conversations/tsconfig.json, packages/plugin-host/tsconfig.json, packages/plugin-mcp/tsconfig.json, packages/plugin-media/tsconfig.json, packages/plugin-memory/tsconfig.json, packages/plugin-toolkit/tsconfig.json, packages/promptfoo-provider/tsconfig.json, packages/server/tsconfig.json, tsconfig.json
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 12 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configsexamples/agent-community/tsconfig.json, examples/brand-intelligence/tsconfig.json, examples/context-layer/tsconfig.json, examples/delivery/tsconfig.json, examples/ecommerce/tsconfig.json, examples/finance/tsconfig.json, examples/leadership/tsconfig.json, examples/legal/tsconfig.json, examples/lobu-crm/tsconfig.json, examples/lobu-team/tsconfig.json, examples/market/tsconfig.json, examples/personal-agent/tsconfig.json, examples/personal-finance/tsconfig.json, examples/sales/tsconfig.json, packages/cli/tsconfig.json, packages/client/tsconfig.json, packages/connector-sdk/tsconfig.json, packages/connector-worker/tsconfig.json, packages/connectors/tsconfig.json, packages/core/tsconfig.json, packages/device-connectors/tsconfig.json, packages/embeddings/tsconfig.json, packages/pgvector-embedded/tsconfig.json, packages/plugin-api/tsconfig.json, packages/plugin-conversations/tsconfig.json, packages/plugin-host/tsconfig.json, packages/plugin-mcp/tsconfig.json, packages/plugin-media/tsconfig.json, packages/plugin-memory/tsconfig.json, packages/plugin-toolkit/tsconfig.json, packages/promptfoo-provider/tsconfig.json, packages/server/tsconfig.json, tsconfig.json
agent_commit_share0.12
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.1/55Manageable file sizes — 39/2,469 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes204,546
source_files_sampled2,469
oversized_source_files39
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofchat-bot, network-service

Key facts

220GitHub stars
37contributors
3,424commits, last 12 months
0days since last push
100releases
1bus factor
48open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index npm:lobu-monorepo@3.0.8; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 30 ⇿
0Stars
30Forks
97Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0510152025303022026-022026-062026-09
Major 0Minor 5Patch 6
OpenSSF Scorecard 4.9 / 10
4.9aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-12 07:29 UTC

6Binary-Artifactsbinaries present in source code
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
4Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities115 existing vulnerabilities detected
All dependencies 105

Full resolved dependency set from the GitHub dependency graph: 0 direct and 105 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@agentclientprotocol/claude-agent-acp0.70.0indirect
npm@agentclientprotocol/codex-acp1.6.2indirect
npm@agentclientprotocol/sdk1.4.0indirect
npm@aws-sdk/client-bedrock^3.1028.0indirect
npm@aws-sdk/client-secrets-manager^3.1028.0indirect
npm@better-auth/core1.6.9indirect
npm@better-auth/passkey1.6.9indirect
npm@biomejs/biome^2.2.2indirect
npm@chat-adapter/discord4.38.1indirect
npm@chat-adapter/gchat4.38.1indirect
npm@chat-adapter/slack4.38.1indirect
npm@chat-adapter/teams4.38.1indirect
npm@chat-adapter/telegram4.38.1indirect
npm@chat-adapter/whatsapp4.38.1indirect
npm@clack/prompts^1.2.0indirect
npm@daytonaio/sdk^0.205.1indirect
npm@hey-api/client-fetch^0.13.1indirect
npm@hey-api/openapi-ts^0.99.0indirect
npm@hono/node-server^2.0.11indirect
npm@hono/zod-openapi^1.2.1indirect
npm@inquirer/prompts^7.10.1indirect
npm@lobu/cli^13.3.0indirect
npm@lobu/cli^14.0.0indirect
npm@lobu/cli^9.3.0indirect
npm@lobu/connector-sdk^13.3.0indirect
npm@lobu/connector-sdk^9.3.0indirect
npm@mariozechner/pi-agent-core^0.73.1indirect
npm@mariozechner/pi-ai^0.73.1indirect
npm@mariozechner/pi-coding-agent^0.73.1indirect
npm@modelcontextprotocol/sdk^1.27.1indirect
npm@opentelemetry/api^1.9.0indirect
npm@opentelemetry/exporter-trace-otlp-grpc^0.57.0indirect
npm@opentelemetry/resources^1.30.0indirect
npm@opentelemetry/sdk-trace-node^1.30.0indirect
npm@opentelemetry/semantic-conventions^1.28.0indirect
npm@polyglot-sql/sdk^0.1.13indirect
npm@react-email/components^1.0.12indirect
npm@react-email/render^2.0.7indirect
npm@scalar/hono-api-reference^0.9.39indirect
npm@sentry/node^10.23.0indirect
npm@sentry/node^9.0.0indirect
npm@sinclair/typebox^0.34.33indirect
npm@sinclair/typebox^0.34.41indirect
npm@types/bun1.2.11indirect
npm@types/node20.19.9indirect
npm@types/node^20.0.0indirect
npm@types/node^20.10.0indirect
npm@types/node^20.19.9indirect
npm@types/react^19.2.14indirect
npm@types/tar^6.1.13indirect
npm@types/turndown^5.0.5indirect
npm@vercel/sandbox^2.2.1indirect
npm@vitest/coverage-v8^3.2.6indirect
npm@xenova/transformers^2.17.2indirect
npmajv^8.17.1indirect
npmajv-formats^3.0.1indirect
npmbetter-auth1.6.9indirect
npmchalk^5.3.0indirect
npmchat^4.38.1indirect
npmcommander^14.0.1indirect
npmcron-parser^5.6.1indirect
npmdotenv^16.4.5indirect
npmembedded-postgres18.3.0-beta.17indirect
npmesbuild^0.28.1indirect
npmhono^4.10.4indirect
npmhono-pino^0.10.3indirect
npmhusky^9.1.7indirect
npmisolated-vm^6.2.0indirect
npmisolated-vm^7.0.1indirect
npmisomorphic-git^1.34.0indirect
npmjimp^1.6.0indirect
npmjiti^2.4.2indirect
npmjscpd^4.0.5indirect
npmjust-bash^2.14.2indirect
npmknip^5.66.3indirect
npmky^1.14.0indirect
npmkysely^0.28.0indirect
npmkysely-postgres-js^2.0.0indirect
npmmarked^17.0.4indirect
npmmarked-terminal^7.3.0indirect
npmopen^10.1.0indirect
npmora^8.0.1indirect
npmpatchright^1.57.0indirect
npmpathe^2.0.3indirect
npmpino^10.1.0indirect
npmplaywright^1.60.0indirect
npmpostgres^3.4.7indirect
npmpromptfoo^0.121.0indirect
npmreact^19.2.5indirect
npmresend^6.6.0indirect
npmsharp^0.35.3indirect
npmtar^7.4.3indirect
npmtsx^4.19.2indirect
npmtsx^4.7.0indirect
npmturndown7.2.2indirect
npmtypescript^5.3.3indirect
npmtypescript^5.7.2indirect
npmtypescript^5.8.3indirect
npmundici7.29.0indirect
npmvite^6.0.0indirect
npmvitest^3.2.6indirect
npmwinston^3.17.0indirect
npmyaml^2.7.1indirect
npmzod^4.1.12indirect
npmzod^4.4.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 17 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 88 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
better-auth1.6.9indirectcritical91.7.0-beta.10

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.