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

Kotlin / kotlinx.collections.immutable

Immutable persistent collections for Kotlin

KotlinApache-2.0★ 1,422 stars⑂ 73 forkssince May 2016View on GitHub ↗

Kotlin/kotlinx.collections.immutable holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (78/100) and lowest on Engineering Quality (41/100). It was last updated today. 2 contributors account 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

KotlinOrganization · verified domain
3,452 followers141 public repossince Feb 2012

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?

78Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
12.5/36Commit cadence — 18/52 weeks with commits
15.3/18Commit volume — 49 commits in the last year
10/10OpenSSF Scorecard: Maintained — 15 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year49
human_commit_share1
days_since_last_push0
active_weeks_last_year18
How it's scored
27/27Ships releases — 16 releases published
36/36Release recency — latest release 51 days ago
12.6/27Release cadence — a release every ~219.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count16
latest_release_tagv0.5.2
releases_from_tagsno
days_since_latest_release51
mean_days_between_releases219.7
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?

71Good · 17% of overall
How it's scored
51.1/60Stars — 1,422 stars
15.5/25Forks — 73 forks
9.1/15Watchers — 45 watchers
Inputs used
forks73
stars1,422
watchers45
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductyes
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?

72Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.3/22.5Commit distribution — top contributor authored 50% of commits
13.5/13.5Contributor breadth — 27 contributors
10/10OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled27
top_contributor_share0.498
How it's scored
23.7/42Issue resolution — 56% of issues closed
21.6/30PR acceptance — 129/179 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-Review — Found 25/30 approved changesets -- score normalized to 8
Inputs used
merged_prs129
open_issues75
closed_issues97
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.564
closed_unmerged_prs50
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 3,452 followers of Kotlin
25/25Track record — 141 public repos, account ~14 yr old
Inputs used
followers3,452
owner_typeOrganization
is_verifiedyes
owner_loginKotlin
public_repos141
account_age_days5,357

Engineering Quality

Are baseline engineering and documentation practices in place?

41Weak · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://kotlinlang.org/api/kotlinx.collections.immutable/
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicskotlin, collections, immutable-collections, immutable
has_wikiyes
homepagehttps://kotlinlang.org/api/kotlinx.collections.immutable/
docs_sitehttps://kotlinlang.org/api/kotlinx.collections.immutable/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

52Moderate · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 30 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
6/7.5Code-Review — Found 25/30 approved changesets -- score normalized to 8
2.5/2.5Contributors — project has 12 contributing companies or organizations
0/10Dangerous-Workflow — no data
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 — 15 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
0/7.5Vulnerabilities — 10 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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
advisories10
affected_packages4
assessed_packages85
unassessed_packages5
affected_by_severityhigh 3, moderate 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 85 resolved dependencies against OSV. 5 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

51Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://kotlinlang.org/llms.txt)
30.9/40Legible commit history — 58 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://kotlinlang.org/llms.txt
legible_history_share0.58
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — .teamcity/pom.xml, benchmarks/build.gradle.kts, benchmarks/runner/build.gradle.kts (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Kotlin (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilesyarn.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests.teamcity/pom.xml, benchmarks/build.gradle.kts, benchmarks/runner/build.gradle.kts, build.gradle.kts, core/build.gradle.kts
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — Kotlin (statically typed)
55/55Manageable file sizes — 0/155 source files over 60KB
Inputs used
primary_languageKotlin
largest_source_bytes40,867
source_files_sampled155
oversized_source_files0

Key facts

1,422GitHub stars
27contributors
49commits, last 12 months
0days since last push
16releases
2bus factor
75open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch maven package 'kotlinx.team.infra:teamcity' from its registry

More detail

Star and fork history 0 ★ / 73 ⇿
0Stars
73Forks
16Releases

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.

01325385063757322017-032021-122026-09
Major 0Minor 2Patch 10

Each point covers 9 days.

OpenSSF Scorecard 4.0 / 10
4.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 08:35 UTC

9Binary-Artifactsbinaries present in source code
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
0CI-Tests0 out of 30 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 25/30 approved changesets -- score normalized to 8
10Contributorsproject has 12 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained15 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities10 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
Mavenorg.jetbrains.teamcity:configs-dsl-kotlin-latest${teamcity.dsl.version}.teamcity/pom.xml
Mavenorg.jetbrains.teamcity:configs-dsl-kotlin-plugins-latest1.0-SNAPSHOT.teamcity/pom.xml
Mavenorg.jetbrains.kotlin:kotlin-stdlib-jdk8${kotlin.version}.teamcity/pom.xml
Mavenorg.jetbrains.kotlin:kotlin-script-runtime${kotlin.version}.teamcity/pom.xml
All dependencies 90

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

RegistryPackageVersionRelation
Mavenorg.jetbrains.kotlin:kotlin-script-runtime—direct
Mavenorg.jetbrains.kotlin:kotlin-stdlib-jdk8—direct
Mavenorg.jetbrains.teamcity:configs-dsl-kotlin-latest—direct
Mavenorg.jetbrains.teamcity:configs-dsl-kotlin-plugins-latest1.0-SNAPSHOTdirect
Mavenorg.jetbrains.kotlin:kotlin-maven-plugin—indirect
Mavenorg.jetbrains.teamcity:teamcity-configs-maven-plugin—indirect
npm@isaacs/cliui8.0.2indirect
npm@pkgjs/parseargs0.11.0indirect
npmansi-regex5.0.1indirect
npmansi-regex6.2.2indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbenchmark2.1.4indirect
npmbrace-expansion2.1.2indirect
npmbrowser-stdout1.3.1indirect
npmbuffer-from1.1.2indirect
npmcamelcase6.3.0indirect
npmchalk4.1.2indirect
npmchokidar4.0.3indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdecamelize4.0.0indirect
npmdiff7.0.0indirect
npmeastasianwidth0.2.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmescalade3.2.0indirect
npmescape-string-regexp4.0.0indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmforeground-child3.3.1indirect
npmformat-util1.0.5indirect
npmget-caller-file2.0.5indirect
npmglob10.5.0indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmisexe2.0.0indirect
npmjackspeak3.4.3indirect
npmjs-yaml4.3.0indirect
npmkotlin-web-helpers3.0.0indirect
npmlocate-path6.0.0indirect
npmlodash4.18.1indirect
npmlog-symbols4.1.0indirect
npmlru-cache10.4.3indirect
npmminimatch9.0.9indirect
npmminipass7.1.3indirect
npmmocha11.7.2indirect
npmms2.1.3indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-scurry1.11.1indirect
npmpicocolors1.1.1indirect
npmplatform1.3.6indirect
npmrandombytes2.1.0indirect
npmreaddirp4.1.2indirect
npmrequire-directory2.1.1indirect
npmsafe-buffer5.2.1indirect
npmserialize-javascript6.0.2indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmsource-map0.6.1indirect
npmsource-map-support0.5.21indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.2.0indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmwhich2.0.2indirect
npmworkerpool9.3.4indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmy18n5.0.8indirect
npmyargs17.7.3indirect
npmyargs-parser21.1.1indirect
npmyargs-unparser2.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 4

This repository publishes no package the index resolves, so its own dependency graph was assessed — 85 packages, which also include development and test pins that never ship: 4 carry known advisories, of which 0 are direct. 5 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion2.1.2indirecthigh55.0.12
js-yaml4.3.0indirecthigh24.3.2
serialize-javascript6.0.2indirecthigh27.0.5
diff7.0.0indirectmoderate18.0.3

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.