Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-09 16:20 UTC

Jypeli-JYU / Jypeli

A simple educational C# game programming library built on top of Silk.NET.

C#Custom license★ 31 stars⑂ 6 forkssince Sep 2018View on GitHub ↗
KindLibraryMobile applicationhow this is determined

Jypeli-JYU/Jypeli holds a health index of 47 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (59/100) and lowest on Vitality (31/100). It was last updated today. A single contributor accounts for most of its recent work.

47
overall / 100
Weak

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.

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

Ownership

Jypeli-JYUOrganization
1 follower1 public reposince Sep 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
NuGetJypeli.NET11.5.0-440 days ago
NuGetJypeli.FarseerPhysics.NET2.0.10-200 days ago

Metrics by category

Vitality

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

31At Risk · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
2.1/36Commit cadence — 3/52 weeks with commits
7.6/18Commit volume — 6 commits in the last year
5/10OpenSSF Scorecard: Maintained — 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year6
human_commit_share1
days_since_last_push0
active_weeks_last_year3
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

44Weak · 17% of overall
How it's scored
24/60Stars — 31 stars
5.8/25Forks — 6 forks
2.7/15Watchers — 4 watchers
Inputs used
forks6
stars31
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
51.6/80Total downloads — 92,136 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesJypeli.NET
dependents—
ecosystemsnuget
total_downloads92,136
monthly_downloads—
unverified_packages_excludedJypeli.FarseerPhysics.NET
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.1/22.5Commit distribution — top contributor authored 77% of commits
10.8/13.5Contributor breadth — 8 contributors
10/10OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.772
How it's scored
28.7/42Issue resolution — 68% of issues closed
27.6/30PR acceptance — 23/25 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 2/27 approved changesets -- score normalized to 0
Inputs used
merged_prs23
open_issues6
closed_issues13
prs_merged_7d4
prs_decided_7d4
prs_merged_30d4
prs_decided_30d4
issue_closed_ratio0.684
closed_unmerged_prs2
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
2.2/25Owner reach — 1 followers of Jypeli-JYU
14.2/25Track record — 1 public repos, account ~8 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_loginJypeli-JYU
public_repos1
account_age_days2,937

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on nuget
35/35Publish recency — latest publish 0 days ago
20/20Version history — 44 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesJypeli.NET, Jypeli.FarseerPhysics.NET
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 6 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicsjypeli, c-sharp, game-development, education, android
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 2/27 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 8 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
3.8/7.5Maintained — 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.8
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/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_packages15
unassessed_packages2
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 15 resolved dependencies against OSV. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

58Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
9.1/40Legible commit history — 17 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.17
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Examples/Koripallo/Koripallo.csproj, Examples/Marswagen/Marswagen.csproj, Examples/Pong/Pong.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
0/10Reproducible environment
10/10Demonstrated agent practice — 6 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.06
toolchain_manifestsExamples/Koripallo/Koripallo.csproj, Examples/Marswagen/Marswagen.csproj, Examples/Pong/Pong.csproj, FarseerPhysics/FarseerPhysics.csproj, Jypeli/Jypeli.csproj, Physics2d/Jypeli.Physics2d.csproj, Projektimallit/Jypeli.Templates/Jypeli.Templates.csproj, Projektimallit/Jypeli.Templates/content/AndroidFysiikkapeli/AndroidFysiikkapeli.csproj, Projektimallit/Jypeli.Templates/content/ConsoleMain/ConsoleMain.csproj, Projektimallit/Jypeli.Templates/content/Fysiikkapeli/Fysiikkapeli.csproj, Projektimallit/Jypeli.Templates/content/Peruspeli/Peruspeli.csproj, Projektimallit/Jypeli.Templates/content/Tasohyppely/Tasohyppelypeli.csproj, SimplePhysics/Jypeli.SimplePhysics.csproj, Tests/AccelerometerTest/AccelerometerTestAndroid/AccelerometerTest.csproj, Tests/DataStorageTest/DataStorageTest/DataStorageTest.csproj, Tests/Jypeli.Tests/Jypeli.Tests.csproj, Tests/Net6Android/Net6Android.csproj, Tests/TasohyppelypeliFarseer/Norsupeli/Tasohyppelypeli.csproj
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — C# (statically typed)
54.7/55Manageable file sizes — 3/504 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes65,528
source_files_sampled504
oversized_source_files3
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

31GitHub stars
8contributors
6commits, last 12 months
0days since last push
0releases
1bus factor
6open issues
NuGetpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch nuget package 'Jypeli.Physics2d.NET' from its registry
  • Could not fetch nuget package 'Jypeli.SimplePhysics.Core' from its registry

More detail

Star and fork history 0 ★ / 6 ⇿
0Stars
6Forks

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.

123456612020-022023-042026-06

Each point covers 6 days.

OpenSSF Scorecard 3.8 / 10
3.8aggregate

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-10-09 16:20 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
0CI-Tests0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/27 approved changesets -- score normalized to 0
10Contributorsproject has 8 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
5Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
NuGetFontStashSharp.PlatformAgnostic1.5.0Jypeli/Jypeli.csproj
NuGetSilk.NET.Input2.22.0Jypeli/Jypeli.csproj
NuGetSilk.NET.OpenGL2.22.0Jypeli/Jypeli.csproj
NuGetSilk.NET.Windowing2.22.0Jypeli/Jypeli.csproj
NuGetStbImageSharp2.30.16Jypeli/Jypeli.csproj
NuGetStbImageWriteSharp1.16.7Jypeli/Jypeli.csproj
NuGetSilk.NET.OpenGL.Extensions.ImGui2.17.0Jypeli/Jypeli.csproj
NuGetSilk.NET.OpenAL2.22.0Jypeli/Jypeli.csproj
NuGetSilk.NET.OpenAL.Soft.Native1.23.1Jypeli/Jypeli.csproj
NuGetSystem.Text.Json8.0.5Jypeli/Jypeli.csproj
NuGetXamarin.Essentials1.8.1Jypeli/Jypeli.csproj
NuGetMonoGame.Framework.DesktopGL.Core3.7.0.7SimplePhysics/Jypeli.SimplePhysics.csproj
All dependencies 17

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

RegistryPackageVersionRelation
NuGetFontStashSharp.PlatformAgnostic1.5.0direct
NuGetMonoGame.Framework.DesktopGL.Core3.7.0.7direct
NuGetSilk.NET.Input2.22.0direct
NuGetSilk.NET.OpenAL2.22.0direct
NuGetSilk.NET.OpenAL.Soft.Native1.23.1direct
NuGetSilk.NET.OpenGL2.22.0direct
NuGetSilk.NET.OpenGL.Extensions.ImGui2.17.0direct
NuGetSilk.NET.Windowing2.22.0direct
NuGetStbImageSharp2.30.16direct
NuGetStbImageWriteSharp1.16.7direct
NuGetSystem.Text.Json8.0.5direct
NuGetXamarin.Essentials1.8.1direct
NuGetJypeli.FarseerPhysics.NET—indirect
NuGetJypeli.NET—indirect
NuGetMicrosoft.NET.Test.Sdk17.11.1indirect
NuGetNUnit3.13.2indirect
NuGetNUnit3TestAdapter4.6.0indirect
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. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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