Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 02:21 UTC

Kiryuumaru / NukeBuildHelpers

NukeBuildHelpers is a C# project build automation tool built on top of NukeBuild. It supports both GitHub Actions and Azure Pipelines for CI/CD, enabling release management across multiple projects and environments within a single repository.

C#MIT★ 3 stars⑂ 0 forkssince Dec 2023View on GitHub ↗

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

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.

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

Ownership

Clynt Neiko RupintaPersonal account

14 followers56 public repossince Sep 2017

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
NuGet	NukeBuildHelpers	1.0.2	-	14	—	nukebuildhelpers nuke build helpers

Metrics by category

Vitality

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

84Excellent · 21% of overall

Development activity

80Excellent

How it's scored

36/36	Push recency — last push 1 days ago
18.7/36	Commit cadence — 27/52 weeks with commits
14.8/18	Commit volume — 44 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	44
human_commit_share	0.47
days_since_last_push	1
active_weeks_last_year	27

Release discipline

90Excellent

How it's scored

27/27	Ships releases — 100 releases published
36/36	Release recency — latest release 1 days ago
27/27	Release cadence — a release every ~7.2 days
0/10	OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.

Inputs used

releases_count	100
latest_release_tag	build.20260909143250.5c17b96
releases_from_tags	no
days_since_latest_release	1
mean_days_between_releases	7.2

Community & Adoption

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

37Weak · 17% of overall

Popularity & adoption

5Critical

How it's scored

4.9/60	Stars — 3 stars
0/25	Forks — 0 forks
0/15	Watchers — 1 watchers

Inputs used

forks	0
stars	3
watchers	1
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

70Good

How it's scored

55.9/80	Total downloads — 241,044 downloads all-time across nuget
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	NukeBuildHelpers
dependents	—
ecosystems	nuget
total_downloads	241,044
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?

54Moderate · 23% of overall

Maintainer resilience (bus factor)

16Critical

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
0/22.5	Commit distribution — top contributor authored 100% of commits
1.4/13.5	Contributor breadth — 1 contributors
6/10	OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6

Inputs used

bus_factor	1
contributors_sampled	1
top_contributor_share	1

Issue & PR responsiveness

62Moderate

How it's scored

0/42	Issue resolution — no issues or no data
27.8/30	PR acceptance — 281/303 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 0/1 approved changesets -- score normalized to 0

Inputs used

merged_prs	281
open_issues	0
closed_issues	0
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	—
closed_unmerged_prs	22
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

54Moderate

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
8.5/25	Owner reach — 14 followers of Kiryuumaru
24.8/25	Track record — 56 public repos, account ~9 yr old

Inputs used

followers	14
owner_type	User
is_verified	—
owner_login	Kiryuumaru
public_repos	56
account_age_days	3,295

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on nuget
0/35	Publish recency — no data
20/20	Version history — 14 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	NukeBuildHelpers
ecosystems	nuget
any_deprecated	no
min_days_since_publish	—

Excluded from scoring (no data or not applicable): Publish recency. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 19% of overall

Engineering practices

50Moderate

How it's scored

24/24	CI workflows — 3 workflow(s)
0/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
6.4/6.4	.editorconfig
20/20	OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10

Inputs used

has_ci	yes
has_tests	no
has_editorconfig	yes
has_linter_config	no
has_precommit_config	no

Documentation

75Good

How it's scored

30/30	README
25/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	yes
has_description	yes

Security

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

52Moderate · 16% of overall

Security posture

50Moderate

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
3/7.5	Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5	CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/1 approved changesets -- score normalized to 0
1.5/2.5	Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
7.5/7.5	Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
0/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5	Vulnerabilities — 0 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	17
scorecard_version	v5.5.0
checks_inconclusive	1
scorecard_aggregate	5

Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

61Moderate

How it's scored

12.6/35	Direct dependencies free of known advisories — 1 affected: Microsoft.Build.Tasks.Core 17.11.48 (high 8.0)
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.3/40	No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 485 days ago

Inputs used

source	osv
advisories	1
affected_packages	1
assessed_packages	18
unassessed_packages	0
affected_by_severity	high 1
direct_affected_packages	1

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 18 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.

49Weak · 4% of overall

Agent context & guidance

40Weak

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
40/40	Legible commit history — 47 of 47 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	1
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

36Weak

How it's scored

12.6/18	One-command bootstrap — NukeBuildHelpers.UnitTest/NukeBuildHelpers.UnitTest.csproj, NukeBuildHelpers/NukeBuildHelpers.csproj, build/_build.csproj (toolchain convention, no task runner)
0/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — C# (statically typed)
0/10	Reproducible environment
4/10	Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
8/8	Automated maintenance — 53 of the last 100 commits are automated dependency updates
0/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0

Inputs used

has_nix	no
has_tests	no
lockfiles	—
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0.02
toolchain_manifests	NukeBuildHelpers.UnitTest/NukeBuildHelpers.UnitTest.csproj, NukeBuildHelpers/NukeBuildHelpers.csproj, build/_build.csproj
dependency_bot_commit_share	0.53

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — C# (statically typed)
54.5/55	Manageable file sizes — 1/108 source files over 60KB

Inputs used

primary_language	C#
largest_source_bytes	72,036
source_files_sampled	108
oversized_source_files	1

Key facts

3GitHub stars

1contributors

44commits, last 12 months

1days since last push

100releases

1bus factor

0open issues

NuGetpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 5.0 / 10

5.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-09-11 02:21 UTC

10	Binary-Artifacts	no binaries found in the repo
4	Branch-Protection	branch protection is not maximal on development and all release branches
10	CI-Tests	30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/1 approved changesets -- score normalized to 0
6	Contributors	project has 2 contributing companies or organizations -- score normalized to 6
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
0	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 0
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
0	Signed-Releases	Project has not signed or included provenance with any releases.
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
10	Vulnerabilities	0 existing vulnerabilities detected

Direct dependencies 21

Registry	Package	Version constraint	Manifest
NuGet	GitHubActionsTestLogger	`3.0.5`	NukeBuildHelpers.UnitTest/NukeBuildHelpers.UnitTest.csproj
NuGet	Microsoft.NET.Test.Sdk	`18.10.0`	NukeBuildHelpers.UnitTest/NukeBuildHelpers.UnitTest.csproj
NuGet	xunit	`2.9.3`	NukeBuildHelpers.UnitTest/NukeBuildHelpers.UnitTest.csproj
NuGet	xunit.runner.visualstudio	`4.0.0`	NukeBuildHelpers.UnitTest/NukeBuildHelpers.UnitTest.csproj
NuGet	coverlet.collector	`10.0.1`	NukeBuildHelpers.UnitTest/NukeBuildHelpers.UnitTest.csproj
NuGet	Nuke.Common	`9.0.4`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	Nuke.Common	`10.0.0`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	Semver	`3.0.0`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	Sharprompt	`3.1.2`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	YamlDotNet	`18.1.0`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	Microsoft.Build	`17.11.48`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	Microsoft.Build.Tasks.Core	`17.11.48`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	Microsoft.Build.Utilities.Core	`17.11.48`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	System.Security.Cryptography.Xml	`10.0.11`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	Microsoft.Build	`17.12.50`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	Microsoft.Build.Tasks.Core	`18.9.6`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	Microsoft.Build.Utilities.Core	`18.9.6`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	System.Security.Cryptography.Xml	`10.0.11`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	System.Security.Cryptography.Xml	`10.0.11`	NukeBuildHelpers/NukeBuildHelpers.csproj
NuGet	Nuke.Common	`10.0.0`	build/_build.csproj
NuGet	NuGet.Packaging	`7.3.1`	build/_build.csproj

All dependencies 18

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

Registry	Package	Version	Relation
NuGet	coverlet.collector	`10.0.1`	direct
NuGet	GitHubActionsTestLogger	`3.0.5`	direct
NuGet	Microsoft.Build	`17.11.48`	direct
NuGet	Microsoft.Build	`17.12.50`	direct
NuGet	Microsoft.Build.Tasks.Core	`17.11.48`	direct
NuGet	Microsoft.Build.Tasks.Core	`18.9.6`	direct
NuGet	Microsoft.Build.Utilities.Core	`17.11.48`	direct
NuGet	Microsoft.Build.Utilities.Core	`18.9.6`	direct
NuGet	Microsoft.NET.Test.Sdk	`18.10.0`	direct
NuGet	NuGet.Packaging	`7.3.1`	direct
NuGet	Nuke.Common	`10.0.0`	direct
NuGet	Nuke.Common	`9.0.4`	direct
NuGet	Semver	`3.0.0`	direct
NuGet	Sharprompt	`3.1.2`	direct
NuGet	System.Security.Cryptography.Xml	`10.0.11`	direct
NuGet	xunit	`2.9.3`	direct
NuGet	xunit.runner.visualstudio	`4.0.0`	direct
NuGet	YamlDotNet	`18.1.0`	direct

Dependency advisories 1

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

Package	Version	Relation	Severity	Advisories	Fixed in
Microsoft.Build.Tasks.Core	`17.11.48`	direct	high	1	`17.14.8`

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.

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 — NuGet.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records