Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 15:34 UTC

sverweij / watskeburt

get changed files & their statuses since any git revision

TypeScript · JavaScriptMIT★ 6 stars⑂ 2 forkssince Jun 2022View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

sverweij/watskeburt holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (84/100) and lowest on Sustainability & Governance (61/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

86
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.

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

Ownership

Sander VerweijPersonal account
483 followers34 public repossince Jun 2013

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
npmwatskeburt6.0.013,637,4325072 days agogitdiff

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
17.3/36Commit cadence — 25/52 weeks with commits
14.6/18Commit volume — 41 commits in the last year
10/10OpenSSF Scorecard: Maintained — 15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year41
human_commit_share0.85
days_since_last_push1
active_weeks_last_year25
How it's scored
27/27Ships releases — 25 releases published
36/36Release recency — latest release 72 days ago
19.8/27Release cadence — a release every ~62.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count25
latest_release_tagv6.0.0
releases_from_tagsno
days_since_latest_release72
mean_days_between_releases62.1
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
11.3/60Stars — 6 stars
0/25Forks — 2 forks
0/15Watchers — 1 watchers
Inputs used
forks2
stars6
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 13,637,432 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageswatskeburt
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads13,637,432
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution — 100% of issues closed
29.5/30PR acceptance — 64/65 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/23 approved changesets -- score normalized to 0
Inputs used
merged_prs64
open_issues0
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs1
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
19.3/25Owner reach — 483 followers of sverweij
23.2/25Track record — 34 public repos, account ~13 yr old
Inputs used
followers483
owner_typeUser
is_verified—
owner_loginsverweij
public_repos34
account_age_days4,810
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 npm
35/35Publish recency — latest publish 72 days ago
20/20Version history — 50 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageswatskeburt
ecosystemsnpm
any_deprecatedno
min_days_since_publish72

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 7 out of 7 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://www.npmjs.com/package/watskeburt
10/10Repository description
10/10Topics — 2 topics
0/10Wiki
Inputs used
topicsgit, git-diff
has_wikino
homepagehttps://www.npmjs.com/package/watskeburt
docs_sitehttps://www.npmjs.com/package/watskeburt
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 7 out of 7 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/23 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
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 — 15 commit(s) and 0 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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.7
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

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
advisories1
affected_packages1
assessed_packages181
unassessed_packages0
affected_by_severityhigh 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 181 resolved dependencies against OSV. 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.

72Good · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 69 of 85 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.812
agent_instruction_files.github/copilot-instructions.md
agent_instruction_max_bytes3,132
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 15 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.15
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/24 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes10,838
source_files_sampled24
oversized_source_files0

Key facts

6GitHub stars
1contributors
41commits, last 12 months
1days since last push
25releases
1bus factor
0open 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 ★ / 2 ⇿
0Stars
2Forks
23Releases

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.

111222212023-042024-092026-02
Major 4Minor 2Patch 14

Each point covers 3 days.

OpenSSF Scorecard 6.7 / 10
6.7aggregate

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-08-27 15:34 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests7 out of 7 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/23 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained15 commit(s) and 0 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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 181

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

RegistryPackageVersionRelation
npm@bcoe/v8-coverage1.0.2indirect
npm@esbuild/aix-ppc640.28.1indirect
npm@esbuild/android-arm0.28.1indirect
npm@esbuild/android-arm640.28.1indirect
npm@esbuild/android-x640.28.1indirect
npm@esbuild/darwin-arm640.28.1indirect
npm@esbuild/darwin-x640.28.1indirect
npm@esbuild/freebsd-arm640.28.1indirect
npm@esbuild/freebsd-x640.28.1indirect
npm@esbuild/linux-arm0.28.1indirect
npm@esbuild/linux-arm640.28.1indirect
npm@esbuild/linux-ia320.28.1indirect
npm@esbuild/linux-loong640.28.1indirect
npm@esbuild/linux-mips64el0.28.1indirect
npm@esbuild/linux-ppc640.28.1indirect
npm@esbuild/linux-riscv640.28.1indirect
npm@esbuild/linux-s390x0.28.1indirect
npm@esbuild/linux-x640.28.1indirect
npm@esbuild/netbsd-arm640.28.1indirect
npm@esbuild/netbsd-x640.28.1indirect
npm@esbuild/openbsd-arm640.28.1indirect
npm@esbuild/openbsd-x640.28.1indirect
npm@esbuild/openharmony-arm640.28.1indirect
npm@esbuild/sunos-x640.28.1indirect
npm@esbuild/win32-arm640.28.1indirect
npm@esbuild/win32-ia320.28.1indirect
npm@esbuild/win32-x640.28.1indirect
npm@gar/promise-retry1.0.3indirect
npm@istanbuljs/schema0.1.6indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@npmcli/config10.11.0indirect
npm@npmcli/git7.0.2indirect
npm@npmcli/map-workspaces5.0.3indirect
npm@npmcli/name-from-folder4.0.0indirect
npm@npmcli/package-json7.0.5indirect
npm@npmcli/promise-spawn9.0.1indirect
npm@oxlint/binding-android-arm-eabi1.75.0indirect
npm@oxlint/binding-android-arm641.75.0indirect
npm@oxlint/binding-darwin-arm641.75.0indirect
npm@oxlint/binding-darwin-x641.75.0indirect
npm@oxlint/binding-freebsd-x641.75.0indirect
npm@oxlint/binding-linux-arm-gnueabihf1.75.0indirect
npm@oxlint/binding-linux-arm-musleabihf1.75.0indirect
npm@oxlint/binding-linux-arm64-gnu1.75.0indirect
npm@oxlint/binding-linux-arm64-musl1.75.0indirect
npm@oxlint/binding-linux-ppc64-gnu1.75.0indirect
npm@oxlint/binding-linux-riscv64-gnu1.75.0indirect
npm@oxlint/binding-linux-riscv64-musl1.75.0indirect
npm@oxlint/binding-linux-s390x-gnu1.75.0indirect
npm@oxlint/binding-linux-x64-gnu1.75.0indirect
npm@oxlint/binding-linux-x64-musl1.75.0indirect
npm@oxlint/binding-openharmony-arm641.75.0indirect
npm@oxlint/binding-win32-arm64-msvc1.75.0indirect
npm@oxlint/binding-win32-ia32-msvc1.75.0indirect
npm@oxlint/binding-win32-x64-msvc1.75.0indirect
npm@types/istanbul-lib-coverage2.0.6indirect
npm@types/node26.1.1indirect
npmabbrev4.0.0indirect
npmacorn8.17.0indirect
npmacorn-jsx5.3.2indirect
npmacorn-jsx-walk2.0.0indirect
npmacorn-loose8.5.2indirect
npmacorn-walk8.3.5indirect
npmansi-regex6.2.2indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.8indirect
npmc812.0.0indirect
npmchalk4.1.2indirect
npmci-info4.4.0indirect
npmclean-pkg-json2.0.0indirect
npmcliui9.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcommander15.0.0indirect
npmconvert-source-map2.0.0indirect
npmcross-spawn7.0.6indirect
npmdependency-cruiser18.1.0indirect
npmemoji-regex10.6.0indirect
npmenhanced-resolve5.24.2indirect
npmes-errors1.3.0indirect
npmesbuild0.28.1indirect
npmescalade3.2.0indirect
npmfind-up5.0.0indirect
npmforeground-child3.3.1indirect
npmfsevents2.3.3indirect
npmfunction-bind1.1.2indirect
npmget-caller-file2.0.5indirect
npmget-east-asian-width1.6.0indirect
npmglob13.0.6indirect
npmglobal-directory4.0.1indirect
npmgraceful-fs4.2.11indirect
npmhas-flag4.0.0indirect
npmhasown2.0.4indirect
npmhosted-git-info9.0.3indirect
npmhtml-escaper2.0.2indirect
npmignore7.0.6indirect
npmini4.1.1indirect
npmini6.0.0indirect
npminterpret3.1.1indirect
npmis-core-module2.16.2indirect
npmis-installed-globally1.0.0indirect
npmis-path-inside4.0.0indirect
npmisexe2.0.0indirect
npmisexe4.0.0indirect
npmistanbul-lib-coverage3.2.2indirect
npmistanbul-lib-report3.0.1indirect
npmistanbul-reports3.2.0indirect
npmjson-parse-even-better-errors5.0.0indirect
npmjson-parse-even-better-errors6.0.0indirect
npmjson52.2.3indirect
npmkleur3.0.3indirect
npmlocate-path6.0.0indirect
npmlru-cache11.5.2indirect
npmmake-dir4.0.0indirect
npmmemorystream0.3.1indirect
npmminimatch10.2.5indirect
npmminimist1.2.8indirect
npmminipass7.1.3indirect
npmnopt9.0.0indirect
npmnpm-install-checks8.0.0indirect
npmnpm-normalize-package-bin5.0.0indirect
npmnpm-normalize-package-bin6.0.0indirect
npmnpm-package-arg13.0.2indirect
npmnpm-pick-manifest11.0.3indirect
npmnpm-run-all29.0.2indirect
npmoxlint1.75.0indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-parse1.0.7indirect
npmpath-scurry2.0.2indirect
npmpicomatch4.0.5indirect
npmpidtree1.0.0indirect
npmprettier3.9.6indirect
npmproc-log6.1.0indirect
npmprompts2.4.2indirect
npmread-package-json-fast6.0.0indirect
npmrechoir0.8.0indirect
npmregexp-tree0.1.27indirect
npmresolve1.22.12indirect
npmsafe-regex2.1.1indirect
npmsemver7.8.5indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmshell-quote1.10.0indirect
npmsignal-exit4.1.0indirect
npmsisteransi1.0.5indirect
npmspdx-exceptions2.5.0indirect
npmspdx-expression-parse4.0.0indirect
npmspdx-license-ids3.0.23indirect
npmstring-width7.2.0indirect
npmstrip-ansi7.2.0indirect
npmstrip-bom3.0.0indirect
npmsupports-color7.2.0indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmtapable2.3.3indirect
npmtest-exclude8.0.0indirect
npmtsconfig-paths4.2.0indirect
npmtsconfig-paths-webpack-plugin4.2.0indirect
npmtsx4.23.1indirect
npmtypescript6.0.3indirect
npmundici-types8.3.0indirect
npmupem11.0.0indirect
npmv8-to-istanbul9.3.0indirect
npmvalidate-npm-package-name7.0.2indirect
npmwalk-up-path4.0.0indirect
npmwatskeburt6.0.0indirect
npmwhich2.0.2indirect
npmwhich6.0.1indirect
npmwhich7.0.0indirect
npmwrap-ansi9.0.2indirect
npmy18n5.0.8indirect
npmyargs18.0.0indirect
npmyargs-parser21.1.1indirect
npmyargs-parser22.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 181 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion5.0.8indirecthigh15.0.9

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.