Leaderboard github.com
amaneureka/AtomOS
A multitasking monolithic Kernel based x86 targeting Operating System written in C# from scratch aiming for high-level implementation of drivers in managed environment.
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
49/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
82/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.13
Lines added per month all AI-attributed share
- 2014-0616,154 · 0% AI
- 2014-079,151 · 0% AI
- 2014-081,663 · 0% AI
- 2014-09851 · 0% AI
- 2014-10398 · 0% AI
- 2014-11328 · 0% AI
- 2014-122,409 · 0% AI
- 2015-03769 · 0% AI
- 2015-04306 · 0% AI
- 2015-051,196 · 0% AI
- 2015-061,523 · 0% AI
- 2015-071,443 · 0% AI
- 2015-101,144 · 0% AI
- 2015-1180 · 0% AI
- 2015-12885 · 0% AI
- 2016-01635 · 0% AI
- 2016-021,586 · 0% AI
- 2016-031,363 · 0% AI
- 2016-04912 · 0% AI
- 2016-066,290 · 0% AI
- 2016-071,395 · 0% AI
- 2016-09504 · 0% AI
- 2016-10133 · 0% AI
- 2016-114,492 · 0% AI
- 2016-1215,036 · 0% AI
- 2017-01827 · 0% AI
- 2017-027,445 · 0% AI
- 2017-031,255 · 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
- 346
- effective_loc
- 80,173
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 23,463
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 1,730.46
- measured_loc
- 56,710
- median_loc_per_hour
- 78.75
- pr_timed_units
- 2
- pre_ai_era_burst_loc
- 3,259
- pre_ai_era_bursts
- 2
- pre_ai_era_measured_loc
- 56,710
- work_units
- 256
Release velocityskipped
Coding styleok6 items
- step-by-step narration comment: // Now we scan whole source i mean billions of lines kernel code, will be in future so no need to laugh
- step-by-step narration comment: //Now we have to calculate the offset of object, and also give us that field
- step-by-step narration comment: //Now we have to calculate the offset of object, and also give us that field
- step-by-step narration comment: //Now we have to calculate the offset of object, and also give us that field
- step-by-step narration comment: /* Now we open door of gold coins xDD */
- step-by-step narration comment: /* Now we open door of gold coins xDD */
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 6
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 6
- files:placeholder
- 0
- index
- 0.13
- lines_scanned
- 46,825
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0.13
- per_kloc:placeholder
- 0
Code quality
49 poor
Code quality is poor: test-to-source ratio 0.00, no CI test run detected; 12% of function code in complex or long functions; 23% duplicated lines. Weakest area: testing.
How the score is built
- Complexity71
- Duplication25
- Lint and smells92
- Tests and CI15
- Documentation65
- Type safetynot measured
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok10 items
- Keyboard::GetKeyChar in src/Kernel/Kernel_alpha/Drivers/Input/keyboard/Keyboard.cs: complexity 118, 74 lines
- BodyProcesser::Process in src/Compiler/OpCodes.cs: complexity 88, 356 lines
- Compiler::EmitOpCodes in src/Compiler/Atomixilc/Compiler.cs: complexity 85, 347 lines
- Compiler::ScanMethod in src/Compiler/Compiler.cs: complexity 34, 142 lines
- Compositor::HandleMouseEvent in src/Kernel/Atomix.Kernel_H/Gui/Compositor.cs: complexity 31, 84 lines
- Helper::GetTypeSize in src/Compiler/Atomixilc/Helper.cs: complexity 30, 56 lines
- NewObj::Execute in src/Compiler/IL/Object/NewObj.cs: complexity 30, 162 lines
- ILHelper::SizeOf in src/Compiler/ILHelper.cs: complexity 28, 53 lines
- IDE::Access_Disk in src/Kernel/Kernel_alpha/Drivers/Buses/ATA/IDE.cs: complexity 26, 117 lines
- ebppush::Apply in src/Compiler/ILOptimizer/optimizations/ebppush.cs: complexity 25, 79 lines
- complex_functions
- 24
- function_nloc
- 21,260
- functions
- 1,534
- long_functions
- 7
- many_param_functions
- 2
- mean_ccn
- 3.02
- p90_ccn
- 7
- risky_nloc_share
- 11.5%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: libs/Build-cairo.sh:1 and libs/Build-freetype.sh:1
- 6+ duplicated lines: libs/Build-pixman.sh:17 and libs/Build-zlib.sh:16
- 6+ duplicated lines: src/Apps/Atomix.Core/Properties/AssemblyInfo.cs:13 and src/Apps/Atomix.Shell/Properties/AssemblyInfo.cs:13
- 6+ duplicated lines: src/Apps/Atomix.Core/mscorlib/Exception.cs:15 and src/Kernel/Atomix.mscorlib/Exception.cs:14
- 6+ duplicated lines: src/Compiler/Atomix.Assembler/Properties/AssemblyInfo.cs:13 and src/Compiler/CompilerExt/Properties/AssemblyInfo.cs:13
- 6+ duplicated lines: src/Compiler/Atomix.Assembler/Registers.cs:12 and src/Compiler/Atomixilc/Machine/Register.cs:12
- 6+ duplicated lines: src/Compiler/Atomix.Assembler/x86/Cmpss.cs:19 and src/Compiler/Atomix.Assembler/x86/DestinationSource.cs:27
- 6+ duplicated lines: src/Compiler/Atomix.Assembler/x86/DestinationSource.cs:14 and src/Compiler/Atomix.Assembler/x86/DestinationSourceSize.cs:14
- 6+ duplicated lines: src/Compiler/Atomixilc/Compiler.cs:1027 and src/Compiler/Atomixilc/Compiler.cs:1056
- 6+ duplicated lines: src/Compiler/Atomixilc/Compiler.cs:1199 and src/Compiler/OpCodes.cs:93
- compared_lines
- 27,577
- duplicated_lines
- 6,306
- duplicated_share
- 22.9%
- files
- 610
Lintok
- category:correctness
- 61
- findings
- 61
- scanned_lines
- 46,825
- weighted_findings
- 15.25
Tests and CIok1 item
- CI config: .travis.yml
.travis.yml
- check:ci_present
- yes
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- no
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 1
- cochange_commits
- 281
- cochange_share
- 0.0%
- source_lines
- 46,825
- test_lines
- 0
- test_ratio
- 0
Documentationok2 items
- README.md
README.md - LICENSE.md
LICENSE.md
- check:changelog
- no
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 38
Type safetyskipped
Security
82 adequate
Security posture is adequate: no high-impact findings. Weakest area: posture.
How the score is built
- Secrets100
- Static analysis (SAST)100
- 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
- 0
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 0
- findings_high
- 0
- findings_low
- 0
- findings_medium
- 0
- parse_errors
- 0
- scanned_lines
- 46,825
- weighted_findings
- 0
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
61 low
61 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-cairo.sh:23 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-cairo.sh:25 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-cairo.sh:26 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-cairo.sh:34 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-cairo.sh:37 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-cairo.sh:39 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-cairo.sh:41 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-freetype.sh:23 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-freetype.sh:25 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-freetype.sh:26 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-freetype.sh:34 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-freetype.sh:37 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-freetype.sh:39 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-freetype.sh:41 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-libpng.sh:23 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-libpng.sh:25 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-libpng.sh:26 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-libpng.sh:34 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-libpng.sh:37 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-libpng.sh:39 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-libpng.sh:41 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-pixman.sh:23 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-pixman.sh:25 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-pixman.sh:26 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-pixman.sh:34 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-pixman.sh:37 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-pixman.sh:39 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-pixman.sh:41 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-zlib.sh:22 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-zlib.sh:24 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-zlib.sh:30 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-zlib.sh:33 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-zlib.sh:36 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-zlib.sh:38 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
libs/Build-zlib.sh:40 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Build.sh:35 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Build.sh:36 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Build.sh:38 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Build.sh:40 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Build.sh:41 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Build.sh:52 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Build.sh:55 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:101 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:119 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:123 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:129 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:133 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:139 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:143 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:149 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:152 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:156 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:162 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:165 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:166 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:169 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:173 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:177 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:178 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:179 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
src/Build/Setup.sh:183 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
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 | 61 | |
| 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 | 0 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 0 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | a425e283712b | prov-5+qual-2+sec-2 | 0% | 49 | 82 |
| 2026-11-14 | a425e283712b | prov-4+qual-2+sec-2 | 0% | 49 | 82 |
Full text report
- Repository: https://github.com/amaneureka/AtomOS
- Commit:
a425e283712b82defdfa0952e83c59c63027c779 - Generated: 2026-11-14T14:52:02+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 | 49 | poor | 90% | 100% |
| Security | 82 | 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.13 per 1,000 lines (narrated steps 6, placeholders 0, assistant phrasing 0, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2016-02 | 1,586 | 0% |
| 2016-03 | 1,363 | 0% |
| 2016-04 | 912 | 0% |
| 2016-06 | 6,290 | 0% |
| 2016-07 | 1,395 | 0% |
| 2016-09 | 504 | 0% |
| 2016-10 | 133 | 0% |
| 2016-11 | 4,492 | 0% |
| 2016-12 | 15,036 | 0% |
| 2017-01 | 827 | 0% |
| 2017-02 | 7,445 | 0% |
| 2017-03 | 1,255 | 0% |
Evidence
- step-by-step narration comment: // Now we scan whole source i mean billions of lines kernel code, will be in future so no need to laugh (src/Compiler)
- step-by-step narration comment: //Now we have to calculate the offset of object, and also give us that field (src/Compiler)
- step-by-step narration comment: //Now we have to calculate the offset of object, and also give us that field (src/Compiler)
- step-by-step narration comment: //Now we have to calculate the offset of object, and also give us that field (src/Compiler)
- step-by-step narration comment: /* Now we open door of gold coins xDD */ (src/Kernel/A)
- step-by-step narration comment: /* Now we open door of gold coins xDD */ (src/Kernel/K)
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; 12% of function code in complex or long functions; 23% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 71 |
| Duplication | 25 |
| Code smells (Opengrep) | 92 |
| Tests and CI | 15 |
| Documentation | 65 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 1,534; mean complexity 3.0, 90th percentile 7; 24 complex and 7 long functions
- Duplicated lines: 22.9% of 27,577 compared
- Tests: 0 test lines for 46,825 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:
- Keyboard::GetKeyChar in src/Kernel/Kernel_alpha/Drivers/Input/keyboard/Keyboard.cs: complexity 118, 74 lines
- BodyProcesser::Process in src/Compiler/OpCodes.cs: complexity 88, 356 lines
- Compiler::EmitOpCodes in src/Compiler/Atomixilc/Compiler.cs: complexity 85, 347 lines
- Compiler::ScanMethod in src/Compiler/Compiler.cs: complexity 34, 142 lines
- Compositor::HandleMouseEvent in src/Kernel/Atomix.Kernel_H/Gui/Compositor.cs: complexity 31, 84 lines
Security
Security posture is adequate: no high-impact findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 100 |
| 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
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: 46,825; test lines: 0
| Language | Lines |
|---|---|
| C# | 46,168 |
| Shell | 484 |
| C | 173 |