Kotlin/kotlinx.serialization holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Community & Adoption (90/100) and lowest on Engineering Quality (44/100). It was last updated today. A single contributor accounts for most of its recent work.
78
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.
78
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)
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 67 is calibrated to 78 on the published index scale (record calibration 2026-08-02).
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25
Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40
No advisories left outstanding — no advisory carries a publication date
Inputs used
source
osv
advisories
16
affected_packages
6
assessed_packages
85
unassessed_packages
0
affected_by_severity
high 5, moderate 1
direct_affected_packages
0
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. 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.
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.
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.
Key facts
5,943GitHub stars
100contributors
52commits, last 12 months
0days since last push
37releases
1bus factor
277open 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 ★ / 677 ⇿
0Stars
677Forks
37Releases
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.
Major 1Minor 11Patch 15
Each point covers 9 days.
OpenSSF Scorecard 3.3 / 10
3.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-08-28 04:56 UTC
Full resolved dependency set from the GitHub dependency graph: 0 direct and 85 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
Registry
Package
Version
Relation
npm
@isaacs/cliui
8.0.2
indirect
npm
@pkgjs/parseargs
0.11.0
indirect
npm
ansi-regex
5.0.1
indirect
npm
ansi-regex
6.2.2
indirect
npm
ansi-styles
4.3.0
indirect
npm
ansi-styles
6.2.3
indirect
npm
argparse
2.0.1
indirect
npm
balanced-match
1.0.2
indirect
npm
brace-expansion
2.0.1
indirect
npm
browser-stdout
1.3.1
indirect
npm
buffer-from
1.1.2
indirect
npm
camelcase
6.3.0
indirect
npm
chalk
4.1.2
indirect
npm
chokidar
4.0.3
indirect
npm
cliui
8.0.1
indirect
npm
color-convert
2.0.1
indirect
npm
color-name
1.1.4
indirect
npm
cross-spawn
7.0.6
indirect
npm
debug
4.3.6
indirect
npm
debug
4.4.0
indirect
npm
decamelize
4.0.0
indirect
npm
diff
7.0.0
indirect
npm
eastasianwidth
0.2.0
indirect
npm
emoji-regex
8.0.0
indirect
npm
emoji-regex
9.2.2
indirect
npm
escalade
3.1.1
indirect
npm
escalade
3.2.0
indirect
npm
escape-string-regexp
4.0.0
indirect
npm
find-up
5.0.0
indirect
npm
flat
5.0.2
indirect
npm
foreground-child
3.3.1
indirect
npm
format-util
1.0.5
indirect
npm
get-caller-file
2.0.5
indirect
npm
glob
10.4.5
indirect
npm
has-flag
4.0.0
indirect
npm
he
1.2.0
indirect
npm
is-fullwidth-code-point
3.0.0
indirect
npm
is-path-inside
3.0.3
indirect
npm
is-plain-obj
2.1.0
indirect
npm
is-unicode-supported
0.1.0
indirect
npm
isexe
2.0.0
indirect
npm
jackspeak
3.4.3
indirect
npm
js-yaml
4.1.0
indirect
npm
kotlin-web-helpers
3.0.0
indirect
npm
locate-path
6.0.0
indirect
npm
log-symbols
4.1.0
indirect
npm
lru-cache
10.4.3
indirect
npm
minimatch
9.0.5
indirect
npm
minipass
7.1.2
indirect
npm
mocha
11.7.5
indirect
npm
ms
2.1.2
indirect
npm
ms
2.1.3
indirect
npm
p-limit
3.1.0
indirect
npm
p-locate
5.0.0
indirect
npm
package-json-from-dist
1.0.1
indirect
npm
path-exists
4.0.0
indirect
npm
path-key
3.1.1
indirect
npm
path-scurry
1.11.1
indirect
npm
picocolors
1.1.1
indirect
npm
randombytes
2.1.0
indirect
npm
readdirp
4.1.2
indirect
npm
require-directory
2.1.1
indirect
npm
safe-buffer
5.2.1
indirect
npm
serialize-javascript
6.0.2
indirect
npm
shebang-command
2.0.0
indirect
npm
shebang-regex
3.0.0
indirect
npm
signal-exit
4.1.0
indirect
npm
source-map
0.6.1
indirect
npm
source-map-support
0.5.21
indirect
npm
string-width
4.2.3
indirect
npm
string-width
5.1.2
indirect
npm
strip-ansi
6.0.1
indirect
npm
strip-ansi
7.1.2
indirect
npm
strip-json-comments
3.1.1
indirect
npm
supports-color
7.2.0
indirect
npm
supports-color
8.1.1
indirect
npm
which
2.0.2
indirect
npm
workerpool
9.3.4
indirect
npm
wrap-ansi
7.0.0
indirect
npm
wrap-ansi
8.1.0
indirect
npm
y18n
5.0.8
indirect
npm
yargs
17.7.2
indirect
npm
yargs-parser
21.1.1
indirect
npm
yargs-unparser
2.0.0
indirect
npm
yocto-queue
0.1.0
indirect
Dependency advisories 6
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: 6 carry known advisories, of which 0 are direct.
Package
Version
Relation
Severity
Advisories
Fixed in
brace-expansion
2.0.1
indirect
high
5
5.0.9
glob
10.4.5
indirect
high
1
11.1.0
js-yaml
4.1.0
indirect
high
4
4.3.1
minimatch
9.0.5
indirect
high
3
10.2.3
serialize-javascript
6.0.2
indirect
high
2
7.0.5
diff
7.0.0
indirect
moderate
1
8.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.
Related records
Inspected repositories sharing catalogue tags or ecosystems with Kotlin/kotlinx.serialization. Read them side by side →
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.
