Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 05:51 UTC

lovasoa / whitebophir

Online collaborative Whiteboard that is simple, free, easy to use and to deploy

JavaScriptAGPL-3.0★ 2,643 stars⑂ 485 forkssince Aug 2013View on GitHub ↗

lovasoa/whitebophir holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Engineering Quality (80/100) and lowest on Security (51/100). It was last updated 35 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

Ophir LOJKINEPersonal account
649 followers363 public repossince Jan 2011@datadog

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
npmwhitebophir1.0.225412800 days agocollaborativewhiteboard

Metrics by category

Vitality

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

69Good · 21% of overall
How it's scored
18/36Push recency — last push 35 days ago
10.4/36Commit cadence — 15/52 weeks with commits
18/18Commit volume — 1,044 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,044
human_commit_share1
days_since_last_push35
active_weeks_last_year15
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 35 days ago
27/27Release cadence — a release every ~5.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.17.0
releases_from_tagsyes
days_since_latest_release35
mean_days_between_releases5.4
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?

62Moderate · 17% of overall
How it's scored
55.5/60Stars — 2,643 stars
22.4/25Forks — 485 forks
8.7/15Watchers — 38 watchers
Inputs used
forks485
stars2,643
watchers38
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (AGPL-3.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_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
23.2/80Monthly downloads — 54 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageswhitebophir
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads54
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?

52Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.7/22.5Commit distribution — top contributor authored 93% of commits
13.5/13.5Contributor breadth — 37 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled37
top_contributor_share0.926
How it's scored
24.7/42Issue resolution — 59% of issues closed
22.5/30PR acceptance — 122/163 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/9 approved changesets -- score normalized to 0
Inputs used
merged_prs122
open_issues94
closed_issues134
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.588
closed_unmerged_prs41
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
20.2/25Owner reach — 649 followers of lovasoa
25/25Track record — 363 public repos, account ~15 yr old
Inputs used
followers649
owner_typeUser
is_verified—
owner_loginlovasoa
public_repos363
account_age_days5,724
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 2,800 days ago
4/20Version history — 1 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageswhitebophir
ecosystemsnpm
any_deprecatedno
min_days_since_publish2,800

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 3 out of 3 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://wbo.ophir.dev
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicscollaborative, javascript, whiteboard, teaching, education, draw, art
has_wikiyes
homepagehttps://wbo.ophir.dev
docs_sitehttps://wbo.ophir.dev
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

51Moderate · 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
2.5/2.5CI-Tests — 3 out of 3 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/9 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 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 1 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.5
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: node-static 0.7.11 (high 7.5)
3/25Indirect dependencies free of known advisories — 7 affected: minimist 0.0.10 (critical 9.8), uglify-js 1.3.5 (critical 9.8), timespan 2.3.0 (high 7.5), +4 more
17.7/40No advisories left outstanding — 8 advisory-carrying package(s) unaddressed past 90 days; oldest published 3,242 days ago
Inputs used
sourceosv
advisories15
affected_packages8
assessed_packages84
unassessed_packages0
affected_by_severitycritical 2, high 2, moderate 2, low 2
direct_affected_packages1
Matched the npm:whitebophir@1.0.22 runtime dependency closure — what installing the published package pulls in — 84 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.

60Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
9.1/40Legible commit history — 17 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.17
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes28,766
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — tsconfig.json
10/10Reproducible environment — devcontainer, Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontaineryes
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — JavaScript with type-check config (tsconfig.json)
54.5/55Manageable file sizes — 2/204 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes86,379
source_files_sampled204
oversized_source_files2

Key facts

2,643GitHub stars
37contributors
1,044commits, last 12 months
35days since last push
100releases
1bus factor
94open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 485 ⇿
0Stars
485Forks
100Releases

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.

0100200300400500464112018-112022-102026-09
Major 1Minor 45Patch 54

Each point covers 8 days.

OpenSSF Scorecard 5.5 / 10
5.5aggregate

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 05:50 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests3 out of 3 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/9 approved changesets -- score normalized to 0
10Contributorsproject has 4 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 1 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
npm@opentelemetry/api^1.9.1package.json
npm@opentelemetry/exporter-logs-otlp-http^0.221.0package.json
npm@opentelemetry/exporter-metrics-otlp-http^0.221.0package.json
npm@opentelemetry/exporter-trace-otlp-http^0.221.0package.json
npm@opentelemetry/instrumentation-runtime-node^0.34.0package.json
npm@opentelemetry/resources^2.8.0package.json
npm@opentelemetry/sdk-logs^0.221.0package.json
npm@opentelemetry/sdk-metrics^2.8.0package.json
npm@opentelemetry/sdk-node^0.221.0package.json
npm@opentelemetry/sdk-trace-base^2.8.0package.json
npm@opentelemetry/semantic-conventions^1.40.0package.json
npmhandlebars^4.7.7package.json
npmjsonwebtoken^9.0.0package.json
npmserve-static^2.2.0package.json
npmsocket.io^4package.json
All dependencies 146

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

RegistryPackageVersionRelation
npm@opentelemetry/api1.9.1direct
npm@opentelemetry/exporter-logs-otlp-http0.219.0direct
npm@opentelemetry/exporter-metrics-otlp-http0.219.0direct
npm@opentelemetry/exporter-trace-otlp-http0.219.0direct
npm@opentelemetry/instrumentation-runtime-node0.32.0direct
npm@opentelemetry/resources2.8.0direct
npm@opentelemetry/resources2.9.0direct
npm@opentelemetry/sdk-logs0.219.0direct
npm@opentelemetry/sdk-metrics2.8.0direct
npm@opentelemetry/sdk-metrics2.9.0direct
npm@opentelemetry/sdk-node0.219.0direct
npm@opentelemetry/sdk-trace-base2.8.0direct
npm@opentelemetry/sdk-trace-base2.9.0direct
npm@opentelemetry/semantic-conventions1.41.1direct
npmhandlebars4.7.9direct
npmjsonwebtoken9.0.3direct
npmserve-static2.2.1direct
npmsocket.io4.8.3direct
npm@biomejs/biome2.5.2indirect
npm@biomejs/cli-darwin-arm642.5.2indirect
npm@biomejs/cli-darwin-x642.5.2indirect
npm@biomejs/cli-linux-arm642.5.2indirect
npm@biomejs/cli-linux-arm64-musl2.5.2indirect
npm@biomejs/cli-linux-x642.5.2indirect
npm@biomejs/cli-linux-x64-musl2.5.2indirect
npm@biomejs/cli-win32-arm642.5.2indirect
npm@biomejs/cli-win32-x642.5.2indirect
npm@grpc/grpc-js1.14.4indirect
npm@grpc/proto-loader0.8.1indirect
npm@js-sdsl/ordered-map4.4.2indirect
npm@opentelemetry/api-logs0.219.0indirect
npm@opentelemetry/configuration0.219.0indirect
npm@opentelemetry/context-async-hooks2.8.0indirect
npm@opentelemetry/core2.8.0indirect
npm@opentelemetry/core2.9.0indirect
npm@opentelemetry/exporter-logs-otlp-grpc0.219.0indirect
npm@opentelemetry/exporter-logs-otlp-proto0.219.0indirect
npm@opentelemetry/exporter-metrics-otlp-grpc0.219.0indirect
npm@opentelemetry/exporter-metrics-otlp-proto0.219.0indirect
npm@opentelemetry/exporter-prometheus0.219.0indirect
npm@opentelemetry/exporter-trace-otlp-grpc0.219.0indirect
npm@opentelemetry/exporter-trace-otlp-proto0.219.0indirect
npm@opentelemetry/exporter-zipkin2.8.0indirect
npm@opentelemetry/instrumentation0.219.0indirect
npm@opentelemetry/otlp-exporter-base0.219.0indirect
npm@opentelemetry/otlp-grpc-exporter-base0.219.0indirect
npm@opentelemetry/otlp-transformer0.219.0indirect
npm@opentelemetry/propagator-b32.8.0indirect
npm@opentelemetry/propagator-jaeger2.8.0indirect
npm@opentelemetry/sdk-trace2.9.0indirect
npm@opentelemetry/sdk-trace-node2.8.0indirect
npm@playwright/test1.61.1indirect
npm@protobufjs/aspromise1.1.2indirect
npm@protobufjs/base641.1.2indirect
npm@protobufjs/codegen2.0.5indirect
npm@protobufjs/eventemitter1.1.1indirect
npm@protobufjs/fetch1.1.1indirect
npm@protobufjs/float1.0.2indirect
npm@protobufjs/path1.1.2indirect
npm@protobufjs/pool1.1.0indirect
npm@protobufjs/utf81.1.1indirect
npm@socket.io/component-emitter3.1.2indirect
npm@types/cors2.8.19indirect
npm@types/node26.1.0indirect
npm@types/ws8.18.1indirect
npmaccepts1.3.8indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmbase64id2.0.0indirect
npmbuffer-equal-constant-time1.0.1indirect
npmcjs-module-lexer2.2.0indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcookie0.7.2indirect
npmcors2.8.6indirect
npmdebug4.4.3indirect
npmdepd2.0.0indirect
npmecdsa-sig-formatter1.0.11indirect
npmee-first1.1.1indirect
npmemoji-regex8.0.0indirect
npmencodeurl2.0.0indirect
npmengine.io6.6.9indirect
npmengine.io-parser5.2.3indirect
npmes-module-lexer2.3.0indirect
npmescalade3.2.0indirect
npmescape-html1.0.3indirect
npmetag1.8.1indirect
npmfresh2.0.0indirect
npmfsevents2.3.2indirect
npmget-caller-file2.0.5indirect
npmhttp-errors2.0.1indirect
npmimport-in-the-middle3.3.0indirect
npminherits2.0.4indirect
npmis-fullwidth-code-point3.0.0indirect
npmjwa2.0.1indirect
npmjws4.0.1indirect
npmlodash.camelcase4.3.0indirect
npmlodash.includes4.3.0indirect
npmlodash.isboolean3.0.3indirect
npmlodash.isinteger4.0.4indirect
npmlodash.isnumber3.0.3indirect
npmlodash.isplainobject4.0.6indirect
npmlodash.isstring4.0.1indirect
npmlodash.once4.1.1indirect
npmlong5.3.2indirect
npmmime-db1.52.0indirect
npmmime-db1.54.0indirect
npmmime-types2.1.35indirect
npmmime-types3.0.2indirect
npmminimist1.2.8indirect
npmmodule-details-from-path1.0.4indirect
npmms2.1.3indirect
npmnegotiator0.6.3indirect
npmneo-async2.6.2indirect
npmobject-assign4.1.1indirect
npmon-finished2.4.1indirect
npmparseurl1.3.3indirect
npmplaywright1.61.1indirect
npmplaywright-core1.61.1indirect
npmprotobufjs7.6.5indirect
npmrange-parser1.3.0indirect
npmrequire-directory2.1.1indirect
npmrequire-in-the-middle8.0.1indirect
npmsafe-buffer5.2.1indirect
npmsemver7.8.5indirect
npmsend1.2.1indirect
npmsetprototypeof1.2.0indirect
npmsocket.io-adapter2.5.8indirect
npmsocket.io-parser4.2.6indirect
npmsource-map0.6.1indirect
npmstatuses2.0.2indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmtoidentifier1.0.1indirect
npmtypescript6.0.3indirect
npmuglify-js3.19.3indirect
npmundici-types8.3.0indirect
npmvary1.1.2indirect
npmwordwrap1.0.0indirect
npmwrap-ansi7.0.0indirect
npmws8.21.0indirect
npmy18n5.0.8indirect
npmyaml2.9.0indirect
npmyargs17.7.3indirect
npmyargs-parser21.1.1indirect
Dependency advisories 8

Installing npm:whitebophir@1.0.22 pulls in 84 packages, direct and transitive: 8 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
minimist0.0.10indirectcritical21.2.6
uglify-js1.3.5indirectcritical22.7.2
node-static0.7.11directhigh2—
timespan2.3.0indirecthigh1—
js-yaml0.3.7indirectmoderate54.2.0
parseuri0.0.6indirectmoderate1—
cookie0.4.2indirectlow10.7.0
debug4.1.1indirectlow14.3.1

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.