Leaderboard github.com
ArhanChaudhary/egg-solver
egg-solver is the fastest publicly available optimal Rubik's Cube solver
unreviewed-ai-risk
AI provenance
45%
explicit
- Confidence
- 95%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
44/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
60/100
weak
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
45% explicit
Explicit AI attribution on 45% of first-party code added; an estimated 45% including velocity signals.
How the score is built
- Explicitly attributed share45%
- Unattributed share in AI-pace bursts0%
- Estimated AI-generated share45%
- AI tool configuration files0
- Work sessions at AI pace8
- Releases at AI pacenot measured
- Coding-style index (1.0+ means possible)0.06
Attributed AI tools
| Tool | Commits | Lines added | First seen | Last seen |
|---|---|---|---|---|
| Claude Code | 134 | 33,833 | 2026-11-02 | 2026-11-10 |
Lines added per month all AI-attributed share
- 2026-1175,842 · 45% AI
Findings in AI-attributed lines vs the rest
From git blame: 23,027 lines trace to AI-attributed commits, 43,924 to others. Reported, not scored.
| Findings per 1,000 lines | AI-attributed | Other | Ratio |
|---|---|---|---|
| Code quality | 0.39 | 3.14 | 0.12× |
| Security | 0.30 | 6.58 | 0.05× |
Evidence by analyzer
Explicit AI attributionok26 items
- Claude Code: 134 attributed commits, 33,833 lines added
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- Claude Code: author email [email protected]
- attributed_commit_share
- 96.4%
- attributed_commits
- 134
- attributed_loc
- 33,833
- attributed_loc_share
- 44.6%
- commits
- 139
- effective_loc
- 75,842
- tools_detected
- 1
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok8 items
- 3,570 lines of first-party code in ~1.4h (2,634 lines/hour, 4 commit session)
- 3,874 lines of first-party code in ~1.7h (2,287 lines/hour, 5 commit session)
- 2,173 lines of first-party code in ~1.3h (1,686 lines/hour, 2 commit session)
- 2,133 lines of first-party code in ~1.3h (1,591 lines/hour, 2 commit session)
- 2,811 lines of first-party code in ~2.5h (1,111 lines/hour, 6 commit session)
- 1,340 lines of first-party code in ~2.0h (686 lines/hour, 6 commit session)
- 1,681 lines of first-party code in ~2.6h (648 lines/hour, 9 commit session)
- 2,068 lines of first-party code in ~4.0h (519 lines/hour, 7 commit session)
- excluded_import_loc
- 43,036
- flagged_loc
- 19,650
- flagged_loc_share
- 59.9%
- flagged_units
- 8
- max_loc_per_hour
- 2,634.15
- measured_loc
- 32,806
- median_loc_per_hour
- 269.22
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 0
- work_units
- 46
Release velocityskipped
Coding styleok2 items
- assistant-style phrasing left in code: # The report includes the reviewed upstream findings as requested. Keep a
- assistant-style phrasing left in code: the nodes, as requested. No 1 GiB hugetlb measurements exist in this archive:
- count:assistant_voice
- 2
- count:emoji_in_code
- 0
- count:narrated_steps
- 0
- count:placeholder
- 0
- files:assistant_voice
- 2
- files:emoji_in_code
- 0
- files:narrated_steps
- 0
- files:placeholder
- 0
- index
- 0.06
- lines_scanned
- 66,951
- per_kloc:assistant_voice
- 0.03
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 0
Findings in AI-written linesok
- ai_lines
- 23,027
- blame_failures
- 0
- files_blamed
- 128
- other_lines
- 43,924
- quality:ai_findings
- 9
- quality:ai_per_kloc
- 0.39
- quality:other_findings
- 138
- quality:other_per_kloc
- 3.14
- quality:ratio
- 0.12
- security:ai_findings
- 7
- security:ai_per_kloc
- 0.30
- security:other_findings
- 289
- security:other_per_kloc
- 6.58
- security:ratio
- 0.05
Code quality
44 poor
Code quality is poor: test-to-source ratio 0.04, no CI test run detected; 15% of function code in complex or long functions; 85% duplicated lines. Weakest area: duplication.
How the score is built
- Complexity64
- Duplication1
- Lint and smells61
- Tests and CI45
- Documentation40
- Type safety40
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok10 items
- d20_section in docs/reproduce/final-report.py: complexity 71, 94 lines
- main in build.rs: complexity 52, 97 lines
- cell in docs/reproduce/final-report.py: complexity 49, 56 lines
- wiki_section in docs/reproduce/final-report.py: complexity 48, 92 lines
- main in docs/data/nissy-throughput-20261108/src/nissy-batch.c: complexity 43, 40 lines
- parse_raw in docs/reproduce/final-report.py: complexity 37, 83 lines
- build in docs/evidence/validation/mordant/sources/main/src/lanes/share.rs: complexity 34, 108 lines
- build in docs/evidence/validation/ub-audit/fix/src/lanes/share.rs: complexity 34, 108 lines
- build in docs/evidence/validation/ub-audit/source/src/lanes/share.rs: complexity 34, 108 lines
- build in docs/evidence/validation/ub-audit/trace-before-fix.rs: complexity 34, 108 lines
- complex_functions
- 70
- function_nloc
- 40,670
- functions
- 2,373
- long_functions
- 15
- many_param_functions
- 28
- mean_ccn
- 3.68
- p90_ccn
- 8
- risky_nloc_share
- 15.1%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: benches/kernels.rs:7 and build.rs:7
- 6+ duplicated lines: docs/data/nissy-throughput-20261108/checkpoint-cli-grid.py:5 and docs/data/nissy-throughput-20261108/checkpoint-current.py:5
- 6+ duplicated lines: docs/data/nissy-throughput-20261108/checkpoint-next.py:5 and docs/data/nissy-throughput-20261108/checkpoint.py:5
- 6+ duplicated lines: docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:6 and docs/data/nissy-throughput-20261108/provenance/pgo-train2.sh:5
- 6+ duplicated lines: docs/data/nissy-throughput-20261108/src/sample-fast.py:6 and docs/data/nxopt32-20261107/sample.py:6
- 6+ duplicated lines: docs/data/nissy-throughput-20261108/src/throughput-measured.rs:1 and docs/data/nissy-throughput-20261108/src/throughput.rs:1
- 6+ duplicated lines: docs/evidence/validation/mordant/sources/main/src/cli.rs:1 and src/cli.rs:1
- 6+ duplicated lines: docs/evidence/validation/mordant/sources/main/src/coord.rs:1 and docs/reference/source/src/coord.rs:1
- 6+ duplicated lines: docs/evidence/validation/mordant/sources/main/src/cubie.rs:1 and src/cubie.rs:1
- 6+ duplicated lines: docs/evidence/validation/mordant/sources/main/src/env.rs:1 and src/env.rs:1
- compared_lines
- 53,127
- duplicated_lines
- 44,969
- duplicated_share
- 84.6%
- files
- 128
Lintok
- category:best-practice
- 54
- category:correctness
- 82
- category:maintainability
- 11
- findings
- 147
- scanned_lines
- 66,951
- weighted_findings
- 133.50
Tests and CIok1 item
- CI config: .github/workflows/pages.yml
.github/workflows/pages.yml
- check:ci_present
- yes
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- yes
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 1
- cochange_commits
- 132
- cochange_share
- 20.4%
- source_lines
- 66,951
- test_lines
- 2,806
- test_ratio
- 0.04
Documentationok1 item
- README.md
README.md
- check:changelog
- no
- check:contributing
- no
- check:license
- no
- check:readme
- yes
- readme_lines
- 60
Type safetyok
- check:low_escape_density
- yes
- check:strict_config
- no
- escapes
- 1
- escapes_per_kloc
- 0.40
Security
60 weak
Security posture is weak: 10 high-severity SAST findings; 5 high-severity workflow issues. Weakest area: posture.
How the score is built
- Secrets94
- Static analysis (SAST)26
- Vulnerable dependencies100
- CI workflows37
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesok
- checked
- 13
- declared
- 13
- lookup_errors
- 0
- missing
- 0
- recent
- 0
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 2
Static analysis (opengrep)ok
- findings
- 1,022
- findings_high
- 10
- findings_low
- 988
- findings_medium
- 24
- parse_errors
- 16
- scanned_lines
- 66,951
- weighted_findings
- 260.61
Dependencies (osv-scanner)ok
- penalty
- 0
- vulnerabilities
- 0
- vulnerable_packages
- 0
- vulns_critical
- 0
- vulns_high
- 0
- vulns_low
- 0
- vulns_medium
- 0
- vulns_unknown
- 0
CI workflows (zizmor)ok
- findings
- 6
- findings_high
- 5
- findings_low
- 1
- findings_medium
- 0
- penalty
- 60.30
- workflows
- 1
Security postureok2 items
- docs/evidence/validation/ub-audit/probes/Cargo.toml has no lockfile alongside it (unpinned dependencies)
docs/evidence/validation/ub-audit/probes/Cargo.toml - wasm/Cargo.toml has no lockfile alongside it (unpinned dependencies)
wasm/Cargo.toml
- check:dependency_updates
- no
- check:lockfiles
- no
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 0.7%
- unpinned_manifests
- 2
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
36 high76 medium343 low
455 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-cli-grid.py:12 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-cli-grid.py:16 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-current.py:12 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-current.py:16 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-full-grid.py:12 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-full-grid.py:16 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-next.py:12 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-next.py:8 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-stdin.py:12 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-stdin.py:16 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-topologies.py:12 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint-topologies.py:16 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint.py:12 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/checkpoint.py:8 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.open-never-closed |
docs/data/nissy-throughput-20261108/matrix.py:14 | file object opened without corresponding close | Lint |
| high | opengrep/python.lang.best-practice.open-never-closed |
docs/data/nissy-throughput-20261108/matrix.py:14 | file object opened without corresponding close | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/matrix.py:38 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/src/docs-browser-smoke.py:7 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nissy-throughput-20261108/src/sample-fast.py:5 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nxopt32-20261107/run.py:29 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
docs/data/nxopt32-20261107/sample.py:5 | time.sleep() call; did you mean to leave this in? | Lint |
| high | zizmor/unpinned-uses |
.github/workflows/pages.yml:19 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/pages.yml:20 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/pages.yml:21 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/pages.yml:31 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/pages.yml:47 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
docs/data/nissy-throughput-20261108/cross-replay.py:6 | Detected subprocess function 'check_output' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
docs/data/nissy-throughput-20261108/matrix.py:44 | Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
docs/data/nissy-throughput-20261108/matrix.py:45 | Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
docs/data/nissy-throughput-20261108/matrix.py:82 | Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
docs/data/nissy-throughput-20261108/restore-requested-tables.py:22 | Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-os-exec-audit |
docs/data/nxopt32-20261107/exec-solver.py:5 | Found dynamic content when spawning a process. This is dangerous if external data can reach this function call because it allows a malicious actor to execute commands. Ensure no external data reaches here. [confidence low] | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-os-exec-tainted-env-args |
docs/data/nxopt32-20261107/exec-solver.py:5 | Found user controlled content when spawning a process. This is dangerous because it allows a malicious actor to execute commands. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
docs/data/nxopt32-20261107/run.py:34 | Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
docs/data/nxopt32-20261107/run.py:35 | Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
docs/reproduce/historical/replay-phack-exports.py:28 | Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
docs/data/nissy-throughput-20261108/matrix.py:101 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
docs/data/nissy-throughput-20261108/matrix.py:105 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
docs/data/nissy-throughput-20261108/matrix.py:106 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
docs/data/nissy-throughput-20261108/matrix.py:109 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
docs/data/nissy-throughput-20261108/matrix.py:112 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.best-practice.hardcoded-tmp-path |
docs/data/nissy-throughput-20261108/matrix.py:14 | Detected hardcoded temp directory. Consider using 'tempfile.TemporaryFile' instead. | Lint |
| medium | opengrep/python.lang.best-practice.hardcoded-tmp-path |
docs/data/nissy-throughput-20261108/matrix.py:14 | Detected hardcoded temp directory. Consider using 'tempfile.TemporaryFile' instead. | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/data/nissy-throughput-20261108/matrix.py:14 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/data/nissy-throughput-20261108/matrix.py:14 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
docs/data/nissy-throughput-20261108/matrix.py:99 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.best-practice.hardcoded-tmp-path |
docs/data/nissy-throughput-20261108/restore-requested-tables.py:5 | Detected hardcoded temp directory. Consider using 'tempfile.TemporaryFile' instead. | Lint |
| medium | opengrep/python.lang.best-practice.hardcoded-tmp-path |
docs/data/nissy-throughput-20261108/restore-requested-tables.py:5 | Detected hardcoded temp directory. Consider using 'tempfile.TemporaryFile' instead. | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/data/nissy-throughput-20261108/restore-requested-tables.py:5 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/data/nissy-throughput-20261108/restore-requested-tables.py:5 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/c.lang.correctness.incorrect-use-ato-fn |
docs/data/nissy-throughput-20261108/src/nissy-batch.c:27 | 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 |
docs/data/nissy-throughput-20261108/src/nissy-batch.c:27 | 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/python.lang.best-practice.hardcoded-tmp-path |
docs/data/nxopt32-20261107/run.py:26 | Detected hardcoded temp directory. Consider using 'tempfile.TemporaryFile' instead. | Lint |
| medium | opengrep/python.lang.best-practice.hardcoded-tmp-path |
docs/data/nxopt32-20261107/run.py:26 | Detected hardcoded temp directory. Consider using 'tempfile.TemporaryFile' instead. | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/data/nxopt32-20261107/run.py:26 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/data/nxopt32-20261107/run.py:26 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:101 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:1021 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:1022 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:1055 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:1058 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:1064 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:1066 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:1071 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:1094 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:224 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:315 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:323 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:334 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.manual-defaultdict-list-create |
docs/reproduce/final-report.py:364 | manually creating a defaultdict - use collections.defaultdict(list) | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:462 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.manual-defaultdict-list-create |
docs/reproduce/final-report.py:492 | manually creating a defaultdict - use collections.defaultdict(list) | Lint |
| medium | opengrep/python.lang.best-practice.pass-body-range |
docs/reproduce/final-report.py:568 | `pass` is the body of for title, d in ref.items(). Consider removing this or raise NotImplementedError() if this is a TODO | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:572 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:603 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:625 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
docs/reproduce/final-report.py:629 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
docs/reproduce/final-report.py:648 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
docs/reproduce/final-report.py:651 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
docs/reproduce/final-report.py:653 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
docs/reproduce/final-report.py:657 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
docs/reproduce/final-report.py:683 | `return` only makes sense inside a function | Lint |
| medium | opengrep/javascript.lang.correctness.no-replaceall |
scripts/render-docs.mjs:144 | The string method replaceAll is not supported in all versions of javascript, and is not supported by older browser versions. Consider using replace() with a regex as the first argument instead like mystring.replace(/bad/g, "good")... | Lint |
| medium | opengrep/javascript.lang.correctness.no-replaceall |
scripts/render-docs.mjs:159 | The string method replaceAll is not supported in all versions of javascript, and is not supported by older browser versions. Consider using replace() with a regex as the first argument instead like mystring.replace(/bad/g, "good")... | Lint |
| medium | opengrep/javascript.lang.correctness.no-replaceall |
scripts/render-docs.mjs:22 | The string method replaceAll is not supported in all versions of javascript, and is not supported by older browser versions. Consider using replace() with a regex as the first argument instead like mystring.replace(/bad/g, "good")... | Lint |
| medium | opengrep/javascript.lang.correctness.no-replaceall |
scripts/render-docs.mjs:22 | The string method replaceAll is not supported in all versions of javascript, and is not supported by older browser versions. Consider using replace() with a regex as the first argument instead like mystring.replace(/bad/g, "good")... | Lint |
| medium | opengrep/javascript.lang.correctness.no-replaceall |
scripts/render-docs.mjs:22 | The string method replaceAll is not supported in all versions of javascript, and is not supported by older browser versions. Consider using replace() with a regex as the first argument instead like mystring.replace(/bad/g, "good")... | Lint |
| medium | opengrep/javascript.lang.correctness.no-replaceall |
scripts/render-docs.mjs:22 | The string method replaceAll is not supported in all versions of javascript, and is not supported by older browser versions. Consider using replace() with a regex as the first argument instead like mystring.replace(/bad/g, "good")... | Lint |
| medium | opengrep/python.lang.security.audit.exec-detected |
docs/data/nissy-throughput-20261108/finish-scaling.py:3 | Detected the use of exec(). exec() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by... | Static analysis (opengrep) |
| medium | opengrep/c.lang.security.insecure-use-printf-fn |
docs/data/nissy-throughput-20261108/src/hugecp.c:44 | Avoid using user-controlled format strings passed into 'sprintf', 'printf' and 'vsprintf'. These functions put you at risk of buffer overflow vulnerabilities through the use of format string exploits. Instead, use 'snprintf' and... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs.html:153 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs.html:156 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs.html:255 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs.html:440 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:126 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:126 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:127 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
scripts/render-docs.mjs:145 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:154 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:156 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:167 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:168 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:173 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:175 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:175 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:179 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:179 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:179 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:180 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
scripts/render-docs.mjs:181 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
wasm/demo-worker.mjs:36 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
wasm/egg-solver.mjs:348 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
docs/data/nissy-throughput-20261108/provenance/pgo-build.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.sh:27 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.sh:28 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.sh:29 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-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 |
docs/data/nissy-throughput-20261108/provenance/pgo-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 |
docs/data/nissy-throughput-20261108/provenance/pgo-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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.sh:42 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.sh:43 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.sh:45 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-build.sh:47 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:14 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:14 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:16 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:17 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:17 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:18 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:18 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:20 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:20 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:21 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:21 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:27 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:27 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:28 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:28 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.sh:29 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.sh:13 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.sh:13 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.sh:15 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.sh:17 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.sh:17 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.sh:18 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.sh:18 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.sh:19 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.sh:21 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.sh:21 | 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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.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 |
docs/data/nissy-throughput-20261108/provenance/pgo-train2.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 |
scripts/check.sh:105 | 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 |
scripts/check.sh:110 | 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 |
scripts/check.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 |
scripts/check.sh:54 | 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 |
scripts/check.sh:57 | 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/javascript.lang.correctness.missing-template-string-indicator |
scripts/render-docs.mjs:25 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
scripts/render-docs.mjs:25 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
scripts/render-docs.mjs:79 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
scripts/render-docs.mjs:79 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
scripts/stress.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 |
scripts/stress.sh:50 | 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 |
scripts/stress.sh:60 | 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 |
wasm/build.sh:13 | 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/javascript.lang.correctness.useless-assignment |
wasm/egg-solver.mjs:423 | `this.table` is assigned twice; the first assignment is useless | Lint |
| low | zizmor/artipacked |
.github/workflows/pages.yml:19 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| low | opengrep/rust.lang.security.unsafe-usage |
benches/kernels.rs:61 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.args |
docs/data/nissy-throughput-20261108/src/throughput-measured.rs:21 | args should not be used for security operations. From the docs: "The first element is traditionally the path of the executable, but it can be set to arbitrary text, and might not even exist. This means this property should not be relied... | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/data/nissy-throughput-20261108/src/throughput-measured.rs:51 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.args |
docs/data/nissy-throughput-20261108/src/throughput.rs:24 | args should not be used for security operations. From the docs: "The first element is traditionally the path of the executable, but it can be set to arbitrary text, and might not even exist. This means this property should not be relied... | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/data/nissy-throughput-20261108/src/throughput.rs:54 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.args |
docs/data/nissy-throughput-20261108/src/verify_solutions.rs:17 | args should not be used for security operations. From the docs: "The first element is traditionally the path of the executable, but it can be set to arbitrary text, and might not even exist. This means this property should not be relied... | Static analysis (opengrep) |
| low | gitleaks/generic-api-key |
docs/evidence/validation/continuation/miri-before-additional-ub-audit/no-ub-evidence.json:17 | Possible generic-api-key secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
docs/evidence/validation/mordant/sources.json:158 | Possible generic-api-key secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/coord.rs:216 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/coord.rs:254 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/coord.rs:273 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/coord.rs:290 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/coord.rs:306 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/coord.rs:349 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/coord.rs:408 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/coord.rs:461 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:1178 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:1469 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:1493 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2034 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2045 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2085 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2131 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2138 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2168 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2273 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2305 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2340 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2351 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2431 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2435 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2441 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2450 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2453 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2460 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2534 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2656 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2672 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2675 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2689 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2706 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2718 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2729 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2792 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2804 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2827 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2840 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2847 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2860 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2870 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2878 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2885 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2910 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2923 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2924 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2944 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2950 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2967 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2975 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:2999 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3028 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3099 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3226 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3287 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3292 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3310 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3316 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3324 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3327 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3356 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3365 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3375 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3412 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3427 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3445 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3448 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3486 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3488 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3494 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3501 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3504 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3521 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3573 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3574 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:3597 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:392 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:406 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:4080 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:413 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:4361 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/lanes/share.rs:605 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/portable/mod.rs:487 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/portable/mod.rs:499 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/portable/mod.rs:518 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/portable/mod.rs:529 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/portable/mod.rs:657 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/portable/mod.rs:783 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/solver.rs:187 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/solver.rs:211 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/solver.rs:231 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:1007 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:1127 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:1131 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:1159 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:1171 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.temp-dir |
docs/evidence/validation/mordant/sources/main/src/tables.rs:1190 | temp_dir should not be used for security operations. From the docs: 'The temporary directory may be shared among users, or between processes with different privileges; thus, the creation of any files or directories in the temporary... | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:1239 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:184 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:227 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:254 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:262 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:309 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:350 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:364 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:369 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:388 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:490 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:511 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:535 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:538 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:572 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:582 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:603 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:612 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:621 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:628 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:634 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:736 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:751 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables.rs:970 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/file.rs:298 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/file.rs:390 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:1140 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:315 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:325 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:337 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:346 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:363 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:385 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:407 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:419 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:653 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:675 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:735 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:810 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:832 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/src/tables/shm.rs:837 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs:126 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs:186 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs:197 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs:313 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs:358 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs:64 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:1180 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:1471 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:1495 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:1693 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2039 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2050 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2090 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2136 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2143 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2173 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2285 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2317 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2352 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2363 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2443 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2447 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2453 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2462 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2465 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2472 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2546 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2668 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2684 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2687 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2701 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2718 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2730 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2741 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2804 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2816 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2839 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2852 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2859 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2872 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2882 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2890 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2897 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2922 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2935 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2936 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2956 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2962 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2979 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:2987 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3011 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3040 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3111 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3238 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3299 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3304 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3322 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3328 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3336 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3339 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3368 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3377 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3387 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3424 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3439 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3457 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3460 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3498 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3500 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3506 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3513 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3516 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3533 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3585 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3586 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:3609 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:392 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:406 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:4103 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:413 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/lanes/share.rs:605 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1042 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1062 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1112 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1122 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1158 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1278 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1282 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1310 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1322 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.temp-dir |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1341 | temp_dir should not be used for security operations. From the docs: 'The temporary directory may be shared among users, or between processes with different privileges; thus, the creation of any files or directories in the temporary... | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1365 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1389 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1410 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:1452 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:214 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:257 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:284 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:292 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:342 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:391 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:406 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:411 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:431 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:543 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:558 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:571 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:595 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:598 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:645 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:655 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:676 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:685 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:694 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:701 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:707 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:814 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:870 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:887 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables.rs:899 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
docs/evidence/validation/ub-audit/fix/src/tables/shm.rs:46 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
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 | |
| Findings in AI-written lines | AI provenance | ok | git-blame | 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 | 147 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | ok | — | 0 | |
| CI workflows (zizmor) | Security | ok | zizmor 1.32.0 | 6 | |
| Dependencies (osv-scanner) | Security | ok | osv-scanner version: 2.7.1 | 0 | |
| Release downloads | Security | ok | — | 0 | |
| Security posture | Security | ok | — | 0 | |
| Package registries | Security | ok | — | 0 | |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 300 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 2 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 28a1953da96f | prov-5+qual-2+sec-2 | 45% | 44 | 60 |
| 2026-11-14 | 28a1953da96f | prov-4+qual-2+sec-2 | 45% | 44 | 60 |
Full text report
- Repository: https://github.com/ArhanChaudhary/egg-solver
- Commit:
28a1953da96f389154541ff1da145be1d08d394b - Generated: 2026-11-14T14:51:59+00:00
- Scorer 0.1.0, scoring prov-5+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) | 45 | explicit | 95% | 100% |
| Code quality | 44 | poor | 90% | 100% |
| Security | 60 | weak | 85% | 100% |
AI provenance
Explicit AI attribution on 45% of first-party code added; an estimated 45% including velocity signals.
- Explicitly attributed share (lower bound): 44.6%
- Unattributed share in AI-consistent velocity bursts: 0.0%
- Estimated AI-generated share: 44.6%
| AI tool | Attributed commits | Lines added |
|---|---|---|
| Claude Code | 134 | 33,833 |
Current source lines last changed by AI-attributed commits: 23,027 of 66,951.
| Findings per 1,000 lines | AI-attributed | Other | Ratio |
|---|---|---|---|
| Quality | 0.391 | 3.142 | 0.12x |
| Security | 0.304 | 6.58 | 0.05x |
- Stylometry index: 0.06 per 1,000 lines (narrated steps 0, placeholders 0, assistant phrasing 2, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2026-11 | 75,842 | 45% |
Evidence
- Claude Code: author email [email protected] (28a1953da96f)
- Claude Code: author email [email protected] (875fb45da494)
- Claude Code: author email [email protected] (b922b75bb2e5)
- Claude Code: author email [email protected] (0bfaf66706c1)
- Claude Code: author email [email protected] (3f40b92366b0)
- Claude Code: author email [email protected] (a8e1365e7037)
- Claude Code: author email [email protected] (365289687800)
- Claude Code: author email [email protected] (346433ad8b0f)
- Claude Code: author email [email protected] (13307bad3150)
- Claude Code: author email [email protected] (e18e971b2f8b)
- Claude Code: author email [email protected] (da134bc6d27b)
- Claude Code: author email [email protected] (4dda0ab76605)
- Claude Code: author email [email protected] (ce92f830536e)
- Claude Code: author email [email protected] (050ecb389305)
- Claude Code: author email [email protected] (75f5e8c28689)
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.04, no CI test run detected; 15% of function code in complex or long functions; 85% duplicated lines. Weakest area: duplication.
| Area | Score |
|---|---|
| Complexity (lizard) | 64 |
| Duplication | 1 |
| Code smells (Opengrep) | 61 |
| Tests and CI | 45 |
| Documentation | 40 |
| Type safety | 40 |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 2,373; mean complexity 3.7, 90th percentile 8; 70 complex and 15 long functions
- Duplicated lines: 84.6% of 53,127 compared
- Tests: 2,806 test lines for 66,951 source lines (ratio 0.04); CI test commands: none detected; 20% of recent source commits also change tests
- Docs missing or thin: license, contributing, changelog
Most complex functions:
- d20_section in docs/reproduce/final-report.py: complexity 71, 94 lines
- main in build.rs: complexity 52, 97 lines
- cell in docs/reproduce/final-report.py: complexity 49, 56 lines
- wiki_section in docs/reproduce/final-report.py: complexity 48, 92 lines
- main in docs/data/nissy-throughput-20261108/src/nissy-batch.c: complexity 43, 40 lines
Security
Security posture is weak: 10 high-severity SAST findings; 5 high-severity workflow issues. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 94 |
| Static analysis (Opengrep) | 26 |
| Vulnerable dependencies (OSV) | 100 |
| CI workflows (zizmor) | 37 |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: none; missing: security policy, dependency updates, signed commits, lockfiles
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'check_output' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
docs/data/nissy-throughput-20261108/cross-replay.py:6 |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
docs/data/nissy-throughput-20261108/matrix.py:44 |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
docs/data/nissy-throughput-20261108/matrix.py:45 |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
docs/data/nissy-throughput-20261108/matrix.py:82 |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
docs/data/nissy-throughput-20261108/restore-requested-tables.py:22 |
| high | opengrep/python.lang.security.audit.dangerous-os-exec-audit: Found dynamic content when spawning a process. This is dangerous if external data can reach this function call because it allows a malicious actor to execute commands. Ensure no external data reaches here. [confidence low] |
docs/data/nxopt32-20261107/exec-solver.py:5 |
| high | opengrep/python.lang.security.audit.dangerous-os-exec-tainted-env-args: Found user controlled content when spawning a process. This is dangerous because it allows a malicious actor to execute commands. [confidence medium] |
docs/data/nxopt32-20261107/exec-solver.py:5 |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
docs/data/nxopt32-20261107/run.py:34 |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
docs/data/nxopt32-20261107/run.py:35 |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
docs/reproduce/historical/replay-phack-exports.py:28 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/pages.yml:19 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/pages.yml:20 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/pages.yml:21 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/pages.yml:31 |
| high | zizmor/unpinned-uses: unpinned action reference [confidence high] |
.github/workflows/pages.yml:47 |
| medium | opengrep/python.lang.security.audit.exec-detected: Detected the use of exec(). exec() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by external sources. [confidence low] |
docs/data/nissy-throughput-20261108/finish-scaling.py:3 |
| medium | opengrep/c.lang.security.insecure-use-printf-fn: Avoid using user-controlled format strings passed into 'sprintf', 'printf' and 'vsprintf'. These functions put you at risk of buffer overflow vulnerabilities through the use of format string exploits. Instead, use 'snprintf' and 'vsnprintf'. [confidence low] |
docs/data/nissy-throughput-20261108/src/hugecp.c:44 |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape: Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must do this, ensure no external data can reach this location. [confidence low] |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs.html:153 |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape: Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must do this, ensure no external data can reach this location. [confidence low] |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs.html:156 |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape: Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must do this, ensure no external data can reach this location. [confidence low] |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs.html:255 |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape: Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must do this, ensure no external data can reach this location. [confidence low] |
docs/evidence/validation/mordant/sources/main/wasm/src/lib.rs.html:440 |
| medium | opengrep/javascript.lang.security.html-in-template-string: This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS). [confidence low] |
scripts/render-docs.mjs:126 |
| medium | opengrep/javascript.lang.security.html-in-template-string: This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS). [confidence low] |
scripts/render-docs.mjs:126 |
| medium | opengrep/javascript.lang.security.html-in-template-string: This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS). [confidence low] |
scripts/render-docs.mjs:127 |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html: JQuery's html function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider text instead. Otherwise, use a function that escapes HTML such as edX's HtmlUtils.setHtml(). [confidence low] |
scripts/render-docs.mjs:145 |
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: 66,951; test lines: 2,806
| Language | Lines |
|---|---|
| Rust | 65,013 |
| Python | 2,510 |
| Shell | 1,089 |
| JavaScript | 1,034 |
| C | 111 |