Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 22:59 UTC

WolpertingerLabs / callboard

Lightweight Claude Code UI wrapper - integrates with your local settings and chats

TypeScriptMIT★ 2 stars⑂ 0 forkssince Feb 2026View on GitHub ↗
KindLibraryCommand-line toolMCP serverWeb interfaceNetwork servicehow this is determined

WolpertingerLabs/callboard holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Vitality (75/100) and lowest on Community & Adoption (32/100). It was last updated today. A single contributor accounts for most of its recent work.

60
overall / 100
Moderate

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.

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

Ownership

Wolpertinger LabsOrganization
0 followers4 public repossince May 2023

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

Package ecosystems

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
19.4/36Commit cadence — 28/52 weeks with commits
18/18Commit volume — 1,136 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,136
human_commit_share1
days_since_last_push0
active_weeks_last_year28
How it's scored
16.2/27Ships releases — 1 version tags (no GitHub releases)
27/36Release recency — latest release 92 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv1.0.0-alpha.22
releases_from_tagsyes
days_since_latest_release92
mean_days_between_releases—
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

32At Risk · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars2
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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
44/80Monthly downloads — 2,004 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@wolpertingerlabs/callboard
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,004
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?

58Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.6/22.5Commit distribution — top contributor authored 62% of commits
2.7/13.5Contributor breadth — 2 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.617
How it's scored
36.8/42Issue resolution — 88% of issues closed
29.2/30PR acceptance — 426/437 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 4/30 approved changesets -- score normalized to 1
Inputs used
merged_prs426
open_issues1
closed_issues7
prs_merged_7d40
prs_decided_7d41
prs_merged_30d59
prs_decided_30d60
issue_closed_ratio0.875
closed_unmerged_prs11
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
0/25Owner reach — 0 followers of WolpertingerLabs
11.8/25Track record — 4 public repos, account ~3 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginWolpertingerLabs
public_repos4
account_age_days1,218

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 1 days ago
20/20Version history — 74 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@wolpertingerlabs/callboard
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 24 out of 24 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.8/7.5Code-Review — Found 4/30 approved changesets -- score normalized to 1
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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 5 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 66 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: adm-zip 0.5.18 (high 7.5)
6.4/25Indirect dependencies free of known advisories — 5 affected: undici 5.29.0 (high 7.5), uuid 8.3.2 (high 7.5), @ai-sdk/provider-utils 5.0.0 (moderate 4.3), +2 more
27/40No advisories left outstanding — 3 advisory-carrying package(s) unaddressed past 90 days; oldest published 239 days ago
Inputs used
sourceosv
advisories19
affected_packages6
assessed_packages529
unassessed_packages0
affected_by_severityhigh 3, moderate 3
direct_affected_packages1
Matched the npm:@wolpertingerlabs/callboard@1.0.0-alpha.55 runtime dependency closure — what installing the published package pulls in — 529 packages. 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.

74Good · 4% of overall
How it's scored
45/45Agent instructions — .claude/CLAUDE.md, backend/src/scaffold/CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.anthropic.com/llms.txt)
40/40Legible commit history — 99 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.anthropic.com/llms.txt
legible_history_share0.99
agent_instruction_files.claude/CLAUDE.md, backend/src/scaffold/CLAUDE.md
agent_instruction_max_bytes9,896
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — backend/tsconfig.json, frontend/tsconfig.json, packages/computer-use/tsconfig.json, shared/tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 62 of the last 100 commits agent-authored or agent-credited
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_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsbackend/tsconfig.json, frontend/tsconfig.json, packages/computer-use/tsconfig.json, shared/tsconfig.json
agent_commit_share0.62
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.3/55Manageable file sizes — 11/815 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes172,691
source_files_sampled815
oversized_source_files11
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

2GitHub stars
2contributors
1,136commits, last 12 months
0days since last push
1releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.8 / 10
3.8aggregate

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-10 22:59 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests24 out of 24 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/30 approved changesets -- score normalized to 1
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities66 existing vulnerabilities detected
Direct dependencies 50
RegistryPackageVersion constraintManifest
npm@agentclientprotocol/sdk1.4.0backend/package.json
npm@anthropic-ai/claude-agent-sdk^0.3.261backend/package.json
npm@cline/sdk0.0.82backend/package.json
npm@earendil-works/pi-coding-agent0.85.1backend/package.json
npm@modelcontextprotocol/sdk^1.29.0backend/package.json
npm@openai/codex-sdk^0.153.4backend/package.json
npm@wolpertingerlabs/drawlatch^1.0.0-alpha.40backend/package.json
npmadm-zip^0.5.16backend/package.json
npmarchiver^7.0.1backend/package.json
npmcookie-parser^1.4.7backend/package.json
npmcors^2.8.5backend/package.json
npmcron-parser^5.0.0backend/package.json
npmdotenv^17.2.3backend/package.json
npmexpress^4.21.0backend/package.json
npmexpress-rate-limit^7.5.1backend/package.json
npmipaddr.js^2.4.0backend/package.json
npmmulter^2.0.2backend/package.json
npmnode-cron^3.0.3backend/package.json
npmshared*backend/package.json
npmwinston^3.19.0backend/package.json
npmzod>=4.4.3 <4.5.3backend/package.json
npmlucide-react^0.563.0frontend/package.json
npmreact^18.3.0frontend/package.json
npmreact-dom^18.3.0frontend/package.json
npmreact-markdown^10.1.0frontend/package.json
npmreact-router-dom^6.26.0frontend/package.json
npmrehype-highlight^7.0.2frontend/package.json
npmremark-gfm^4.0.1frontend/package.json
npmshared*frontend/package.json
npm@agentclientprotocol/sdk1.4.0package.json
npm@anthropic-ai/claude-agent-sdk^0.3.261package.json
npm@cline/sdk0.0.82package.json
npm@earendil-works/pi-coding-agent0.85.1package.json
npm@modelcontextprotocol/sdk^1.29.0package.json
npm@openai/codex-sdk^0.153.4package.json
npm@sap-cloud-sdk/connectivity4.8.0package.json
npm@wolpertingerlabs/drawlatch^1.0.0-alpha.40package.json
npmadm-zip^0.5.16package.json
npmarchiver^7.0.1package.json
npmcookie-parser^1.4.7package.json
npmcors^2.8.5package.json
npmcron-parser^5.0.0package.json
npmdotenv^17.2.3package.json
npmexpress^4.21.0package.json
npmexpress-rate-limit^7.5.1package.json
npmipaddr.js^2.4.0package.json
npmmulter^2.0.2package.json
npmnode-cron^3.0.3package.json
npmwinston^3.19.0package.json
npmzod>=4.4.3 <4.5.3package.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

Dependency advisories 6

Installing npm:@wolpertingerlabs/callboard@1.0.0-alpha.55 pulls in 529 packages, direct and transitive: 6 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
adm-zip0.5.18directhigh20.6.0
undici5.29.0indirecthigh128.9.0
uuid8.3.2indirecthigh113.0.1
@ai-sdk/provider-utils5.0.0indirectmoderate1—
@opentelemetry/core2.6.1indirectmoderate12.8.0
qs6.15.3indirectmoderate26.16.0

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.