RepoTrust

Leaderboard github.com

NetSys/NetBricks

NetBricks: A new network function framework based on Rust.

  • View repository ↗
  • Rust
  • ★ 483
  • commit 71dfb94beaea
  • scored 2026-11-14
  • scoring prov-5+qual-2+sec-2

AI provenance

0%

none-detected

Confidence
65%
Coverage
100%

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

Code quality

55/100

weak

Confidence
90%
Coverage
100%

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

Security

53/100

weak

Confidence
85%
Coverage
100%

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

Dispute or request a re-score Full report JSON RepoTrust ai badgeRepoTrust quality badgeRepoTrust security badge

AI provenance

0% none-detected

No AI attribution or AI-consistent velocity signals detected.

How the score is built

  • Explicitly attributed share0%
  • Unattributed share in AI-pace bursts0%
  • Estimated AI-generated share0%
  • AI tool configuration files0
  • Work sessions at AI pace0
  • Releases at AI pacenot measured
  • Coding-style index (1.0+ means possible)0.00

Lines added per month all AI-attributed share

  1. 2015-043,942 · 0% AI
  2. 2015-057,595 · 0% AI
  3. 2015-064,858 · 0% AI
  4. 2015-071,058 · 0% AI
  5. 2015-091,716,266 · 0% AI
  6. 2015-10583 · 0% AI
  7. 2015-11497 · 0% AI
  8. 2015-122,061 · 0% AI
  9. 2016-01339 · 0% AI
  10. 2016-021,681 · 0% AI
  11. 2016-0348,395 · 0% AI
  12. 2016-044,932 · 0% AI
  13. 2016-057,021 · 0% AI
  14. 2016-062,906 · 0% AI
  15. 2016-072,763 · 0% AI
  16. 2016-082,303 · 0% AI
  17. 2016-092,023 · 0% AI
  18. 2016-101,798 · 0% AI
  19. 2016-11310 · 0% AI
  20. 2016-121,402 · 0% AI
  21. 2017-011,733 · 0% AI
  22. 2017-026 · 0% AI
  23. 2017-038 · 0% AI
  24. 2017-051,127 · 0% AI
  25. 2017-063,107 · 0% AI
  26. 2017-0712 · 0% AI
  27. 2017-083 · 0% AI
  28. 2017-1094 · 0% AI
  29. 2017-12412 · 0% AI
  30. 2018-0220 · 0% AI
  31. 2018-038 · 0% AI
  32. 2018-0413 · 0% AI
  33. 2018-057 · 0% AI
  34. 2019-013 · 0% AI

Evidence by analyzer

Explicit AI attributionok
attributed_commit_share
0.0%
attributed_commits
0
attributed_loc
0
attributed_loc_share
0.0%
commits
515
effective_loc
1,819,286
tools_detected
0
AI tool configurationok
artifacts
0
tools_configured
0
workflow_agents
0
Commit velocityok
excluded_import_loc
1,765,131
flagged_loc
0
flagged_loc_share
0.0%
flagged_units
0
max_loc_per_hour
1,757.52
measured_loc
54,155
median_loc_per_hour
56.25
pr_timed_units
62
pre_ai_era_burst_loc
4,506
pre_ai_era_bursts
2
pre_ai_era_measured_loc
54,155
work_units
346
Release velocityskipped
Coding styleok
count:assistant_voice
0
count:emoji_in_code
0
count:narrated_steps
0
count:placeholder
0
files:assistant_voice
0
files:emoji_in_code
0
files:narrated_steps
0
files:placeholder
0
index
0
lines_scanned
11,358
per_kloc:assistant_voice
0
per_kloc:emoji_in_code
0
per_kloc:narrated_steps
0
per_kloc:placeholder
0

Code quality

55 weak

Code quality is weak: test-to-source ratio 0.37, no CI test run detected; 3% of function code in complex or long functions; 18% duplicated lines. Weakest area: lint.

How the score is built

  • Complexity90
  • Duplication34
  • Lint and smells15
  • Tests and CI64
  • Documentation65
  • Type safety40
  • Review processnot measured

Evidence by analyzer

Complexity (lizard)ok2 items
complex_functions
2
function_nloc
5,469
functions
706
long_functions
1
many_param_functions
4
mean_ccn
1.64
p90_ccn
3
risky_nloc_share
3.5%
Duplication (jscpd)ok10 items
compared_lines
7,938
duplicated_lines
1,436
duplicated_share
18.1%
files
115
Lintok
category:best-practice
6
category:correctness
299
findings
305
scanned_lines
11,358
weighted_findings
86.75
Tests and CIok1 item
  • CI config: .travis.yml .travis.yml
check:ci_present
yes
check:ci_runs_lint
no
check:ci_runs_tests
no
check:has_tests
yes
check:test_ratio
no
check:tests_cochange
yes
ci_files
1
cochange_commits
250
cochange_share
39.2%
source_lines
11,358
test_lines
4,227
test_ratio
0.37
Documentationok2 items
  • README.md README.md
  • LICENSE.md LICENSE.md
check:changelog
no
check:contributing
no
check:license
yes
check:readme
yes
readme_lines
82
Type safetyok
check:low_escape_density
yes
check:strict_config
no
escapes
0
escapes_per_kloc
0

Security

53 weak

Security posture is weak: 4 high-severity SAST findings. Weakest area: posture.

How the score is built

  • Secrets88
  • Static analysis (SAST)36
  • Vulnerable dependenciesnot measured
  • CI workflowsnot measured
  • Security posture0
  • OpenSSF Scorecardnot measured

Evidence by analyzer

OpenSSF Scorecardskipped

no published OpenSSF Scorecard result for this repo

Package registriesok
checked
17
declared
17
lookup_errors
0
missing
0
recent
0
Secrets (gitleaks)ok
secrets_current
0
secrets_history
0
secrets_low_confidence
2
secrets_nonprod
2
Static analysis (opengrep)ok
findings
112
findings_high
4
findings_low
102
findings_medium
6
parse_errors
23
scanned_lines
11,358
weighted_findings
33.15
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok3 items
  • Cargo.toml has no lockfile alongside it (unpinned dependencies) Cargo.toml
  • debugging/rdtscp-test/Cargo.toml has no lockfile alongside it (unpinned dependencies) debugging/rdtscp-test/Cargo.toml
  • framework/Cargo.toml has no lockfile alongside it (unpinned dependencies) framework/Cargo.toml
check:dependency_updates
no
check:lockfiles
no
check:security_policy
no
check:signed_commits
no
signed_commit_share
0.0%
unpinned_manifests
3
Release downloadsok
binary_assets
0
signals
0
suspicious
0

Findings

7 high9 medium300 low

SeverityRuleLocationMessageTool
high opengrep/python.lang.best-practice.open-never-closed scripts/tuning/pmqos-static.py:64 file object opened without corresponding close Lint
high opengrep/python.lang.best-practice.arbitrary-sleep scripts/tuning/pmqos-static.py:75 time.sleep() call; did you mean to leave this in? Lint
high opengrep/python.lang.best-practice.open-never-closed scripts/tuning/read_cpu_dma_latency.py:11 file object opened without corresponding close Lint
high opengrep/dockerfile.security.missing-user build-container/Dockerfile:18 By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile... Static analysis (opengrep)
high opengrep/dockerfile.security.missing-user container/Dockerfile:41 By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile... Static analysis (opengrep)
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit container/run-script.py:17 Detected subprocess function 'check_call' 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-tainted-env-args container/run-script.py:17 Detected subprocess function 'check_call' with user controlled data. A malicious actor could leverage this to perform command injection. You may consider using 'shlex.quote()'. [confidence medium] Static analysis (opengrep)
medium opengrep/python.lang.best-practice.unspecified-open-encoding scripts/tuning/pmqos-static.py:107 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 scripts/tuning/pmqos-static.py:64 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 scripts/tuning/read_cpu_dma_latency.py:11 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.security.insecure-use-string-copy-fn native/init.c:163 Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn native/init.c:180 Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-memset native/mempool.c:138 When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-memset native/pmd.c:57 When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-memset native/pmd.c:98 When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-memset native/ring.c:52 When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... Static analysis (opengrep)
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command 3rdparty/get-dpdk.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 3rdparty/get-dpdk.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 3rdparty/get-dpdk.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 3rdparty/get-dpdk.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 3rdparty/get-dpdk.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 3rdparty/get-dpdk.sh:40 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command 3rdparty/scripts/rustc.sh:5 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 3rdparty/scripts/rustdoc.sh:5 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 build.sh:101 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command build.sh:103 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 build.sh:108 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 build.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 build.sh:127 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 build.sh:128 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 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/bash.lang.correctness.unquoted-variable-expansion-in-command build.sh:136 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 build.sh:136 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 build.sh:137 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 build.sh:144 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 build.sh:145 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 build.sh:148 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 build.sh:149 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command build.sh:153 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 build.sh:154 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 build.sh:157 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 build.sh:158 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 build.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 build.sh:183 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command build.sh:184 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 build.sh:185 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 build.sh:186 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 build.sh:187 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 build.sh:188 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 build.sh:193 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 build.sh:200 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 build.sh:203 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 build.sh:213 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 build.sh:218 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 build.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 build.sh:223 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 build.sh:227 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 build.sh:228 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 build.sh:236 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 build.sh:270 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 build.sh:271 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 build.sh:279 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 build.sh:280 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 build.sh:287 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 build.sh:289 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 build.sh:291 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 build.sh:302 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 build.sh:304 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 build.sh:306 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 build.sh:313 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 build.sh:314 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 build.sh:318 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 build.sh:319 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 build.sh:327 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 build.sh:336 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 build.sh:338 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 build.sh:339 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 build.sh:344 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 build.sh:348 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 build.sh:353 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 build.sh:359 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-command-substitution-in-command build.sh:360 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command build.sh:364 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 build.sh:366 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 build.sh:370 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 build.sh:385 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 build.sh:389 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 build.sh:402 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 build.sh:406 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 build.sh:418 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 build.sh:419 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 build.sh:423 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 build.sh:424 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 build.sh:430 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 build.sh:431 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 build.sh:434 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 build.sh:435 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 build.sh:441 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-command-substitution-in-command build.sh:442 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command build.sh:447 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 build.sh:448 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 build.sh:451 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 build.sh:452 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 build.sh:456 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 build.sh:457 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 build.sh:466 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 build.sh:467 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 build.sh:474 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 build.sh:475 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 build.sh:476 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 build.sh:477 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 build.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 build.sh:56 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 build.sh:59 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 build.sh:63 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 build.sh:64 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 build.sh:69 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 build.sh:70 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 container/run-container-bess.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-command-substitution-in-command container/run-container-bess.sh:50 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command container/run-container-bess.sh:51 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 container/run-container-bess.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 container/run-container.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-command-substitution-in-command container/run-container.sh:49 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command container/run-container.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 container/run-container.sh:51 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 container/run-script.sh:12 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 container/run-script.sh:3 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 container/run-script.sh:5 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 container/run-script.sh:6 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 native/fmt.sh:10 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 native/fmt.sh:4 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 native/fmt.sh:5 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 native/fmt.sh:9 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/bind-xl710.sh:10 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/bind-xl710.sh:6 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/bind-xl710.sh:7 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/comparisons/kill-ovs-chain.py:10 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/comparisons/kill-ovs-chain.py:11 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/comparisons/kill-ovs-chain.py: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-command-substitution-in-command scripts/comparisons/kill-ovs-chain.py:14 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/kill-ovs-chain.py: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 scripts/comparisons/kill-ovs-chain.py: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 scripts/comparisons/start-bess-chain-vm.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-command-substitution-in-command scripts/comparisons/start-bess-chain-vm.sh:31 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-bess-chain-vm.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 scripts/comparisons/start-bess-chain-vm.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 scripts/comparisons/start-bess-chain-vm.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 scripts/comparisons/start-bess-chain-vm.sh:44 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/comparisons/start-bess-chain-vm.sh:53 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/comparisons/start-bess-chain-vm.sh:55 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-bess-chain-vm.sh:64 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/comparisons/start-bess-chain-vm.sh:73 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/comparisons/start-bess-chain-vm.sh:75 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/comparisons/start-bess-chain-vm.sh:77 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/comparisons/start-bess-chain-vm.sh:83 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/comparisons/start-bess-chain-vm.sh:85 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/comparisons/start-bess-chain.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 scripts/comparisons/start-bess-chain.sh:32 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/comparisons/start-bess-chain.sh:40 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-bess-chain.sh:46 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/comparisons/start-bess-chain.sh:55 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-ovs-chain-vm.sh:104 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/comparisons/start-ovs-chain-vm.sh:113 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/comparisons/start-ovs-chain-vm.sh:115 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/comparisons/start-ovs-chain-vm.sh:117 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/comparisons/start-ovs-chain-vm.sh:12 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/comparisons/start-ovs-chain-vm.sh:123 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-ovs-chain-vm.sh:125 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-command-substitution-in-command scripts/comparisons/start-ovs-chain-vm.sh:19 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-ovs-chain-vm.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 scripts/comparisons/start-ovs-chain-vm.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 scripts/comparisons/start-ovs-chain-vm.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-command-substitution-in-command scripts/comparisons/start-ovs-chain-vm.sh:27 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-ovs-chain-vm.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 scripts/comparisons/start-ovs-chain-vm.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 scripts/comparisons/start-ovs-chain-vm.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 scripts/comparisons/start-ovs-chain-vm.sh:48 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/comparisons/start-ovs-chain-vm.sh:56 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/comparisons/start-ovs-chain-vm.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/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-ovs-chain-vm.sh:59 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-command-substitution-in-command scripts/comparisons/start-ovs-chain-vm.sh:71 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-ovs-chain-vm.sh:73 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/comparisons/start-ovs-chain-vm.sh:74 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/comparisons/start-ovs-chain-vm.sh:81 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/comparisons/start-ovs-chain-vm.sh:84 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/comparisons/start-ovs-chain-vm.sh:93 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/comparisons/start-ovs-chain-vm.sh:95 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/comparisons/start-ovs-chain.sh:11 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-command-substitution-in-command scripts/comparisons/start-ovs-chain.sh:18 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-ovs-chain.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 scripts/comparisons/start-ovs-chain.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-command-substitution-in-command scripts/comparisons/start-ovs-chain.sh:26 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-ovs-chain.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/comparisons/start-ovs-chain.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 scripts/comparisons/start-ovs-chain.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 scripts/comparisons/start-ovs-chain.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 scripts/comparisons/start-ovs-chain.sh:55 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-ovs-chain.sh:56 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/comparisons/start-ovs-chain.sh:58 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/comparisons/start-ovs-chain.sh:63 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/comparisons/start-ovs-chain.sh:68 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/comparisons/start-ovs-chain.sh:76 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/comparisons/start-ovs-test-vm.sh:12 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-command-substitution-in-command scripts/comparisons/start-ovs-test-vm.sh:19 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-ovs-test-vm.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 scripts/comparisons/start-ovs-test-vm.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-command-substitution-in-command scripts/comparisons/start-ovs-test-vm.sh:26 The result of command substitution $(...) or `...`, if unquoted, is split on whitespace or other separators specified by the IFS variable. You should surround it with double quotes to avoid splitting the result. Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command scripts/comparisons/start-ovs-test-vm.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/comparisons/start-ovs-test-vm.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 gitleaks/generic-api-key 3rdparty/dpdk-2.1.0/examples/ip_pipeline/pipeline/pipeline_firewall.c:226 Possible generic-api-key secret in history (commit 98817f15e4); removed from the current tree but still retrievable Secrets (gitleaks)
low gitleaks/generic-api-key 3rdparty/dpdk-2.1.0/examples/ip_pipeline/pipeline/pipeline_flow_classification.c:113 Possible generic-api-key secret in history (commit 98817f15e4); removed from the current tree but still retrievable Secrets (gitleaks)
low gitleaks/generic-api-key 3rdparty/dpdk-2.1.0/lib/librte_table/rte_table_lpm.c:253 Possible generic-api-key secret in history (commit 98817f15e4); removed from the current tree but still retrievable Secrets (gitleaks)
low gitleaks/generic-api-key 3rdparty/dpdk-2.1.0/lib/librte_table/rte_table_lpm_ipv6.c:264 Possible generic-api-key secret in history (commit 98817f15e4); removed from the current tree but still retrievable Secrets (gitleaks)
low opengrep/rust.lang.security.unsafe-usage debugging/rdtscp-test/src/main.rs:20 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage debugging/rdtscp-test/src/main.rs:34 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage debugging/rdtscp-test/src/main.rs:7 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/allocators/cache_aligned.rs:19 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/allocators/cache_aligned.rs:31 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/allocators/cache_aligned.rs:37 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/allocators/cache_aligned.rs:43 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/allocators/cache_aligned.rs:58 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.args framework/src/config/flag_reader.rs:31 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 framework/src/control/linux/epoll.rs:100 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/control/linux/epoll.rs:98 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/headers/ip.rs:76 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/dpdk.rs:13 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/dpdk.rs:40 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/dpdk.rs:79 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/dpdk.rs:94 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:101 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:205 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:235 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:244 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:249 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:254 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:264 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:269 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:275 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:286 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:298 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:304 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:333 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:345 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:360 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:368 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:383 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:393 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:403 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:416 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:429 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:437 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:451 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:459 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:468 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:476 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:481 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:499 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:507 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:52 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/packet.rs:87 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:130 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:136 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:197 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:198 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:203 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:239 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:263 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:295 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:43 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:440 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:68 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/phy_port.rs:78 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/virt_port.rs:33 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/interface/port/virt_port.rs:46 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:119 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:126 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:130 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:135 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:141 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:147 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:153 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:160 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:165 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:170 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:174 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:181 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:186 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/libnuma.rs:98 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/zcsi/mbuf.rs:119 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/zcsi/mbuf.rs:124 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/zcsi/mbuf.rs:17 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/zcsi/mbuf.rs:35 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/native/zcsi/mbuf.rs:9 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/operators/iterator.rs:78 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/operators/packet_batch.rs:109 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/operators/packet_batch.rs:187 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/operators/packet_batch.rs:204 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/operators/packet_batch.rs:258 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/operators/packet_batch.rs:283 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/operators/packet_batch.rs:79 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/queues/mpsc_mbuf_queue.rs:230 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/queues/mpsc_mbuf_queue.rs:235 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/shared_state/directory.rs:37 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/shared_state/directory.rs:63 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/shared_state/directory.rs:75 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/shared_state/directory.rs:82 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/shared_state/mod.rs:19 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/shared_state/shared_vec.rs:17 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/utils/asm.rs:15 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/utils/asm.rs:3 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/utils/asm.rs:31 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/utils/asm.rs:43 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/utils/flow.rs:120 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/utils/flow.rs:128 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage framework/src/utils/flow.rs:133 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.

AnalyzerPillarStatusVersionFindingsNote
AI tool configurationAI provenanceoksignatures-v10
Explicit AI attributionAI provenanceoksignatures-v10
Release velocityAI provenanceskipped—0
Coding styleAI provenanceok—0
Commit velocityAI provenanceokprov-40
Complexity (lizard)Code qualityoklizard 1.25.10
DocumentationCode qualityok—0
Duplication (jscpd)Code qualityokrepotrust-dup-w60
LintCode qualityokopengrep 1.33.1; rules f1d2b562b414200
Tests and CICode qualityok—0
Type safetyCode qualityok—0
CI workflows (zizmor)Securityskipped—0
Dependencies (osv-scanner)Securityskipped—0
Release downloadsSecurityok—0
Security postureSecurityok—0
Package registriesSecurityok—0
Static analysis (opengrep)Securityokopengrep 1.33.1; rules f1d2b562b414112
OpenSSF ScorecardSecurityskipped—0no published OpenSSF Scorecard result for this repo
Secrets (gitleaks)Securityokgitleaks 8.30.14

Score history

Scores from different scoring versions aren't directly comparable.

ScoredCommitScoringAI provenanceQualitySecurity
2026-11-1471dfb94beaeaprov-5+qual-2+sec-20%5553
2026-11-1471dfb94beaeaprov-4+qual-2+sec-20%5553

Embed a badge

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

[![RepoTrust ai](https://repotrust.synapticcyber.com/badge/github.com/NetSys/NetBricks/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/NetSys/NetBricks/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/NetSys/NetBricks/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/NetSys/NetBricks/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/NetSys/NetBricks/security.svg)](https://repotrust.synapticcyber.com/r/github.com/NetSys/NetBricks/)
Full text report
  • Repository: https://github.com/NetSys/NetBricks
  • Commit: 71dfb94beaeac107d7cd359985f9bd66fd223e1b
  • Generated: 2026-11-14T14:52:01+00:00
  • Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2

Scores

Pillar Score Signal Confidence Coverage
AI provenance (estimated AI-generated share) 0 none-detected 65% 100%
Code quality 55 weak 90% 100%
Security 53 weak 85% 100%

AI provenance

No AI attribution or AI-consistent velocity signals detected.

  • Explicitly attributed share (lower bound): 0.0%
  • Unattributed share in AI-consistent velocity bursts: 0.0%
  • Estimated AI-generated share: 0.0%
Month Lines added Attributed to AI
2017-03 8 0%
2017-05 1,127 0%
2017-06 3,107 0%
2017-07 12 0%
2017-08 3 0%
2017-10 94 0%
2017-12 412 0%
2018-02 20 0%
2018-03 8 0%
2018-04 13 0%
2018-05 7 0%
2019-01 3 0%

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

Code quality

Code quality is weak: test-to-source ratio 0.37, no CI test run detected; 3% of function code in complex or long functions; 18% duplicated lines. Weakest area: lint.

Area Score
Complexity (lizard) 90
Duplication 34
Code smells (Opengrep) 15
Tests and CI 64
Documentation 65
Type safety 40
Process (Scorecard review/maintenance) n/a
  • Functions: 706; mean complexity 1.6, 90th percentile 3; 2 complex and 1 long functions
  • Duplicated lines: 18.1% of 7,938 compared
  • Tests: 4,227 test lines for 11,358 source lines (ratio 0.37); CI test commands: none detected; 39% of recent source commits also change tests
  • Docs missing or thin: contributing, changelog

Most complex functions:

Security

Security posture is weak: 4 high-severity SAST findings. Weakest area: posture.

Area Score
Secrets (gitleaks, tree + history) 88
Static analysis (Opengrep) 36
Vulnerable dependencies (OSV) n/a
CI workflows (zizmor) n/a
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/dockerfile.security.missing-user: By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'. [confidence medium] build-container/Dockerfile:18
high opengrep/dockerfile.security.missing-user: By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'. [confidence medium] container/Dockerfile:41
high opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'check_call' 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] container/run-script.py:17
high opengrep/python.lang.security.audit.dangerous-subprocess-use-tainted-env-args: Detected subprocess function 'check_call' with user controlled data. A malicious actor could leverage this to perform command injection. You may consider using 'shlex.quote()'. [confidence medium] container/run-script.py:17
medium opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] native/init.c:163
medium opengrep/c.lang.security.insecure-use-string-copy-fn: Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker [confidence low] native/init.c:180
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] native/mempool.c:138
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] native/pmd.c:57
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] native/pmd.c:98
medium opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] native/ring.c:52
low gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 98817f15e4); removed from the current tree but still retrievable 3rdparty/dpdk-2.1.0/examples/ip_pipeline/pipeline/pipeline_flow_classification.c:113
low gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 98817f15e4); removed from the current tree but still retrievable 3rdparty/dpdk-2.1.0/examples/ip_pipeline/pipeline/pipeline_firewall.c:226
low gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 98817f15e4); removed from the current tree but still retrievable 3rdparty/dpdk-2.1.0/lib/librte_table/rte_table_lpm.c:253
low gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 98817f15e4); removed from the current tree but still retrievable 3rdparty/dpdk-2.1.0/lib/librte_table/rte_table_lpm_ipv6.c:264
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] debugging/rdtscp-test/src/main.rs:7
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] debugging/rdtscp-test/src/main.rs:20
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] debugging/rdtscp-test/src/main.rs:34
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] framework/src/allocators/cache_aligned.rs:19
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] framework/src/allocators/cache_aligned.rs:31
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] framework/src/allocators/cache_aligned.rs:37
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] framework/src/allocators/cache_aligned.rs:43
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] framework/src/allocators/cache_aligned.rs:58
low opengrep/rust.lang.security.args: 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 upon for security purposes." [confidence high] framework/src/config/flag_reader.rs:31
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] framework/src/control/linux/epoll.rs:98
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] framework/src/control/linux/epoll.rs:100

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: 11,358; test lines: 4,227
Language Lines
Rust 12,326
Shell 1,684
C 1,242
Python 333