Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-09 23:53 UTC

reactiveui / punchclock

Make sure your asynchronous operations show up to work on time

C#MIT★ 263 stars⑂ 18 forkssince Oct 2013View on GitHub ↗

reactiveui/punchclock holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (83/100) and lowest on Engineering Quality (54/100). It was last updated today. 2 contributors account for most of its recent work.

83
overall / 100
Excellent

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.

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

Ownership

ReactiveUIOrganization
292 followers26 public repossince Sep 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
NuGetPunchclock.Reactive7.2.0-20 days ago
NuGetPunchclock7.2.0-220 days ago

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
20.8/36Commit cadence30/52 weeks with commits
18/18Commit volume111 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year111
human_commit_share0.27
days_since_last_push0
active_weeks_last_year30
How it's scored
27/27Ships releases23 releases published
36/36Release recencylatest release 0 days ago
12.6/27Release cadencea release every ~224 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count23
latest_release_tagv7.2.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases224

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

67Good · 17% of overall
How it's scored
39.2/60Stars263 stars
10.3/25Forks18 forks
6.2/15Watchers14 watchers
Inputs used
forks18
stars263
watchers14
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
60.6/80Total downloads677,676 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesPunchclock.Reactive, Punchclock
dependents
ecosystemsnuget
total_downloads677,676
monthly_downloads
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

83Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.7/22.5Commit distributiontop contributor authored 35% of commits
13.5/13.5Contributor breadth15 contributors
10/10OpenSSF Scorecard: Contributorsproject has 31 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled15
top_contributor_share0.347
How it's scored
38.2/42Issue resolution91% of issues closed
22.1/30PR acceptance365/495 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs365
open_issues1
closed_issues10
prs_merged_7d1
prs_decided_7d1
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.909
closed_unmerged_prs130
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 domainverified-domain status not read for this organization
17.7/25Owner reach292 followers of reactiveui
22.4/25Track record26 public repos, account ~13 yr old
Inputs used
followers292
owner_typeOrganization
is_verified
owner_loginreactiveui
public_repos26
account_age_days5,080
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on nuget
35/35Publish recencylatest publish 0 days ago
20/20Version history22 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesPunchclock.Reactive, Punchclock
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics6 topics
10/10Wiki
Inputs used
topicsdotnet, dotnet-core, xamarin, http-client, async, cross-platform
has_wikiyes
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
7.5/7.5Binary-Artifactsno binaries found in the repo
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 31 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
1.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate6.1

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.

64Moderate · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md, AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
39.5/40Legible commit history20 of 27 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.741
agent_instruction_files.github/copilot-instructions.md, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes18,921
How it's scored
12.6/18One-command bootstrapsrc/Punchclock.Benchmarks/Punchclock.Benchmarks.csproj, src/Punchclock.Reactive.Tests/Punchclock.Reactive.Tests.csproj, src/Punchclock.Reactive/Punchclock.Reactive.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance73 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestssrc/Punchclock.Benchmarks/Punchclock.Benchmarks.csproj, src/Punchclock.Reactive.Tests/Punchclock.Reactive.Tests.csproj, src/Punchclock.Reactive/Punchclock.Reactive.csproj, src/Punchclock.Tests/Punchclock.Tests.csproj, src/Punchclock/Punchclock.csproj
dependency_bot_commit_share0.73
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/32 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes46,163
source_files_sampled32
oversized_source_files0

Key facts

263GitHub stars
15contributors
111commits, last 12 months
0days since last push
23releases
2bus factor
1open issues
package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 18 ⇿
0Stars
18Forks
13Releases

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.

0481216201812013-112018-112023-10
Major 1Minor 2Patch 8

Each point covers 10 days.

OpenSSF Scorecard 6.1 / 10
6.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-08-09 23:52 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 31 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
10Packagingpackaging workflow detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
NuGetReactiveUI.Primitivessrc/Punchclock.Benchmarks/Punchclock.Benchmarks.csproj
NuGetBenchmarkDotNetsrc/Punchclock.Benchmarks/Punchclock.Benchmarks.csproj
NuGetDynamicDatasrc/Punchclock.Reactive.Tests/Punchclock.Reactive.Tests.csproj
NuGetReactiveUI.Primitivessrc/Punchclock.Reactive.Tests/Punchclock.Reactive.Tests.csproj
NuGetReactiveUI.Primitives.Reactivesrc/Punchclock.Reactive.Tests/Punchclock.Reactive.Tests.csproj
NuGetReactiveUI.Primitives.Reactivesrc/Punchclock.Reactive/Punchclock.Reactive.csproj
NuGetReactiveUI.Primitivessrc/Punchclock.Tests/Punchclock.Tests.csproj
NuGetDynamicDatasrc/Punchclock.Tests/Punchclock.Tests.csproj
NuGetReactiveUI.Primitivessrc/Punchclock/Punchclock.csproj
All dependencies 4

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

RegistryPackageVersionRelation
NuGetBenchmarkDotNetdirect
NuGetDynamicDatadirect
NuGetReactiveUI.Primitivesdirect
NuGetReactiveUI.Primitives.Reactivedirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsNuGet.