Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 16:10 UTC

voglster / lumbergh

Self-hosted web dashboard for supervising multiple Claude Code AI sessions in tmux. Live terminals, real-time git diffs, file browser, todo lists, prompt templates, and mobile PWA support. Micromanage your AI interns from any device.

Python · TypeScriptMIT★ 32 stars⑂ 10 forkssince Feb 2026View on GitHub ↗
KindNetwork serviceWeb interfaceLibraryCommand-line toolhow this is determined

voglster/lumbergh holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Engineering Quality (88/100) and lowest on Security (33/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

71
overall / 100
Good

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.

71
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 63 is calibrated to 71 on the published index scale (record calibration 2026-08-02).

Ownership

James VogelPersonal account
26 followers73 public repossince Feb 2011capSpire

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmslidespoints to another repo — not scored0.0.02714604 days agoslideshowppt
PyPIpylumbergh0.22.04,37927014 days agoagentaiclaude-codedashboarddevtoolssession-managersupervisorterminaltmux

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
19.4/36Commit cadence — 28/52 weeks with commits
18/18Commit volume — 623 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year623
human_commit_share1
days_since_last_push5
active_weeks_last_year28
How it's scored
27/27Ships releases — 79 releases published
36/36Release recency — latest release 5 days ago
27/27Release cadence — a release every ~5.8 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count79
latest_release_tagalpha
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases5.8

Community & Adoption

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

46Weak · 17% of overall
How it's scored
24.2/60Stars — 32 stars
8/25Forks — 10 forks
0/15Watchers — 0 watchers
Inputs used
forks10
stars32
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
48.6/80Monthly downloads — 4,379 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespylumbergh
dependents—
ecosystemspypi
total_downloads—
monthly_downloads4,379
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.8/22.5Commit distribution — top contributor authored 97% of commits
10.8/13.5Contributor breadth — 8 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.966
How it's scored
42/42Issue resolution — 100% of issues closed
5/30PR acceptance — 3/18 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_prs3
open_issues0
closed_issues10
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs15
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
10.3/25Owner reach — 26 followers of voglster
25/25Track record — 73 public repos, account ~15 yr old
Inputs used
followers26
owner_typeUser
is_verified—
owner_loginvoglster
public_repos73
account_age_days5,689
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 14 days ago
20/20Version history — 270 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespylumbergh
ecosystemspypi
any_deprecatedno
min_days_since_publish14

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — backend/pyproject.toml ([tool.ruff]), eslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://voglster.github.io/lumbergh/
10/10Repository description
10/10Topics — 11 topics
10/10Wiki
Inputs used
topicsai-tools, claude-code, dashboard, developer-tools, fastapi, react, self-hosted, terminal, tmux, xterm-js, claude
has_wikiyes
homepagehttps://voglster.github.io/lumbergh/
docs_sitehttps://voglster.github.io/lumbergh/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

33At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
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
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not 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 — 100 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.3
Excluded from scoring (no data or not applicable): CI-Tests. Remaining weights renormalized.

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.

71Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes13,048
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — backend/pyproject.toml ([tool.ruff]), eslint.config.js
11/11Static type checking — frontend/tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsfrontend/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (frontend/tsconfig.json)
54.3/55Manageable file sizes — 6/503 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes88,286
source_files_sampled503
oversized_source_files6

Key facts

32GitHub stars
8contributors
623commits, last 12 months
5days since last push
79releases
1bus factor
0open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'slides' points at a different repository (https://github.com/hacksparrow/slides); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 10 ⇿
0Stars
10Forks
78Releases

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.

02468101012026-032026-062026-09
Major 0Minor 21Patch 57
OpenSSF Scorecard 3.3 / 10
3.3aggregate

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-14 16:10 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities100 existing vulnerabilities detected
Direct dependencies 30
RegistryPackageVersion constraintManifest
PyPIfastapi—backend/pyproject.toml
PyPIuvicorn—backend/pyproject.toml
PyPIlibtmux—backend/pyproject.toml
PyPItinydb—backend/pyproject.toml
PyPIgitpython>=3.1backend/pyproject.toml
PyPIhttpx>=0.27backend/pyproject.toml
PyPIwebsockets>=12backend/pyproject.toml
PyPIcryptography>=42.0backend/pyproject.toml
PyPIpython-multipart—backend/pyproject.toml
PyPIpywinpty>=3.0.3backend/pyproject.toml
npm@git-diff-view/core^0.0.39frontend/package.json
npm@git-diff-view/react^0.0.39frontend/package.json
npm@tanstack/react-virtual^3.13.24frontend/package.json
npm@types/papaparse^5.5.2frontend/package.json
npm@uiw/react-markdown-preview^5.1.5frontend/package.json
npm@xterm/addon-fit^0.11.0frontend/package.json
npm@xterm/addon-unicode11^0.9.0frontend/package.json
npm@xterm/addon-web-links^0.12.0frontend/package.json
npm@xterm/xterm^6.0.0frontend/package.json
npmdayjs^1.11.19frontend/package.json
npmhighlight.js^11.11.1frontend/package.json
npmlucide-react^0.576.0frontend/package.json
npmmermaid^11.4.0frontend/package.json
npmpapaparse^5.5.3frontend/package.json
npmreact^19.2.0frontend/package.json
npmreact-dom^19.2.0frontend/package.json
npmreact-router-dom^7.13.0frontend/package.json
npm@iconify-json/carbon^1.2.19slides/package.json
npm@slidev/cli^52.14.1slides/package.json
npm@slidev/theme-default^0.25.0slides/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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, PyPI.