Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-18 11:08 UTC

copenhagenatomics / CA_DataUploader

C# software package to upload temperature data from CA temperature hub product

C#MIT★ 4 stars⑂ 2 forkssince Apr 2018View on GitHub ↗

copenhagenatomics/CA_DataUploader holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Vitality (74/100) and lowest on Community & Adoption (37/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

163 followers13 public repossince Nov 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetCA.LoopControlPluginBase1.3.0-7278 days agoraspberrypiiotdatalogger
NuGetCA_DataUploaderLib22.1.0-11981 days agoraspberrypiiotdatalogger

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
13.2/36Commit cadence19/52 weeks with commits
13.3/18Commit volume29 commits in the last year
2/10OpenSSF Scorecard: Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year29
human_commit_share1
days_since_last_push0
active_weeks_last_year19
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 81 days ago
27/27Release cadencea release every ~15.6 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tag22.1.0
releases_from_tagsno
days_since_latest_release81
mean_days_between_releases15.6

Community & Adoption

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

37Weak · 17% of overall
How it's scored
7.7/60Stars4 stars
0/25Forks2 forks
0/15Watchers2 watchers
Inputs used
forks2
stars4
watchers2
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
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
53.9/80Total downloads153,650 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesCA.LoopControlPluginBase, CA_DataUploaderLib
dependents
ecosystemsnuget
total_downloads153,650
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?

71Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.5/22.5Commit distributiontop contributor authored 80% of commits
9.5/13.5Contributor breadth7 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.802
How it's scored
35.2/42Issue resolution84% of issues closed
29.1/30PR acceptance352/363 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
13.5/15OpenSSF Scorecard: Code-ReviewFound 24/26 approved changesets -- score normalized to 9
Inputs used
merged_prs352
open_issues10
closed_issues52
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.839
closed_unmerged_prs11
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
15.9/25Owner reach163 followers of copenhagenatomics
20.3/25Track record13 public repos, account ~8 yr old
Inputs used
followers163
owner_typeOrganization
is_verified
owner_logincopenhagenatomics
public_repos13
account_age_days3,182
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 81 days ago
20/20Version history119 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesCA.LoopControlPluginBase, CA_DataUploaderLib
ecosystemsnuget
any_deprecatedno
min_days_since_publish81

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
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?

57Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests25 out of 25 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
6.8/7.5Code-ReviewFound 24/26 approved changesets -- score normalized to 9
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
1.5/7.5Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
5/5Packagingpackaging workflow detected
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.6
Excluded from scoring (no data or not applicable): Branch-Protection. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages16
unassessed_packages0
affected_by_severitynone
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 16 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.

44Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history82 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.82
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCA.LoopControlPluginBase.Tests/CA.LoopControlPluginBase.Tests.csproj, CA.LoopControlPluginBase/CA.LoopControlPluginBase.csproj, CA_DataUploader/CA_DataUploader.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
0/8Automated maintenanceno automated dependency updates observed
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCA.LoopControlPluginBase.Tests/CA.LoopControlPluginBase.Tests.csproj, CA.LoopControlPluginBase/CA.LoopControlPluginBase.csproj, CA_DataUploader/CA_DataUploader.csproj, CA_DataUploaderLib/CA_DataUploaderLib.csproj, UnitTests/CA_DataUploader.UnitTests.csproj, UnitTests/UnitTests.csproj
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/125 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes55,011
source_files_sampled125
oversized_source_files0

Key facts

4GitHub stars
7contributors
29commits, last 12 months
0days since last push
100releases
1bus factor
10open issues
NuGetpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
87Releases

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.

111222212023-062024-082025-11
Major 16Minor 19Patch 49

Each point covers 3 days.

OpenSSF Scorecard 4.6 / 10
4.6aggregate

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

10Binary-Artifactsno binaries found in the repo
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
10CI-Tests25 out of 25 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 24/26 approved changesets -- score normalized to 9
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
10Packagingpackaging workflow detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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 21
RegistryPackageVersion constraintManifest
NuGetMSTest.Analyzers4.0.2CA.LoopControlPluginBase.Tests/CA.LoopControlPluginBase.Tests.csproj
NuGetMicrosoft.NET.Test.Sdk18.0.1CA.LoopControlPluginBase.Tests/CA.LoopControlPluginBase.Tests.csproj
NuGetMSTest.TestAdapter4.0.2CA.LoopControlPluginBase.Tests/CA.LoopControlPluginBase.Tests.csproj
NuGetMSTest.TestFramework4.0.2CA.LoopControlPluginBase.Tests/CA.LoopControlPluginBase.Tests.csproj
NuGetMinVer3.1.0CA.LoopControlPluginBase/CA.LoopControlPluginBase.csproj
NuGetMinVer3.1.0CA_DataUploader/CA_DataUploader.csproj
NuGetCoreCLR-NCalc3.1.253CA_DataUploaderLib/CA_DataUploaderLib.csproj
NuGetMinVer7.0.0CA_DataUploaderLib/CA_DataUploaderLib.csproj
NuGetSystem.IO.Ports6.0.0CA_DataUploaderLib/CA_DataUploaderLib.csproj
NuGetCA.LoopControlPluginBase1.3.0CA_DataUploaderLib/CA_DataUploaderLib.csproj
NuGetSystem.IO.Pipelines6.0.3CA_DataUploaderLib/CA_DataUploaderLib.csproj
NuGetUdpToHttpGateway.Client0.2.1CA_DataUploaderLib/CA_DataUploaderLib.csproj
NuGetMicrosoft.NET.Test.Sdk17.1.0UnitTests/CA_DataUploader.UnitTests.csproj
NuGetMSTest.TestAdapter2.2.10UnitTests/CA_DataUploader.UnitTests.csproj
NuGetMSTest.TestFramework2.2.10UnitTests/CA_DataUploader.UnitTests.csproj
NuGetMicrosoft.Extensions.TimeProvider.Testing8.0.0-rc.2.23510.2UnitTests/CA_DataUploader.UnitTests.csproj
NuGetMicrosoft.NET.Test.Sdk18.0.1UnitTests/UnitTests.csproj
NuGetMoq4.20.72UnitTests/UnitTests.csproj
NuGetMSTest.TestAdapter4.0.2UnitTests/UnitTests.csproj
NuGetMSTest.TestFramework4.0.2UnitTests/UnitTests.csproj
NuGetMicrosoft.Extensions.TimeProvider.Testing10.2.0UnitTests/UnitTests.csproj
All dependencies 16

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

RegistryPackageVersionRelation
NuGetCA.LoopControlPluginBase1.3.0direct
NuGetCoreCLR-NCalc3.1.253direct
NuGetMicrosoft.Extensions.TimeProvider.Testing10.2.0direct
NuGetMicrosoft.Extensions.TimeProvider.Testing8.0.0-rc.2.23510.2direct
NuGetMicrosoft.NET.Test.Sdk17.1.0direct
NuGetMicrosoft.NET.Test.Sdk18.0.1direct
NuGetMinVer3.1.0direct
NuGetMinVer7.0.0direct
NuGetMoq4.20.72direct
NuGetMSTest.TestAdapter2.2.10direct
NuGetMSTest.TestAdapter4.0.2direct
NuGetMSTest.TestFramework2.2.10direct
NuGetMSTest.TestFramework4.0.2direct
NuGetSystem.IO.Pipelines6.0.3direct
NuGetSystem.IO.Ports6.0.0direct
NuGetUdpToHttpGateway.Client0.2.1direct
Dependency advisories 0

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

No known advisories affect the assessed dependencies.

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

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