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

svenjacobs / reveal

Reveal effect (coach mark) for Compose Multiplatform targeting Android, iOS, Desktop and Web

KotlinMIT★ 629 stars⑂ 18 forkssince Nov 2022View on GitHub ↗
KindMobile applicationhow this is determined

svenjacobs/reveal holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Vitality (92/100) and lowest on Sustainability & Governance (50/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

Sven JacobsPersonal account
192 followers20 public repossince Apr 2010@rewe-digital

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?

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
21.5/36Commit cadence — 31/52 weeks with commits
18/18Commit volume — 156 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year156
human_commit_share0.14
days_since_last_push2
active_weeks_last_year31

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 53 releases published
36/36Release recency — latest release 22 days ago
27/27Release cadence — a release every ~20.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count53
latest_release_tagv5.2.3
releases_from_tagsno
days_since_latest_release22
mean_days_between_releases20.5
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?

63Moderate · 17% of overall
How it's scored
45.4/60Stars — 629 stars
10.3/25Forks — 18 forks
0/15Watchers — 2 watchers
Inputs used
forks18
stars629
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
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?

50Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.7/22.5Commit distribution — top contributor authored 97% of commits
4.1/13.5Contributor breadth — 3 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.97
How it's scored
40/42Issue resolution — 95% of issues closed
27/30PR acceptance — 359/399 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/4 approved changesets -- score normalized to 0
Inputs used
merged_prs359
open_issues2
closed_issues41
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.953
closed_unmerged_prs40
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
16.4/25Owner reach — 192 followers of svenjacobs
21.6/25Track record — 20 public repos, account ~16 yr old
Inputs used
followers192
owner_typeUser
is_verified—
owner_loginsvenjacobs
public_repos20
account_age_days6,049
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests — 14 out of 30 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 20 topics
0/10Wiki
Inputs used
topicsandroid, coach-marks, compose, jetpack-compose, onboarding, reveal, tutorial, walkthrough, tour, user-onboarding, coach-mark, coach-mark-android, coachmarks, showcase, tap-target, compose-multiplatform, ios, kmp, kotlin, kotlin-multiplatform
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

61Moderate · 16% of overall
How it's scored
6/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — no data
1/2.5CI-Tests — 14 out of 30 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/4 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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 1 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
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 — detected GitHub workflow tokens with excessive permissions
4.5/7.5Vulnerabilities — 4 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.1
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
advisories4
affected_packages1
assessed_packages71
unassessed_packages0
affected_by_severitymoderate 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 71 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.

79Good · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md, AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files.github/copilot-instructions.md, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes6,818
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
12.6/18One-command bootstrap — android-tests/build.gradle.kts, build.gradle.kts, convention-plugins/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 — lockfile
10/10Demonstrated agent practice — 18 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 83 of the last 100 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.18
toolchain_manifestsandroid-tests/build.gradle.kts, build.gradle.kts, convention-plugins/build.gradle.kts, demo-app/androidApp/build.gradle.kts, demo-app/build.gradle.kts, demo-app/desktopApp/build.gradle.kts, demo-app/shared/build.gradle.kts, reveal-common/build.gradle.kts, reveal-core/build.gradle.kts, reveal-shapes/build.gradle.kts
dependency_bot_commit_share0.83
How it's scored
45/45Type-checkable code — Kotlin (statically typed)
55/55Manageable file sizes — 0/50 source files over 60KB
Inputs used
primary_languageKotlin
largest_source_bytes14,544
source_files_sampled50
oversized_source_files0

Key facts

629GitHub stars
3contributors
156commits, last 12 months
2days since last push
53releases
1bus factor
2open issues
Maven, 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 ★ / 18 ⇿
0Stars
18Forks
51Releases

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.

0481216201712022-122024-112026-10
Major 5Minor 12Patch 34

Each point covers 4 days.

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-11-19 09:18 UTC

8Binary-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
4CI-Tests14 out of 30 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/4 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6Vulnerabilities4 existing vulnerabilities detected
All dependencies 71

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

RegistryPackageVersionRelation
npm@babel/code-frame7.29.7indirect
npm@babel/helper-validator-identifier7.29.7indirect
npm@commitlint/cli21.2.4indirect
npm@commitlint/config-conventional21.2.4indirect
npm@commitlint/config-validator21.2.3indirect
npm@commitlint/ensure21.2.4indirect
npm@commitlint/execute-rule21.0.1indirect
npm@commitlint/format21.2.3indirect
npm@commitlint/is-ignored21.2.3indirect
npm@commitlint/lint21.2.4indirect
npm@commitlint/load21.2.4indirect
npm@commitlint/message21.2.0indirect
npm@commitlint/parse21.2.3indirect
npm@commitlint/read21.2.3indirect
npm@commitlint/resolve-extends21.2.3indirect
npm@commitlint/rules21.2.4indirect
npm@commitlint/to-lines21.0.1indirect
npm@commitlint/top-level21.2.0indirect
npm@commitlint/types21.2.3indirect
npm@conventional-changelog/git-client3.2.0indirect
npm@conventional-changelog/template1.4.0indirect
npm@simple-libs/child-process-utils2.0.0indirect
npm@simple-libs/stream-utils2.0.0indirect
npmajv8.20.0indirect
npmansi-regex6.4.0indirect
npmansi-styles6.2.3indirect
npmargparse2.0.1indirect
npmargue-cli3.2.0indirect
npmcallsites3.1.0indirect
npmcliui9.0.1indirect
npmconventional-changelog-angular9.4.0indirect
npmconventional-changelog-conventionalcommits10.4.1indirect
npmconventional-commits-parser7.1.3indirect
npmcosmiconfig9.0.2indirect
npmemoji-regex10.6.0indirect
npmenv-paths2.2.1indirect
npmerror-ex1.3.4indirect
npmes-toolkit1.52.0indirect
npmescalade3.2.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-uri3.1.8indirect
npmget-caller-file2.0.5indirect
npmget-east-asian-width1.7.0indirect
npmglobal-directory5.0.0indirect
npmhusky9.1.7indirect
npmimport-fresh3.3.1indirect
npmini6.0.0indirect
npmis-arrayish0.2.1indirect
npmis-plain-obj4.1.0indirect
npmjiti2.7.0indirect
npmjs-tokens4.0.0indirect
npmjs-yaml4.3.2indirect
npmjson-parse-even-better-errors2.3.1indirect
npmjson-schema-traverse1.0.0indirect
npmlines-and-columns1.2.4indirect
npmparent-module1.0.1indirect
npmparse-json5.2.0indirect
npmpicocolors1.1.1indirect
npmrequire-from-string2.0.2indirect
npmresolve-from4.0.0indirect
npmresolve-from5.0.0indirect
npmsemver7.8.5indirect
npmstring-width7.2.0indirect
npmstring-width8.3.0indirect
npmstrip-ansi7.2.0indirect
npmtinyexec1.3.1indirect
npmverkit0.5.0indirect
npmwrap-ansi9.0.2indirect
npmy18n5.0.8indirect
npmyargs18.2.0indirect
npmyargs-parser22.0.0indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
fast-uri3.1.8indirectmoderate44.2.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.