Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-20 09:59 UTC

ParadoxGameConverters / PGCG.commonItems

Common utilities for Paradox game converters written for .NET platform.

C#MIT★ 5 stars⑂ 2 forkssince Jul 2021View on GitHub ↗

ParadoxGameConverters/PGCG.commonItems holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Vitality (92/100) and lowest on Community & Adoption (30/100). It was last updated 3 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

153 followers41 public repossince Sep 2018

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

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
31.8/36Commit cadence — 46/52 weeks with commits
18/18Commit volume — 204 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year204
human_commit_share0.17
days_since_last_push3
active_weeks_last_year46
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 3 days ago
27/27Release cadence — a release every ~26.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag23.3.1
releases_from_tagsyes
days_since_latest_release3
mean_days_between_releases26.7

Community & Adoption

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

30At Risk · 17% of overall
How it's scored
9.8/60Stars — 5 stars
0/25Forks — 2 forks
1.7/15Watchers — 3 watchers
Inputs used
forks2
stars5
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesapp.codacy.com, coveralls.io
has_pull_request_templateno

Sustainability & Governance

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

56Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.2/22.5Commit distribution — top contributor authored 99% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.992
How it's scored
37.7/42Issue resolution — 90% of issues closed
27.6/30PR acceptance — 868/942 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs868
open_issues3
closed_issues26
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.897
closed_unmerged_prs74
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 backing — organization-owned
0/20Verified domain
15.7/25Owner reach — 153 followers of ParadoxGameConverters
23.8/25Track record — 41 public repos, account ~8 yr old
Inputs used
followers153
owner_typeOrganization
is_verifiedno
owner_loginParadoxGameConverters
public_repos41
account_age_days3,001

Engineering Quality

Are baseline engineering and documentation practices in place?

49Weak · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://nuget.org/packages/PGCG.commonItems/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://nuget.org/packages/PGCG.commonItems/
docs_sitehttps://nuget.org/packages/PGCG.commonItems/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestscommonItems.UnitTests/commonItems.UnitTests.csproj, commonItems/commonItems.csproj
has_codeql_workflowno
has_security_policyno
has_dependabot_configyes

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no 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.

34At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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
12.6/18One-command bootstrap — commonItems.UnitTests/commonItems.UnitTests.csproj, commonItems/commonItems.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 83 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestscommonItems.UnitTests/commonItems.UnitTests.csproj, commonItems/commonItems.csproj
dependency_bot_commit_share0.83
How it's scored
45/45Type-checkable code — C# (statically typed)
55/55Manageable file sizes — 0/93 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes38,528
source_files_sampled93
oversized_source_files0

Key facts

5GitHub stars
3contributors
204commits, last 12 months
3days since last push
100releases
1bus factor
3open issues
NuGetpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/ParadoxGameConverters/PGCG.commonItems: run: repo unreachable: Get "https://api.github.com/repos/ParadoxGameConverters/PGCG.commonItems": internal error: innerTransport.RoundTrip: internal error: innerTransport.RoundTrip: error in HTTP: dial tcp: lookup api.github.com on 127.0.0.11:53: server misbehaving); skipping Scorecard checks

More detail

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

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.

111222212021-072023-012024-08
Major 3Minor 10Patch 25

Each point covers 3 days.

Direct dependencies 16
RegistryPackageVersion constraintManifest
NuGetAwesomeAssertions9.6.0commonItems.UnitTests/commonItems.UnitTests.csproj
NuGetMeziantou.Analyzer3.0.324commonItems.UnitTests/commonItems.UnitTests.csproj
NuGetPGCG.commonItems.SourceGenerators1.0.9commonItems.UnitTests/commonItems.UnitTests.csproj
NuGetcoverlet.msbuild10.1.1commonItems.UnitTests/commonItems.UnitTests.csproj
NuGetCsv3.0.0commonItems.UnitTests/commonItems.UnitTests.csproj
NuGetRoslynator.Analyzers5.0.1commonItems.UnitTests/commonItems.UnitTests.csproj
NuGetxunit.v3.mtp-v24.0.3commonItems.UnitTests/commonItems.UnitTests.csproj
NuGetcoverlet.collector10.1.1commonItems.UnitTests/commonItems.UnitTests.csproj
NuGetcoverlet.MTP10.1.1commonItems.UnitTests/commonItems.UnitTests.csproj
NuGetAnyAscii0.3.3commonItems/commonItems.csproj
NuGetColorHashSharp1.1.0commonItems/commonItems.csproj
NuGetGameFinder.StoreHandlers.GOG4.9.0commonItems/commonItems.csproj
NuGetGameFinder.StoreHandlers.Steam4.9.0commonItems/commonItems.csproj
NuGetHardware.Info.Aot110.0.0.1commonItems/commonItems.csproj
NuGetlog4net3.6.0commonItems/commonItems.csproj
NuGetNCalcSync7.1.0commonItems/commonItems.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
NuGetAnyAscii0.3.3direct
NuGetAwesomeAssertions9.6.0direct
NuGetColorHashSharp1.1.0direct
NuGetcoverlet.collector10.1.1direct
NuGetcoverlet.msbuild10.1.1direct
NuGetcoverlet.MTP10.1.1direct
NuGetCsv3.0.0direct
NuGetGameFinder.StoreHandlers.GOG4.9.0direct
NuGetGameFinder.StoreHandlers.Steam4.9.0direct
NuGetHardware.Info.Aot110.0.0.1direct
NuGetlog4net3.6.0direct
NuGetMeziantou.Analyzer3.0.324direct
NuGetNCalcSync7.1.0direct
NuGetPGCG.commonItems.SourceGenerators1.0.9direct
NuGetRoslynator.Analyzers5.0.1direct
NuGetxunit.v3.mtp-v24.0.3direct
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.34.0 — full methodology · metrics wiki.

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