Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-06 03:17 UTC

varabyte / kobweb

A modern framework for full stack web apps in Kotlin, built upon Compose HTML

KotlinApache-2.0★ 2,242 stars⑂ 95 forkssince Jul 2021View on GitHub ↗

varabyte/kobweb holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Vitality (89/100) and lowest on Security (43/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

VarabyteOrganization
78 followers22 public repossince Aug 2021

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

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
22.8/36Commit cadence33/52 weeks with commits
18/18Commit volume260 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year260
human_commit_share0.99
days_since_last_push2
active_weeks_last_year33
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 17 days ago
19.8/27Release cadencea release every ~55.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv0.25.1
releases_from_tagsno
days_since_latest_release17
mean_days_between_releases55.6
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?

74Good · 17% of overall
How it's scored
54.3/60Stars2,242 stars
16.4/25Forks95 forks
7.2/15Watchers21 watchers
Inputs used
forks95
stars2,242
watchers21
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges11
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

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

53Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.1/22.5Commit distributiontop contributor authored 86% of commits
13.5/13.5Contributor breadth31 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled31
top_contributor_share0.862
How it's scored
30.9/42Issue resolution74% of issues closed
22.9/30PR acceptance208/273 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs208
open_issues105
closed_issues293
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.736
closed_unmerged_prs65
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 backingorganization-owned
0/20Verified domain
13.6/25Owner reach78 followers of varabyte
20/25Track record22 public repos, account ~5 yr old
Inputs used
followers78
owner_typeOrganization
is_verifiedno
owner_loginvarabyte
public_repos22
account_age_days1,848

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://kobweb.varabyte.com
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicscompose, web, kotlin, compose-html
has_wikiyes
homepagehttps://kobweb.varabyte.com
docs_sitehttps://kobweb.varabyte.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

43Weak · 16% of overall
How it's scored
6/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): CI-Tests, Signed-Releases. 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.aws.amazon.com/llms.txt)
16.2/40Legible commit history30 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.aws.amazon.com/llms.txt
legible_history_share0.303
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapbackend/io/build.gradle.kts, backend/kobweb-api/build.gradle.kts, backend/server-plugin/build.gradle.kts (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingKotlin (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsbackend/io/build.gradle.kts, backend/kobweb-api/build.gradle.kts, backend/server-plugin/build.gradle.kts, backend/server/build.gradle.kts, build.gradle.kts, common/client-server-internal/build.gradle.kts, common/framework-annotations/build.gradle.kts, common/kobweb-common/build.gradle.kts, common/kobweb-serialization/build.gradle.kts, common/kobwebx-frontmatter/build.gradle.kts, common/kobwebx-serialization-kotlinx/build.gradle.kts, frontend/browser-ext/build.gradle.kts, frontend/compose-html-ext/build.gradle.kts, frontend/kobweb-compose/build.gradle.kts, frontend/kobweb-core/build.gradle.kts, frontend/kobweb-silk/build.gradle.kts, frontend/kobweb-worker-interface/build.gradle.kts, frontend/kobweb-worker/build.gradle.kts, frontend/kobwebx-markdown/build.gradle.kts, frontend/silk-foundation/build.gradle.kts, frontend/silk-icons-fa/build.gradle.kts, frontend/silk-icons-lucide/build.gradle.kts, frontend/silk-icons-mdi/build.gradle.kts, frontend/silk-icons-ms/build.gradle.kts, frontend/silk-widgets-kobweb/build.gradle.kts, frontend/silk-widgets/build.gradle.kts, frontend/test/compose-test-utils/build.gradle.kts, gradle/build-logic/build.gradle.kts, gradle/build-logic/conventions/build.gradle.kts, gradle/build-logic/publish/build.gradle.kts, playground/build.gradle.kts, playground/site/build.gradle.kts, playground/sitelib/build.gradle.kts, playground/workers/countdown/build.gradle.kts, playground/workers/sum/build.gradle.kts, tools/aggregate-docs/build.gradle.kts, tools/gradle-plugins/application/build.gradle.kts, tools/gradle-plugins/core/build.gradle.kts, tools/gradle-plugins/extensions/markdown/build.gradle.kts, tools/gradle-plugins/library/build.gradle.kts, tools/gradle-plugins/worker/build.gradle.kts, tools/ksp/ksp-ext/build.gradle.kts, tools/ksp/site-processors/build.gradle.kts, tools/ksp/worker-processor/build.gradle.kts, tools/processor-common/build.gradle.kts
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeKotlin (statically typed)
54.9/55Manageable file sizes1/516 source files over 60KB
Inputs used
primary_languageKotlin
largest_source_bytes196,050
source_files_sampled516
oversized_source_files1

Key facts

2,242GitHub stars
31contributors
260commits, last 12 months
2days since last push
100releases
1bus factor
105open issues
Mavenpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 95 ⇿
0Stars
95Forks
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.

0204060801009432021-102024-022026-06
Major 0Minor 15Patch 74

Each point covers 5 days.

OpenSSF Scorecard 4.3 / 10
4.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-06 03:16 UTC

8Binary-Artifactsbinaries present in source code
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
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 12 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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.