Leaderboard github.com
farbrausch/fr_public
Farbrausch demo tools 2001-2011
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
32/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
80/100
adequate
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% none-detected
No AI attribution or AI-consistent velocity signals detected.
How the score is built
- Explicitly attributed share0%
- Unattributed share in AI-pace bursts0%
- Estimated AI-generated share0%
- AI tool configuration files0
- Work sessions at AI pace0
- Releases at AI pacenot measured
- Coding-style index (1.0+ means possible)0.10
Lines added per month all AI-attributed share
- 2012-04825,330 · 0% AI
- 2012-05457 · 0% AI
- 2012-06296 · 0% AI
- 2012-076,690 · 0% AI
- 2012-0830,428 · 0% AI
- 2012-099,118 · 0% AI
- 2012-10404 · 0% AI
- 2012-1151 · 0% AI
- 2012-126,233 · 0% AI
- 2013-0126 · 0% AI
- 2013-037,522 · 0% AI
- 2013-061,147 · 0% AI
- 2013-080 · 0% AI
- 2014-04278 · 0% AI
- 2014-09139,011 · 0% AI
- 2015-03510 · 0% AI
- 2016-03130 · 0% AI
- 2017-04315 · 0% AI
Evidence by analyzer
Explicit AI attributionok
- attributed_commit_share
- 0.0%
- attributed_commits
- 0
- attributed_loc
- 0
- attributed_loc_share
- 0.0%
- commits
- 309
- effective_loc
- 1,027,946
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 927,944
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 6,694.55
- measured_loc
- 100,002
- median_loc_per_hour
- 112.64
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 83,819
- pre_ai_era_bursts
- 10
- pre_ai_era_measured_loc
- 100,002
- work_units
- 146
Release velocityskipped
Coding styleok8 items
- step-by-step narration comment: // Finally, given a filename (or an open file or memory block--see header
- step-by-step narration comment: // Finally, the image data.
- step-by-step narration comment: // now we need to indicate how they correspond; we could either
- step-by-step narration comment: // now we use symbolic names for these, so that we can
- step-by-step narration comment: // now, we can start decoding frames... we'll only FAKE decode them,
- step-by-step narration comment: // now we want to lerp between these for the target samples...
- step-by-step narration comment: // step 1: we need to bias towards the page start...
- step-by-step narration comment: // first, store the current decode position so we can restore it
- count:assistant_voice
- 6
- count:emoji_in_code
- 0
- count:narrated_steps
- 79
- count:placeholder
- 0
- files:assistant_voice
- 6
- files:emoji_in_code
- 0
- files:narrated_steps
- 48
- files:placeholder
- 0
- index
- 0.10
- lines_scanned
- 940,900
- per_kloc:assistant_voice
- 0.01
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0.08
- per_kloc:placeholder
- 0
Code quality
32 poor
Code quality is poor: test-to-source ratio 0.00, no CI test run detected; 34% of function code in complex or long functions; 52% duplicated lines. Weakest area: testing.
How the score is built
- Complexity36
- Duplication4
- Lint and smells100
- Tests and CI0
- Documentation40
- Type safetynot measured
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok10 items
- glewContextInit in Altona2/Altona2/Libs/Base/GraphicsGlew.cpp: complexity 869, 651 lines
- glewIsSupported in Altona2/Altona2/Libs/Base/GraphicsGlew.cpp: complexity 867, 2186 lines
- _glewInit_GL_EXT_direct_state_access in Altona2/Altona2/Libs/Base/GraphicsGlew.cpp: complexity 214, 218 lines
- Altona2::sScanner::Scan in Altona2/Altona2/Libs/Util/Scanner.cpp: complexity 186, 456 lines
- sScanner::Scan in altona_wz4/altona/main/util/scanner.cpp: complexity 168, 408 lines
- WinView::OnCommand in werkkzeug3/winview.cpp: complexity 147, 436 lines
- start_decoder in Altona2/Altona2/Libs/Util/StbVorbis.c: complexity 146, 419 lines
- start_decoder in altona_wz4/altona/main/ogg/stb_vorbis.h: complexity 146, 419 lines
- MsgProc in altona_wz4/altona/main/base/system_win.cpp: complexity 143, 398 lines
- wglewContextInit in Altona2/Altona2/Libs/Base/GraphicsGlew.cpp: complexity 141, 95 lines
- complex_functions
- 1,446
- function_nloc
- 573,503
- functions
- 34,019
- long_functions
- 771
- many_param_functions
- 349
- mean_ccn
- 3.89
- p90_ccn
- 8
- risky_nloc_share
- 33.6%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: Altona2/Altona2/Examples/base/Audio/main.cpp:1 and Altona2/Altona2/Examples/base/Audio/main.hpp:1
- 6+ duplicated lines: Altona2/Altona2/Examples/base/Audio/main.cpp:3 and Altona2/Altona2/Examples/base/cpp11/main.cpp:3
- 6+ duplicated lines: Altona2/Altona2/Examples/base/Audio/main.cpp:14 and Altona2/Altona2/Examples/graphics/DynamicTextureMap/main.cpp:14
- 6+ duplicated lines: Altona2/Altona2/Examples/base/Audio/main.cpp:26 and Altona2/Altona2/Examples/graphics_dx11/ComputeMesh/Main.cpp:24
- 6+ duplicated lines: Altona2/Altona2/Examples/base/Audio/main.cpp:33 and Altona2/Altona2/Examples/graphics/DynamicVertexMap/main.cpp:37
- 6+ duplicated lines: Altona2/Altona2/Examples/base/Audio/main.cpp:36 and Altona2/Altona2/Examples/graphics/DynamicVertexArray/main.cpp:43
- 6+ duplicated lines: Altona2/Altona2/Examples/base/Audio/main.cpp:95 and Altona2/Altona2/Examples/emptyprojects/gui3d/main.hpp:14
- 6+ duplicated lines: Altona2/Altona2/Examples/base/Audio/main.hpp:3 and Altona2/Altona2/Examples/graphics/DynamicTextureMap/main.hpp:3
- 6+ duplicated lines: Altona2/Altona2/Examples/base/Volumes/Main.cpp:3 and Altona2/Altona2/Examples/base/helloworld/main.cpp:3
- 6+ duplicated lines: Altona2/Altona2/Examples/emptyprojects/gui3d/doc.cpp:7 and Altona2/Altona2/Tools/Asc/Doc.cpp:14
- compared_lines
- 658,039
- duplicated_lines
- 340,079
- duplicated_share
- 51.7%
- files
- 1,503
Lintok
- category:correctness
- 2
- findings
- 2
- scanned_lines
- 974,913
- weighted_findings
- 2
Tests and CIok
- check:ci_present
- no
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- no
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 0
- cochange_commits
- 219
- cochange_share
- 0.0%
- source_lines
- 974,913
- test_lines
- 0
- test_ratio
- 0
Documentationok1 item
- README.md
README.md
- check:changelog
- no
- check:contributing
- no
- check:license
- no
- check:readme
- yes
- readme_lines
- 93
Type safetyskipped
Security
80 adequate
Security posture is adequate: no high-impact findings. Weakest area: posture.
How the score is built
- Secrets97
- Static analysis (SAST)99
- Vulnerable dependenciesnot measured
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesskipped
no registry dependencies declared
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 1
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 82
- findings_high
- 0
- findings_low
- 0
- findings_medium
- 82
- parse_errors
- 68
- scanned_lines
- 974,913
- weighted_findings
- 20.50
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok
- check:dependency_updates
- no
- check:lockfiles
- yes
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 0.0%
- unpinned_manifests
- 0
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
84 medium1 low
85 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| medium | opengrep/c.lang.correctness.incorrect-use-ato-fn |
RG2/VideoDlg.h:56 | Avoid the 'ato*()' family of functions. Their use can lead to undefined behavior, integer overflows, and lack of appropriate error handling. Instead prefer the 'strtol*()' family of functions. | Lint |
| medium | opengrep/c.lang.correctness.incorrect-use-ato-fn |
RG2/VideoDlg.h:58 | Avoid the 'ato*()' family of functions. Their use can lead to undefined behavior, integer overflows, and lack of appropriate error handling. Instead prefer the 'strtol*()' family of functions. | Lint |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbDxt.h:152 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbImage.c:1036 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbImage.c:1172 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbImage.c:1996 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbImage.c:1997 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbImage.c:2178 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbImage.c:2193 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbImage.c:2197 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbImage.c:2202 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbImage.c:3836 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:1009 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:2102 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:3361 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:3369 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:3656 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:3688 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:3966 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:4159 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:5087 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:5115 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:5156 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
Altona2/Altona2/Libs/Util/StbVorbis.c:5363 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
RG2/Viewer/math3d_2.h:185 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
RG2/math3d_2.h:276 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
RG2/pool.h:141 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
RG2/pool.h:58 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:1022 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:2111 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:3373 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:3381 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:3668 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:3700 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:3978 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:4171 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:5097 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:5126 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:5167 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/ogg/stb_vorbis.h:5374 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/util/stb_image.c:1118 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/util/stb_image.c:1970 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/util/stb_image.c:1971 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/util/stb_image.c:2154 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/util/stb_image.c:2169 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/util/stb_image.c:2173 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/util/stb_image.c:2178 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
altona_wz4/altona/main/util/stb_image.c:991 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/standalone/multibutton.h:80 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/standalone/multibutton.h:84 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/standalone/wtlblaview.h:1060 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/standalone/wtlblaview.h:246 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
v2/vsti/MachineInterfaceTL.h:688 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/multibutton.h:80 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/multibutton.h:84 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/v2appearance.h:750 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/v2buzz.h:668 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/v2buzz.h:672 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/v2buzz.h:688 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/v2buzz.h:699 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
v2/vsti/v2buzz.h:722 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/v2buzz.h:922 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-strcat-fn |
v2/vsti/v2buzz.h:924 | 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] | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-strcat-fn |
v2/vsti/v2buzz.h:926 | 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] | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/v2view.h:4203 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/v2view.h:4204 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/v2view.h:4205 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/v2view.h:4206 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/wtlblaview.h:1214 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/wtlblaview.h:1326 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/wtlblaview.h:1327 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/wtlblaview.h:1328 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/wtlblaview.h:1329 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/wtlblaview.h:1381 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-strcat-fn |
v2/vsti/wtlblaview.h:1382 | 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] | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-string-copy-fn |
v2/vsti/wtlblaview.h:261 | 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,... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
werkkzeug3/w3texlib/stb_image.c:1068 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
werkkzeug3/w3texlib/stb_image.c:1920 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
werkkzeug3/w3texlib/stb_image.c:1921 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
werkkzeug3/w3texlib/stb_image.c:2102 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
werkkzeug3/w3texlib/stb_image.c:2117 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
werkkzeug3/w3texlib/stb_image.c:2121 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
werkkzeug3/w3texlib/stb_image.c:2126 | 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... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-memset |
werkkzeug3/w3texlib/stb_image.c:941 | 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... | Static analysis (opengrep) |
| low | gitleaks/generic-api-key |
altona_wz4/altona/main/base/system.hpp:756 | Possible generic-api-key secret in the current tree | Secrets (gitleaks) |
Tools and coverage
Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.
| Analyzer | Pillar | Status | Version | Findings | Note |
|---|---|---|---|---|---|
| AI tool configuration | AI provenance | ok | signatures-v1 | 0 | |
| Explicit AI attribution | AI provenance | ok | signatures-v1 | 0 | |
| Release velocity | AI provenance | skipped | — | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-4 | 0 | |
| Complexity (lizard) | Code quality | ok | lizard 1.25.1 | 0 | |
| Documentation | Code quality | ok | — | 0 | |
| Duplication (jscpd) | Code quality | ok | repotrust-dup-w6 | 0 | |
| Lint | Code quality | ok | opengrep 1.33.1; rules f1d2b562b414 | 2 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | skipped | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | skipped | — | 0 | |
| Release downloads | Security | ok | — | 0 | |
| Security posture | Security | ok | — | 0 | |
| Package registries | Security | skipped | — | 0 | no registry dependencies declared |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 82 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 1 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 8c8f82c2ae01 | prov-5+qual-2+sec-2 | 0% | 32 | 80 |
| 2026-11-14 | 8c8f82c2ae01 | prov-4+qual-2+sec-2 | 0% | 32 | 80 |
Full text report
- Repository: https://github.com/farbrausch/fr_public
- Commit:
8c8f82c2ae01133370e649bbc05916e7aceecadd - Generated: 2026-11-14T14:52:04+00:00
- Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | none-detected | 65% | 100% |
| Code quality | 32 | poor | 90% | 100% |
| Security | 80 | adequate | 85% | 100% |
AI provenance
No AI attribution or AI-consistent velocity signals detected.
-
Explicitly attributed share (lower bound): 0.0%
-
Unattributed share in AI-consistent velocity bursts: 0.0%
-
Estimated AI-generated share: 0.0%
-
Stylometry index: 0.10 per 1,000 lines (narrated steps 79, placeholders 0, assistant phrasing 6, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2012-09 | 9,118 | 0% |
| 2012-10 | 404 | 0% |
| 2012-11 | 51 | 0% |
| 2012-12 | 6,233 | 0% |
| 2013-01 | 26 | 0% |
| 2013-03 | 7,522 | 0% |
| 2013-06 | 1,147 | 0% |
| 2014-04 | 278 | 0% |
| 2014-09 | 139,011 | 0% |
| 2015-03 | 510 | 0% |
| 2016-03 | 130 | 0% |
| 2017-04 | 315 | 0% |
Evidence
- step-by-step narration comment: // Finally, given a filename (or an open file or memory block--see header (Altona2/Alto)
- step-by-step narration comment: // Finally, the image data. (Altona2/Alto)
- step-by-step narration comment: // now we need to indicate how they correspond; we could either (Altona2/Alto)
- step-by-step narration comment: // now we use symbolic names for these, so that we can (Altona2/Alto)
- step-by-step narration comment: // now, we can start decoding frames... we'll only FAKE decode them, (Altona2/Alto)
- step-by-step narration comment: // now we want to lerp between these for the target samples... (Altona2/Alto)
- step-by-step narration comment: // step 1: we need to bias towards the page start... (Altona2/Alto)
- step-by-step narration comment: // first, store the current decode position so we can restore it (Altona2/Alto)
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 poor: test-to-source ratio 0.00, no CI test run detected; 34% of function code in complex or long functions; 52% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 36 |
| Duplication | 4 |
| Code smells (Opengrep) | 100 |
| Tests and CI | 0 |
| Documentation | 40 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 34,019; mean complexity 3.9, 90th percentile 8; 1446 complex and 771 long functions
- Duplicated lines: 51.7% of 658,039 compared
- Tests: 0 test lines for 974,913 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
- Docs missing or thin: license, contributing, changelog
Most complex functions:
- glewContextInit in Altona2/Altona2/Libs/Base/GraphicsGlew.cpp: complexity 869, 651 lines
- glewIsSupported in Altona2/Altona2/Libs/Base/GraphicsGlew.cpp: complexity 867, 2186 lines
- _glewInit_GL_EXT_direct_state_access in Altona2/Altona2/Libs/Base/GraphicsGlew.cpp: complexity 214, 218 lines
- Altona2::sScanner::Scan in Altona2/Altona2/Libs/Util/Scanner.cpp: complexity 186, 456 lines
- sScanner::Scan in altona_wz4/altona/main/util/scanner.cpp: complexity 168, 408 lines
Security
Security posture is adequate: no high-impact findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 97 |
| Static analysis (Opengrep) | 99 |
| 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] |
Altona2/Altona2/Libs/Util/StbDxt.h:152 |
| 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] |
Altona2/Altona2/Libs/Util/StbImage.c:1036 |
| 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] |
Altona2/Altona2/Libs/Util/StbImage.c:1172 |
| 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] |
Altona2/Altona2/Libs/Util/StbImage.c:1996 |
| 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] |
Altona2/Altona2/Libs/Util/StbImage.c:1997 |
| 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] |
Altona2/Altona2/Libs/Util/StbImage.c:2178 |
| 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] |
Altona2/Altona2/Libs/Util/StbImage.c:2193 |
| 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] |
Altona2/Altona2/Libs/Util/StbImage.c:2197 |
| 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] |
Altona2/Altona2/Libs/Util/StbImage.c:2202 |
| 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] |
Altona2/Altona2/Libs/Util/StbImage.c:3836 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:1009 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:2102 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:3361 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:3369 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:3656 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:3688 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:3966 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:4159 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:5087 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:5115 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:5156 |
| 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] |
Altona2/Altona2/Libs/Util/StbVorbis.c:5363 |
| 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] |
RG2/Viewer/math3d_2.h:185 |
| 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] |
RG2/math3d_2.h:276 |
| 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] |
RG2/pool.h:58 |
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.
Repository profile
- Source lines: 974,913; test lines: 0
| Language | Lines |
|---|---|
| C++ | 877,180 |
| C | 97,733 |