Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-18 21:29 UTC

Tyrrrz / PowerKit

Collection of general-purpose utilities and extensions

C#MIT★ 7 stars⑂ 1 forksince Apr 2026View on GitHub ↗

Tyrrrz/PowerKit holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Vitality (78/100) and lowest on AI Readiness (26/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Oleksii HolubPersonal account
2,901 followers40 public repossince Jul 2012

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?

78Good · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
5.5/36Commit cadence8/52 weeks with commits
18/18Commit volume122 commits in the last year
10/10OpenSSF Scorecard: Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year122
human_commit_share
days_since_last_push2
active_weeks_last_year8
How it's scored
27/27Ships releases8 releases published
36/36Release recencylatest release 5 days ago
27/27Release cadencea release every ~12.2 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count8
latest_release_tag2.1
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases12.2

Community & Adoption

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

34At Risk · 17% of overall
How it's scored
12.6/60Stars7 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars7
watchers0
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes

Sustainability & Governance

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

54Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.7/22.5Commit distributiontop contributor authored 66% of commits
4.1/13.5Contributor breadth3 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.656
How it's scored
0/42Issue resolutionno issues or no data
29.7/30PR acceptance87/88 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/20 approved changesets -- score normalized to 0
Inputs used
merged_prs87
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs1
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
24.9/25Owner reach2,901 followers of Tyrrrz
23.7/25Track record40 public repos, account ~14 yr old
Inputs used
followers2,901
owner_typeUser
is_verified
owner_loginTyrrrz
public_repos40
account_age_days5,124
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

51Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests13 out of 14 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://nuget.org/packages/PowerKit
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicsdotnet, extensions
has_wikino
homepagehttps://nuget.org/packages/PowerKit
docs_sitehttps://nuget.org/packages/PowerKit
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.2/2.5CI-Tests13 out of 14 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/20 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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.5Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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.
6.8/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_aggregate5.3
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

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.

26At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/144 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes8,228
source_files_sampled144
oversized_source_files0

Key facts

7GitHub stars
3contributors
122commits, last 12 months
2days since last push
8releases
1bus factor
0open issues
NuGetpackage ecosystems

More detail

OpenSSF Scorecard 5.3 / 10
5.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-07-18 21:29 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests13 out of 14 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/20 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
10Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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.
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
NuGetCSharpier.MsBuildPowerKit.Tests/PowerKit.Tests.csproj
NuGetcoverlet.collectorPowerKit.Tests/PowerKit.Tests.csproj
NuGetGitHubActionsTestLoggerPowerKit.Tests/PowerKit.Tests.csproj
NuGetFluentAssertionsPowerKit.Tests/PowerKit.Tests.csproj
NuGetGressPowerKit.Tests/PowerKit.Tests.csproj
NuGetMicrosoft.NET.Test.SdkPowerKit.Tests/PowerKit.Tests.csproj
NuGetxunitPowerKit.Tests/PowerKit.Tests.csproj
NuGetxunit.runner.visualstudioPowerKit.Tests/PowerKit.Tests.csproj
NuGetXunit.SkippableFactPowerKit.Tests/PowerKit.Tests.csproj
NuGetCSharpier.MsBuildPowerKit/PowerKit.csproj
NuGetMicrosoft.Bcl.AsyncInterfacesPowerKit/PowerKit.csproj
NuGetPolyShimPowerKit/PowerKit.csproj
NuGetSnekPowerKit/PowerKit.csproj
NuGetSystem.MemoryPowerKit/PowerKit.csproj
All dependencies 13

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

RegistryPackageVersionRelation
NuGetcoverlet.collectordirect
NuGetCSharpier.MsBuilddirect
NuGetFluentAssertionsdirect
NuGetGitHubActionsTestLoggerdirect
NuGetGressdirect
NuGetMicrosoft.Bcl.AsyncInterfacesdirect
NuGetMicrosoft.NET.Test.Sdkdirect
NuGetPolyShimdirect
NuGetSnekdirect
NuGetSystem.Memorydirect
NuGetxunitdirect
NuGetxunit.runner.visualstudiodirect
NuGetXunit.SkippableFactdirect
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.14.0 — full methodology · metrics wiki.

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