Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 09:50 UTC

kyleherzog / Blazicons.Generating

C#MIT★ 0 stars⑂ 2 forkssince Dec 2022View on GitHub ↗

kyleherzog/Blazicons.Generating holds a health index of 29 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (54/100) and lowest on Vitality (14/100). It was last updated 182 days ago. A single contributor accounts for most of its recent work.

overall / 100

At Risk

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

Ownership

Kyle HerzogPersonal account

6 followers34 public repossince Jan 2015Wells Enterprises

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	Blazicons.Generating	3.3.35	-	8	182 days ago	blazor code generation

Metrics by category

Vitality

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

14Critical · 21% of overall

Development activity

22At Risk

How it's scored

3.6/36	Push recency — last push 182 days ago
3.5/36	Commit cadence — 5/52 weeks with commits
14.4/18	Commit volume — 39 commits in the last year
0/10	OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Inputs used

commits_last_year	39
human_commit_share	1
days_since_last_push	182
active_weeks_last_year	5

Release discipline

1Critical

How it's scored

0/27	Ships releases — no releases published
0/36	Release recency — no releases
0/27	Release cadence — no releases
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count

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?

31At Risk · 17% of overall

Popularity & adoption

1Critical

How it's scored

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

Inputs used

forks	2
stars	0
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	2
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	dev.azure.com, shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

52Moderate

How it's scored

41.9/80	Total downloads — 10,835 downloads all-time across nuget
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	Blazicons.Generating
dependents	—
ecosystems	nuget
total_downloads	10,835
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)

15Critical

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	2
top_contributor_share	0.968

Issue & PR responsiveness

78Good

How it's scored

42/42	Issue resolution — 100% of issues closed
25.7/30	PR acceptance — 12/14 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/5 approved changesets -- score normalized to 0

Inputs used

merged_prs	12
open_issues	0
closed_issues	2
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	1
closed_unmerged_prs	2
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): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

49Weak

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
6.1/25	Owner reach — 6 followers of kyleherzog
23.2/25	Track record — 34 public repos, account ~11 yr old

Inputs used

followers	6
owner_type	User
is_verified	—
owner_login	kyleherzog
public_repos	34
account_age_days	4,248

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

Package maintenance

91Excellent

How it's scored

25/25	Published & resolvable — 1 package(s) on nuget
26/35	Publish recency — latest publish 182 days ago
20/20	Version history — 8 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	Blazicons.Generating
ecosystems	nuget
any_deprecated	no
min_days_since_publish	182

Engineering Quality

Are baseline engineering and documentation practices in place?

32At Risk · 19% of overall

Engineering practices

26At Risk

How it's scored

0/24	CI workflows
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 — 5 out of 5 merged PRs checked by a CI test -- score normalized to 10

Inputs used

has_ci	no
has_tests	no
has_editorconfig	yes
has_linter_config	no
has_precommit_config	no

Documentation

40Weak

How it's scored

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

Inputs used

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

Security

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

46Weak · 16% of overall

Security posture

33At Risk

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
2.5/2.5	CI-Tests — 5 out of 5 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/5 approved changesets -- score normalized to 0
0.8/2.5	Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10	Dangerous-Workflow — no data
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
0/7.5	Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
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 — no data
0/7.5	Token-Permissions — no data
7.5/7.5	Vulnerabilities — 0 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	12
scorecard_version	v5.5.0
checks_inconclusive	6
scorecard_aggregate	3.3

Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	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	0
affected_packages	0
assessed_packages	15
unassessed_packages	0
affected_by_severity	none
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 15 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.

33At Risk · 4% of overall

Agent context & guidance

8Critical

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.14
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

26At Risk

How it's scored

12.6/18	One-command bootstrap — Blazicons.Generating.IntegrationTests/Blazicons.Generating.IntegrationTests.csproj, Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj, Blazicons.Generating/Blazicons.Generating.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
0/10	Demonstrated agent practice — no agent-authored commits among the last 93
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

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
toolchain_manifests	Blazicons.Generating.IntegrationTests/Blazicons.Generating.IntegrationTests.csproj, Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj, Blazicons.Generating/Blazicons.Generating.csproj
dependency_bot_commit_share	0

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

100Exceptional

How it's scored

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

Inputs used

primary_language	C#
largest_source_bytes	10,995
source_files_sampled	16
oversized_source_files	0

Key facts

0GitHub stars

2contributors

39commits, last 12 months

182days since last push

0releases

1bus factor

0open issues

NuGetpackage ecosystems

More detail

Star and fork history 0 ★ / 2 ⇿

0Stars

2Forks

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.

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-09-14 09:49 UTC

10	Binary-Artifacts	no binaries found in the repo
n/a	Branch-Protection	internal 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
10	CI-Tests	5 out of 5 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/5 approved changesets -- score normalized to 0
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
n/a	Dangerous-Workflow	no workflows found
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
0	Maintained	0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
10	Vulnerabilities	0 existing vulnerabilities detected

Direct dependencies 29

Registry	Package	Version constraint	Manifest
NuGet	Microsoft.CodeAnalysis.NetAnalyzers	`10.0.201`	Blazicons.Generating.IntegrationTests/Blazicons.Generating.IntegrationTests.csproj
NuGet	Microsoft.NET.Test.Sdk	`18.3.0`	Blazicons.Generating.IntegrationTests/Blazicons.Generating.IntegrationTests.csproj
NuGet	Microsoft.VisualStudio.Threading.Analyzers	`17.14.15`	Blazicons.Generating.IntegrationTests/Blazicons.Generating.IntegrationTests.csproj
NuGet	MSTest.TestAdapter	`4.1.0`	Blazicons.Generating.IntegrationTests/Blazicons.Generating.IntegrationTests.csproj
NuGet	MSTest.TestFramework	`4.1.0`	Blazicons.Generating.IntegrationTests/Blazicons.Generating.IntegrationTests.csproj
NuGet	coverlet.collector	`8.0.0`	Blazicons.Generating.IntegrationTests/Blazicons.Generating.IntegrationTests.csproj
NuGet	SecurityCodeScan.VS2019	`5.6.7`	Blazicons.Generating.IntegrationTests/Blazicons.Generating.IntegrationTests.csproj
NuGet	SonarAnalyzer.CSharp	`10.21.0.135717`	Blazicons.Generating.IntegrationTests/Blazicons.Generating.IntegrationTests.csproj
NuGet	Text.Analyzers	`3.3.4`	Blazicons.Generating.IntegrationTests/Blazicons.Generating.IntegrationTests.csproj
NuGet	coverlet.collector	`8.0.0`	Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj
NuGet	Microsoft.NET.Test.Sdk	`18.3.0`	Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj
NuGet	MSTest.TestAdapter	`4.1.0`	Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj
NuGet	MSTest.TestFramework	`4.1.0`	Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj
NuGet	Verify.MSTest	`31.13.2`	Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj
NuGet	Microsoft.CodeAnalysis.NetAnalyzers	`10.0.201`	Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj
NuGet	Microsoft.VisualStudio.Threading.Analyzers	`17.14.15`	Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj
NuGet	SecurityCodeScan.VS2019	`5.6.7`	Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj
NuGet	SonarAnalyzer.CSharp	`10.21.0.135717`	Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj
NuGet	Text.Analyzers	`3.3.4`	Blazicons.Generating.UnitTests/Blazicons.Generating.UnitTests.csproj
NuGet	CodeCasing	`4.0.5`	Blazicons.Generating/Blazicons.Generating.csproj
NuGet	HtmlAgilityPack	`1.12.4`	Blazicons.Generating/Blazicons.Generating.csproj
NuGet	Microsoft.Build.Utilities.Core	`18.4.0`	Blazicons.Generating/Blazicons.Generating.csproj
NuGet	Microsoft.VisualStudio.Threading	`17.14.15`	Blazicons.Generating/Blazicons.Generating.csproj
NuGet	Microsoft.CodeAnalysis.NetAnalyzers	`10.0.201`	Blazicons.Generating/Blazicons.Generating.csproj
NuGet	Microsoft.SourceLink.GitHub	`10.0.201`	Blazicons.Generating/Blazicons.Generating.csproj
NuGet	Microsoft.VisualStudio.Threading.Analyzers	`17.14.15`	Blazicons.Generating/Blazicons.Generating.csproj
NuGet	SecurityCodeScan.VS2019	`5.6.7`	Blazicons.Generating/Blazicons.Generating.csproj
NuGet	SonarAnalyzer.CSharp	`10.21.0.135717`	Blazicons.Generating/Blazicons.Generating.csproj
NuGet	Text.Analyzers	`3.3.4`	Blazicons.Generating/Blazicons.Generating.csproj

All dependencies 15

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

Registry	Package	Version	Relation
NuGet	CodeCasing	`4.0.5`	direct
NuGet	coverlet.collector	`8.0.0`	direct
NuGet	HtmlAgilityPack	`1.12.4`	direct
NuGet	Microsoft.Build.Utilities.Core	`18.4.0`	direct
NuGet	Microsoft.CodeAnalysis.NetAnalyzers	`10.0.201`	direct
NuGet	Microsoft.NET.Test.Sdk	`18.3.0`	direct
NuGet	Microsoft.SourceLink.GitHub	`10.0.201`	direct
NuGet	Microsoft.VisualStudio.Threading	`17.14.15`	direct
NuGet	Microsoft.VisualStudio.Threading.Analyzers	`17.14.15`	direct
NuGet	MSTest.TestAdapter	`4.1.0`	direct
NuGet	MSTest.TestFramework	`4.1.0`	direct
NuGet	SecurityCodeScan.VS2019	`5.6.7`	direct
NuGet	SonarAnalyzer.CSharp	`10.21.0.135717`	direct
NuGet	Text.Analyzers	`3.3.4`	direct
NuGet	Verify.MSTest	`31.13.2`	direct

Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 15 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.

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

More detail

Feedback

Related records