RepoTrust

Leaderboard github.com

kimchiman52/sonic-mania-mister

Experimental port of Sonic Mania to MiSTer FPGA

  • View repository ↗
  • C
  • ★ 42
  • commit 29ea029e7738
  • scored 2026-11-13
  • scoring prov-4+qual-2+sec-2

AI provenance

0%

explicit

Confidence
95%
Coverage
100%

Estimated share of AI-generated code. Explicit attribution is a lower bound.

Code quality

51/100

weak

Confidence
90%
Coverage
100%

Complexity, duplication, lint density, tests, CI, docs and review process.

Security

68/100

weak

Confidence
85%
Coverage
100%

Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.

Scores

Pillar Score Signal Confidence Coverage
AI provenance (estimated AI-generated share) 0 explicit 95% 100%
Code quality 51 weak 90% 100%
Security 68 weak 85% 100%

AI provenance

Explicit AI attribution on 0% of first-party code added; an estimated 0% including velocity signals.

  • Explicitly attributed share (lower bound): 0.4%
  • Unattributed share in AI-consistent velocity bursts: 14.6%
  • Estimated AI-generated share: 0.4%
AI tool Attributed commits Lines added
Claude Code 79 3,351

Current source lines last changed by AI-attributed commits: 3,038 of 291,688.

Findings per 1,000 lines AI-attributed Other Ratio
Quality 0.0 0.031 0.0x
Security 1.317 0.388 3.39x
  • Stylometry index: 0.00 per 1,000 lines (narrated steps 0, placeholders 0, assistant phrasing 0, emoji 1). Reported as a signal, not scored.
Month Lines added Attributed to AI
2024-11 2 0%
2024-12 21 0%
2025-03 212 0%
2025-05 14 0%
2025-06 1 0%
2025-07 1 0%
2025-08 3 0%
2025-11 5 0%
2026-01 11 0%
2026-02 124 0%
2026-03 6 0%
2026-04 3,393 99%

Evidence

  • Claude Code: trailer 'Co-Authored-By: Claude' (29ea029e7738)
  • Claude Code: trailer 'Co-Authored-By: Claude' (e109f257869c)
  • Claude Code: trailer 'Co-Authored-By: Claude' (9ff9e76203a2)
  • Claude Code: trailer 'Co-Authored-By: Claude' (40293c6668e9)
  • Claude Code: trailer 'Co-Authored-By: Claude' (08548cb5937f)
  • Claude Code: trailer 'Co-Authored-By: Claude' (92933d30f13c)
  • Claude Code: trailer 'Co-Authored-By: Claude' (84ee70b8a888)
  • Claude Code: trailer 'Co-Authored-By: Claude' (4d8af604f3d3)
  • Claude Code: trailer 'Co-Authored-By: Claude' (8bc4c6371467)
  • Claude Code: trailer 'Co-Authored-By: Claude' (d3841de6fd0b)
  • Claude Code: trailer 'Co-Authored-By: Claude' (bf1022c5e664)
  • Claude Code: trailer 'Co-Authored-By: Claude' (f74e83be2580)
  • Claude Code: trailer 'Co-Authored-By: Claude' (77917d12c727)
  • Claude Code: trailer 'Co-Authored-By: Claude' (2576c25db624)
  • Claude Code: trailer 'Co-Authored-By: Claude' (4954f2f9b91f)

AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.

Code quality

Code quality is weak: test-to-source ratio 0.00, no CI test run detected; 21% of function code in complex or long functions; 10% duplicated lines. Weakest area: testing.

Area Score
Complexity (lizard) 53
Duplication 56
Code smells (Opengrep) 99
Tests and CI 15
Documentation 65
Type safety 40
Process (Scorecard review/maintenance) n/a
  • Functions: 10,419; mean complexity 3.7, 90th percentile 8; 341 complex and 93 long functions
  • Duplicated lines: 9.5% of 199,651 compared
  • Tests: 0 test lines for 291,688 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
  • Docs missing or thin: contributing, changelog

Most complex functions:

Security

Security posture is weak: 6 high-severity workflow issues. Weakest area: posture.

Area Score
Secrets (gitleaks, tree + history) 100
Static analysis (Opengrep) 96
Vulnerable dependencies (OSV) n/a
CI workflows (zizmor) 24
Posture (policy, updates, signing, lockfiles) 0
OpenSSF Scorecard n/a
  • Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits

Top findings

Severity Finding Location
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/build.yml:27
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/build.yml:44
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/build.yml:52
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/build.yml:69
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/build.yml:77
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/build.yml:94
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Game.c:52
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Game.c:80
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Game.c:81
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Game.c:118
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/AIZ/FernParallax.c:67
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/AIZ/SchrodingersCapsule.c:220
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/AIZ/SchrodingersCapsule.c:243
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/BSS/BSS_Setup.c:97
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/BSS/BSS_Setup.c:98
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/BSS/BSS_Setup.c:99
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/CPZ/DNARiser.c:475
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/CPZ/DNARiser.c:546
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/Global/APICallback.c:307
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/Global/Competition.c:245
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/Global/Localization.c:107
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/Global/ReplayRecorder.c:173
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/Global/ReplayRecorder.c:276
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/Global/ReplayRecorder.c:279
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] SonicMania/Objects/Global/ReplayRecorder.c:462

Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.

Distribution signals

Signals consistent with a repository that exists to distribute a download. They are heuristics, not a verdict; release files were not downloaded or inspected.

Repository profile

  • Source lines: 291,688; test lines: 0
Language Lines
C 289,113
Shell 2,175
Python 400

Embed a badge

Maintainers can show these in a README. Badges update when the repository is re-scored.

[![RepoTrust ai](https://repotrust.synapticcyber.com/badge/github.com/kimchiman52/sonic-mania-mister/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/kimchiman52/sonic-mania-mister/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/kimchiman52/sonic-mania-mister/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/kimchiman52/sonic-mania-mister/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/kimchiman52/sonic-mania-mister/security.svg)](https://repotrust.synapticcyber.com/r/github.com/kimchiman52/sonic-mania-mister/)