Leaderboard github.com
LeZergan/mcsm-vita
Minecraft: Story Mode PS Vita loader — public prerelease with an easy Windows data builder.
unreviewed-ai-risk
AI provenance
52%
explicit
- Confidence
- 91%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
58/100
weak
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
79/100
adequate
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
- Repository: https://github.com/LeZergan/mcsm-vita
- Commit:
627e16893f4a857dd6f6f93d9dbc04f4b8a2dc82 - Generated: 2026-11-13T23:47:58+00:00
- Scorer 0.1.0, scoring prov-4+qual-2+sec-2, report schema v2
Scores
Unreviewed AI code risk: a large share of this code is explicitly AI-attributed, and its tests or review process are weak while quality or security scores are low.
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 52 | explicit | 91% | 100% |
| Code quality | 58 | weak | 90% | 100% |
| Security | 79 | adequate | 85% | 100% |
AI provenance
Explicit AI attribution on 52% of first-party code added; an estimated 52% including velocity signals.
- Explicitly attributed share (lower bound): 51.6%
- Unattributed share in AI-consistent velocity bursts: 9.3%
- Estimated AI-generated share: 51.6%
| AI tool | Attributed commits | Lines added |
|---|---|---|
| Claude Code | 45 | 44,088 |
Current source lines last changed by AI-attributed commits: 28,870 of 37,887.
| Findings per 1,000 lines | AI-attributed | Other | Ratio |
|---|---|---|---|
| Quality | 0.589 | 0.222 | 2.65x |
| Security | 1.108 | 0.444 | 2.5x |
- Stylometry index: 0.03 per 1,000 lines (narrated steps 1, placeholders 0, assistant phrasing 0, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2026-07 | 41,126 | 97% |
| 2026-08 | 44,280 | 9% |
Evidence
- Claude Code: trailer 'Co-Authored-By: Claude' (627e16893f4a)
- Claude Code: trailer 'Co-Authored-By: Claude' (4c308d790b89)
- Claude Code: trailer 'Co-Authored-By: Claude' (5787d610f76b)
- Claude Code: trailer 'Co-Authored-By: Claude' (661f98e5cef0)
- Claude Code: trailer 'Co-Authored-By: Claude' (a3da37316552)
- Claude Code: trailer 'Co-Authored-By: Claude' (c72093df0d0d)
- Claude Code: trailer 'Co-Authored-By: Claude' (fe1a967c7d0b)
- Claude Code: trailer 'Co-Authored-By: Claude' (6a9f2468b547)
- Claude Code: trailer 'Co-Authored-By: Claude' (c6c6c9f8ed81)
- Claude Code: trailer 'Co-Authored-By: Claude' (556c409e8e57)
- Claude Code: trailer 'Co-Authored-By: Claude' (b9168441be46)
- Claude Code: trailer 'Co-Authored-By: Claude' (c100efa2f2bf)
- Claude Code: trailer 'Co-Authored-By: Claude' (da9d4717b792)
- Claude Code: trailer 'Co-Authored-By: Claude' (c09693d566b9)
- Claude Code: trailer 'Co-Authored-By: Claude' (479e69d73ec3)
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.02, no CI test run detected; 22% of function code in complex or long functions; 3% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 52 |
| Duplication | 86 |
| Code smells (Opengrep) | 89 |
| Tests and CI | 27 |
| Documentation | 65 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 1,223; mean complexity 5.0, 90th percentile 11; 54 complex and 11 long functions
- Duplicated lines: 2.6% of 29,149 compared
- Tests: 597 test lines for 37,887 source lines (ratio 0.02); CI test commands: none detected; 16% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Most complex functions:
- load_cfg in source/utils/config.c: complexity 220, 227 lines
- glTexImage2D_soloader in source/utils/glutil.c: complexity 70, 206 lines
- gl_swap in source/utils/glutil.c: complexity 54, 147 lines
- watchdog_thread in source/main.c: complexity 43, 135 lines
- load_game in source/utils/config.c: complexity 41, 59 lines
Security
Security posture is adequate: no high-impact findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 92 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| 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 |
|---|---|---|
| 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] |
lib/sha1/sha1.c:125 |
| 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] |
source/java.c:365 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
source/java.c:763 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
source/java.c:767 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
source/patch.c:5553 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
source/reimpl/bits/_struct_converters.c:68 |
| 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] |
source/reimpl/egl.c:87 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
source/reimpl/fmod_output_vita.c:308 |
| 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] |
source/reimpl/fmod_output_vita.c:402 |
| 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] |
source/reimpl/io.c:967 |
| 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] |
source/reimpl/mem.c:376 |
| 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] |
source/reimpl/mem.c:379 |
| 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] |
source/reimpl/sys.c:136 |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] |
source/reimpl/sys.c:146 |
| 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] |
source/reimpl/sys.c:507 |
| 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] |
source/reimpl/sys.c:517 |
| 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] |
source/reimpl/time64.c:364 |
| 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] |
source/reimpl/time64.c:396 |
| 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] |
source/reimpl/time64.c:433 |
| 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] |
source/reimpl/time64.c:451 |
| 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] |
source/utils/dialog.c:108 |
| 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] |
source/utils/dialog.c:142 |
| 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] |
source/utils/dialog.c:259 |
| medium | opengrep/c.lang.security.insecure-use-strcat-fn: Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] |
source/utils/glutil.c:256 |
| medium | opengrep/c.lang.security.insecure-use-strcat-fn: Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] |
source/utils/glutil.c:259 |
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
- binary-release-asset: release v1.11 ships MCSM-Vita-Data-Builder-v1.9.exe (363 downloads)
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: 37,887; test lines: 597
| Language | Lines |
|---|---|
| C | 31,616 |
| C# | 6,220 |
| C++ | 353 |
| PowerShell | 292 |
| Shell | 3 |