Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 10:18 UTC

Shusek / kotlin-runtime-web-assembly

Kotlin Runtime Web Assembly

KotlinMIT★ 0 stars⑂ 0 forkssince Jun 2026forkView on GitHub ↗

Shusek/kotlin-runtime-web-assembly holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Vitality (98/100) and lowest on Community & Adoption (12/100). It was last updated 3 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

ShusekPersonal account
2 followers18 public repossince Mar 2013

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

Metrics by category

Vitality

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

98Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
31.8/36Commit cadence — 46/52 weeks with commits
18/18Commit volume — 423 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year423
human_commit_share0.62
days_since_last_push3
active_weeks_last_year46

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 4 releases published
36/36Release recency — latest release 3 days ago
27/27Release cadence — a release every ~6.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count4
latest_release_tagv0.3.4
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases6.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?

12Critical · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/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_readmeno
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

57Moderate · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.1/22.5Commit distribution — top contributor authored 46% of commits
13.5/13.5Contributor breadth — 35 contributors
10/10OpenSSF Scorecard: Contributors — project has 36 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled35
top_contributor_share0.463
How it's scored
0/42Issue resolution — no issues or no data
29.2/30PR acceptance — 72/74 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/3 approved changesets -- score normalized to 0
Inputs used
merged_prs72
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d18
prs_decided_30d18
issue_closed_ratio—
closed_unmerged_prs2
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
3.4/25Owner reach — 2 followers of Shusek
21.3/25Track record — 18 public repos, account ~13 yr old
Inputs used
followers2
owner_typeUser
is_verified—
owner_loginShusek
public_repos18
account_age_days4,954
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

45Weak · 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
0/20OpenSSF Scorecard: CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage site — https://shusek.github.io/kotlin-runtime-web-assembly/
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://shusek.github.io/kotlin-runtime-web-assembly/
docs_sitehttps://shusek.github.io/kotlin-runtime-web-assembly/
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

50Moderate · 16% of overall
How it's scored
0/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/3 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 36 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 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
3.8/7.5Vulnerabilities — 5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Packaging, 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.

84Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENT.md
0/15Machine-readable docs (llms.txt)
38.7/40Legible commit history — 45 of 62 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.726
agent_instruction_filesAGENT.md
agent_instruction_max_bytes5,113
How it's scored
12.6/18One-command bootstrap — build.gradle.kts, buildSrc/build.gradle.kts, modules/annotations/annotations/build.gradle.kts (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Kotlin (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 17 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 38 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
lockfilesCargo.lock, package-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.17
toolchain_manifestsbuild.gradle.kts, buildSrc/build.gradle.kts, modules/annotations/annotations/build.gradle.kts, modules/annotations/processor/build.gradle.kts, modules/bom/build.gradle.kts, modules/component-model/build.gradle.kts, modules/component-model/src/test/fixtures/json-sequence-guest/build.gradle.kts, modules/component-model/src/test/fixtures/wasm-wasi-generated-compile/build.gradle.kts, modules/log/build.gradle.kts, modules/runtime-wasmtime-android/build.gradle.kts, modules/runtime/build.gradle.kts, modules/runtime/src/wasmtime-p3-bridge/Cargo.toml, modules/wasi-preview3/build.gradle.kts, modules/wasi/build.gradle.kts, modules/wasm/build.gradle.kts, samples/android-tests/build.gradle.kts, samples/android-tests/device-tests/build.gradle.kts, samples/ios-runtime-smoke/build.gradle.kts, samples/sample/build.gradle.kts, testing/jmh/build.gradle.kts, testing/runtime-tests/build.gradle.kts, testing/wasi-tests/build.gradle.kts, testing/wasm-corpus/build.gradle.kts, testing/wasm-corpus/src/main/resources/dotnet/basic/DemoDotNetWasi.csproj, testing/wasm-corpus/src/main/resources/kotlin/hello-world/build.gradle.kts, testing/wasm-corpus/src/main/resources/rust-atomics/sieve-primes/Cargo.toml, testing/wasm-corpus/src/main/resources/rust/count_vowels/Cargo.toml, testing/wasm-corpus/src/main/resources/rust/greet-wasi/Cargo.toml, testing/wasm-corpus/src/main/resources/rust/hello-wasi/Cargo.toml, tools/cli/build.gradle.kts, tools/codegen/build.gradle.kts, tools/component-model-gradle-plugin/build.gradle.kts, tools/component-model-tooling/build.gradle.kts, tools/test-gen-lib/build.gradle.kts, tools/wabt/build.gradle.kts, tools/wasi-test-gen/build.gradle.kts, tools/wasm-tools/build.gradle.kts
dependency_bot_commit_share0.38
How it's scored
45/45Type-checkable code — Kotlin (statically typed)
53.2/55Manageable file sizes — 16/499 source files over 60KB
Inputs used
primary_languageKotlin
largest_source_bytes308,963
source_files_sampled499
oversized_source_files16
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — sample, samples
Inputs used
example_dirssample, samples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

0GitHub stars
35contributors
423commits, last 12 months
3days since last push
4releases
2bus factor
0open issues
Maven, PyPIpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-10-19 10:17 UTC

0Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/3 approved changesets -- score normalized to 0
10Contributorsproject has 36 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 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
5Vulnerabilities5 existing vulnerabilities detected
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.