RepoTrust

Leaderboard github.com

Lakr233/vphone-cli

Run a virtual iPhone on an Apple Silicon Mac.

  • View repository ↗
  • Swift
  • ★ 16,667
  • commit 131694050139
  • scored 2026-11-14
  • scoring prov-5+qual-2+sec-2

unreviewed-ai-risk

AI provenance

67%

explicit

Confidence
95%
Coverage
100%

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

Code quality

60/100

weak

Confidence
90%
Coverage
100%

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

Security

70/100

adequate

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

67% explicit

Explicit AI attribution on 67% of first-party code added; an estimated 67% including velocity signals.

How the score is built

  • Explicitly attributed share67%
  • Unattributed share in AI-pace bursts10%
  • Estimated AI-generated share67%
  • AI tool configuration files1
  • Work sessions at AI pace55
  • Releases at AI pace14
  • Coding-style index (1.0+ means possible)0.17

Attributed AI tools

ToolCommitsLines addedFirst seenLast seen
Claude Code920287,0172026-03-012026-11-13
OpenAI Codex567,2292026-03-042026-11-06
Devin122026-04-072026-04-07

Lines added per month all AI-attributed share

  1. 2026-027,559 · 0% AI
  2. 2026-0350,750 · 6% AI
  3. 2026-04498 · 27% AI
  4. 2026-054,191 · 0% AI
  5. 2026-068,468 · 86% AI
  6. 2026-079,061 · 91% AI
  7. 2026-081,880 · 97% AI
  8. 2026-09163,029 · 86% AI
  9. 2026-10149,605 · 78% AI
  10. 2026-1144,808 · 38% AI

Findings in AI-attributed lines vs the rest

From git blame: 228,500 lines trace to AI-attributed commits, 81,382 to others. Reported, not scored.

Findings per 1,000 linesAI-attributedOtherRatio
Code quality0.850.0613.98×
Security0.590.173.44×

Evidence by analyzer

Explicit AI attributionok28 items
attributed_commit_share
65.0%
attributed_commits
977
attributed_loc
294,248
attributed_loc_share
66.9%
commits
1,503
effective_loc
439,849
tools_detected
3
AI tool configurationok1 item
artifacts
1
earliest_adoption
2026-02-27
tools_configured
1
workflow_agents
0
Commit velocityok15 items
excluded_import_loc
110,269
flagged_loc
184,935
flagged_loc_share
56.1%
flagged_units
55
max_loc_per_hour
6,871.57
measured_loc
329,580
median_loc_per_hour
146.19
pr_timed_units
124
pre_ai_era_burst_loc
0
pre_ai_era_bursts
0
pre_ai_era_measured_loc
0
work_units
566
Release velocityok14 items
flagged_releases
14
max_loc_per_day
205,358.10
releases
90
Coding styleok8 items
count:assistant_voice
1
count:emoji_in_code
31
count:narrated_steps
34
count:placeholder
0
files:assistant_voice
1
files:emoji_in_code
7
files:narrated_steps
15
files:placeholder
0
index
0.17
lines_scanned
309,882
per_kloc:assistant_voice
0.00
per_kloc:emoji_in_code
0.10
per_kloc:narrated_steps
0.11
per_kloc:placeholder
0
Findings in AI-written linesok
ai_lines
228,500
blame_failures
0
files_blamed
1,408
other_lines
81,382
quality:ai_findings
195
quality:ai_per_kloc
0.85
quality:other_findings
5
quality:other_per_kloc
0.06
quality:ratio
13.98
security:ai_findings
135
security:ai_per_kloc
0.59
security:other_findings
14
security:other_per_kloc
0.17
security:ratio
3.44

Code quality

60 weak

Code quality is weak: test-to-source ratio 0.00, no CI test run detected; 23% of function code in complex or long functions; 4% duplicated lines. Weakest area: testing.

How the score is built

  • Complexity50
  • Duplication80
  • Lint and smells96
  • Tests and CI36
  • Documentation65
  • Type safety40
  • Review processnot measured

Evidence by analyzer

Complexity (lizard)ok10 items
complex_functions
503
function_nloc
170,546
functions
11,308
long_functions
89
many_param_functions
64
mean_ccn
4.42
p90_ccn
10
risky_nloc_share
22.8%
Duplication (jscpd)ok10 items
compared_lines
235,226
duplicated_lines
8,809
duplicated_share
3.7%
files
1,408
Lintok
category:correctness
205
findings
205
scanned_lines
284,897
weighted_findings
52
Tests and CIok4 items
  • CI config: .github/workflows/build.yml .github/workflows/build.yml
  • CI config: .github/workflows/package.yml .github/workflows/package.yml
  • CI config: .github/workflows/release.yml .github/workflows/release.yml
  • CI config: .github/workflows/website.yml .github/workflows/website.yml
check:ci_present
yes
check:ci_runs_lint
no
check:ci_runs_tests
no
check:has_tests
yes
check:test_ratio
no
check:tests_cochange
no
ci_files
4
cochange_commits
252
cochange_share
1.6%
source_lines
309,882
test_lines
142
test_ratio
0.00
Documentationok2 items
  • README.md README.md
  • LICENSE LICENSE
check:changelog
no
check:contributing
no
check:license
yes
check:readme
yes
readme_lines
31
Type safetyok
check:low_escape_density
yes
check:strict_config
no
escapes
0
escapes_per_kloc
0

Security

70 adequate

Security posture is adequate: 14 high-severity workflow issues. Weakest area: posture.

How the score is built

  • Secrets94
  • Static analysis (SAST)96
  • Vulnerable dependencies100
  • CI workflows6
  • Security posture0
  • OpenSSF Scorecardnot measured

Evidence by analyzer

OpenSSF Scorecardskipped

no published OpenSSF Scorecard result for this repo

Package registriesok
checked
1
declared
1
lookup_errors
0
missing
0
recent
0
Secrets (gitleaks)ok
secrets_current
0
secrets_history
0
secrets_low_confidence
2
secrets_nonprod
0
Static analysis (opengrep)ok
findings
147
findings_high
0
findings_low
0
findings_medium
147
parse_errors
122
scanned_lines
284,897
weighted_findings
36.75
Dependencies (osv-scanner)ok
penalty
0
vulnerabilities
0
vulnerable_packages
0
vulns_critical
0
vulns_high
0
vulns_low
0
vulns_medium
0
vulns_unknown
0
CI workflows (zizmor)ok
findings
19
findings_high
14
findings_low
0
findings_medium
5
penalty
174
workflows
4
Security postureok
check:dependency_updates
no
check:lockfiles
yes
check:security_policy
no
check:signed_commits
no
signed_commit_share
44.5%
unpinned_manifests
0
Release downloadsok5 items
binary_assets
24
signals
1
suspicious
0

Findings

14 high153 medium201 low

SeverityRuleLocationMessageTool
high zizmor/unpinned-uses .github/workflows/build.yml:17 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/build.yml:66 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/package.yml:14 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/package.yml:57 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/package.yml:68 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/release.yml:102 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/release.yml:133 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/excessive-permissions .github/workflows/release.yml:19 overly broad permissions [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/release.yml:26 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/release.yml:59 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/website.yml:37 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/website.yml:40 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/website.yml:54 unpinned action reference [confidence high] CI workflows (zizmor)
high zizmor/unpinned-uses .github/workflows/website.yml:71 unpinned action reference [confidence high] CI workflows (zizmor)
medium opengrep/c.lang.correctness.incorrect-use-ato-fn VPhoneExecutable/VPhoneEscalator/VPhoneEscalator/VPhoneEscalator.c:121 Avoid the 'ato*()' family of functions. Their use can lead to undefined behavior, integer overflows, and lack of appropriate error handling. Instead prefer the 'strtol*()' family of functions. Lint
medium zizmor/artipacked .github/workflows/build.yml:16 credential persistence through GitHub Actions artifacts [confidence low] CI workflows (zizmor)
medium zizmor/artipacked .github/workflows/package.yml:13 credential persistence through GitHub Actions artifacts [confidence low] CI workflows (zizmor)
medium zizmor/artipacked .github/workflows/release.yml:101 credential persistence through GitHub Actions artifacts [confidence low] CI workflows (zizmor)
medium zizmor/artipacked .github/workflows/release.yml:25 credential persistence through GitHub Actions artifacts [confidence low] CI workflows (zizmor)
medium zizmor/artipacked .github/workflows/website.yml:36 credential persistence through GitHub Actions artifacts [confidence low] CI workflows (zizmor)
medium opengrep/c.lang.security.insecure-use-memset VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1024 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1279 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1286 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1438 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1497 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1541 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1619 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:2059 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:2066 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:2641 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:2678 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:2797 When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:2842 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:3042 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:3627 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:3976 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:4026 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:4043 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:4068 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:4131 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-strtok-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:4182 Avoid using 'strtok()'. This function directly modifies the first argument buffer, permanently erasing the delimiter character. Use 'strtok_r()' instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strtok-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:4196 Avoid using 'strtok()'. This function directly modifies the first argument buffer, permanently erasing the delimiter character. Use 'strtok_r()' instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-memset VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:4233 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:4258 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.function-use-after-free VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:4543 Variable 'new_client' was passed to a function after being freed. This can lead to undefined behavior. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-memset VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:824 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:825 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:854 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Bridge/vphone_zip_stub.c:144 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.function-use-after-free VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/common.c:360 Variable 'found->label' was passed to a function after being freed. This can lead to undefined behavior. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/common.c:654 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/common.c:655 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:1159 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:1181 When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:1357 Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strcat-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:1358 Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:1360 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:1606 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:1816 When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:205 Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strcat-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:206 Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strcat-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:207 Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:209 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:214 Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strcat-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:215 Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.function-use-after-free VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:2736 Variable 'NULL' was passed to a function after being freed. This can lead to undefined behavior. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:469 Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strcat-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:470 Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strcat-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:471 Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:473 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:906 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:914 Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strcat-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:915 Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strtok-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:927 Avoid using 'strtok()'. This function directly modifies the first argument buffer, permanently erasing the delimiter character. Use 'strtok_r()' instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strtok-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:934 Avoid using 'strtok()'. This function directly modifies the first argument buffer, permanently erasing the delimiter character. Use 'strtok_r()' instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:942 Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strcat-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:943 Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strcat-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:944 Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Core/idevicerestore.c:984 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Firmware/Containers/fls.c:110 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Firmware/Containers/fls.c:277 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Firmware/Containers/fls.c:55 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Firmware/Containers/fls.c:66 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Firmware/Containers/fls.c:76 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Firmware/Containers/fls.c:85 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Firmware/Containers/ftab.c:159 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Firmware/Images/img3.c:210 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Firmware/Images/img3.c:50 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/dfu.c:194 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/dfu.c:51 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/limera1n.c:109 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/limera1n.c:118 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/limera1n.c:85 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/limera1n.c:97 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.function-use-after-free VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/normal.c:117 Variable 'NULL' was passed to a function after being freed. This can lead to undefined behavior. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.function-use-after-free VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/normal.c:70 Variable 'NULL' was passed to a function after being freed. This can lead to undefined behavior. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-memset VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/openavb.c:241 When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/recovery.c:514 Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strcat-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/recovery.c:515 Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-memset VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Recovery/recovery.c:75 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/asr.c:88 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/fdr.c:317 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/fdr.c:395 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/ipsw.c:1060 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.function-use-after-free VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/ipsw.c:1121 Variable 'NULL' was passed to a function after being freed. This can lead to undefined behavior. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-memset VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/ipsw.c:1156 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.function-use-after-free VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/ipsw.c:259 Variable 'NULL' was passed to a function after being freed. This can lead to undefined behavior. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.function-use-after-free VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/ipsw.c:271 Variable 'NULL' was passed to a function after being freed. This can lead to undefined behavior. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-memset VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/ipsw.c:340 When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/ipsw.c:516 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/restore.c:1246 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/restore.c:1251 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/restore.c:1583 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/restore.c:1587 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/restore.c:1602 When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/restore.c:2351 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/restore.c:2352 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/restore.c:2353 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/restore.c:2844 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/restore.c:3957 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 VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRestoreCore/Transfer/restore.c:468 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 VPhoneExecutable/VPhoneEscalator/VPhoneEscalator/AMFIDTask.c:106 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 VPhoneGuestComponents/DeviceName/libdevicename.c:228 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 VPhoneGuestComponents/LaunchHook/VPhoneX1Exception.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 VPhoneGuestComponents/LaunchHook/VPhoneX1Exception.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-string-copy-fn VPhoneGuestComponents/Shared/RootHideLoaderLinks.c:191 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 VPhoneGuestComponents/Shared/RootHideLoaderLinks.c:203 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 VPhoneGuestComponents/Shared/RootHideLoaderLinks.c:206 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 VPhoneGuestComponents/Shared/RootHideLoaderLinks.c:43 Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows,... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-strcat-fn VPhoneGuestComponents/Shared/RootHideLoaderLinks.c:55 Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. [confidence low] Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-memset VPhoneGuestComponents/SystemHook/VPhoneIOS16SurfaceReply.c:39 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 VPhoneGuestComponents/SystemHook/VPhoneIOS16SurfaceReply.c:5 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 VPhoneGuestComponents/SystemHook/VPhoneIOS18GPUTransport.c:32 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 VPhoneGuestComponents/Tests/DeviceNameTests.c:96 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 VPhoneGuestComponents/Tests/FlutterRemapRepairTests.c:24 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 VPhoneGuestComponents/Tests/FlutterRemapRepairTests.c:33 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 VPhoneGuestComponents/Tests/FlutterRemapRepairTests.c:33 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 VPhoneGuestComponents/Tests/IOS16SurfaceReplyTest.c:15 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 VPhoneGuestComponents/Tests/IOS16SurfaceReplyTest.c:22 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 VPhoneGuestComponents/Tests/IOS16SurfaceReplyTest.c:36 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 VPhoneGuestComponents/Tests/IOS18GPUTransportTest.c:26 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 VPhoneGuestComponents/Tests/IOS18GPUTransportTest.c:42 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 VPhoneGuestComponents/Tests/InstallCoordinationPersonaTests.c:21 When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... Static analysis (opengrep)
medium opengrep/c.lang.security.insecure-use-string-copy-fn VPhoneGuestComponents/Tests/RootHideLoaderLinksTests.c:30 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 VPhoneGuestComponents/Tests/RootHideLoaderLinksTests.c:39 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 VPhoneGuestComponents/Tests/VCamPrewarmScanTests.c:126 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 VPhoneGuestComponents/Tests/VirtIOSoundTests.c:102 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 VPhoneGuestComponents/Tests/VirtIOSoundTests.c:29 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 VPhoneGuestComponents/Tests/VirtIOSoundTests.c:325 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 VPhoneGuestComponents/VCamDataPlane/vcam_dataplane.c:31 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 VPhoneGuestComponents/VCamDataPlane/vcam_dataplane.c:441 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundClock.c:46 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundFilter.c:29 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundProtocol.c:40 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundProtocol.c:89 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundRing.c:10 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundRing.c:116 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundRing.c:124 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundRing.c:135 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundRing.c:18 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundRing.c:232 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundRing.c:29 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 VPhoneGuestComponents/VirtIOSound/VPVirtIOSoundRing.c:43 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 VPhoneGuestComponents/VisionOSIPC/Tests/VisionOSIPCTests.c:51 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 VPhoneGuestComponents/VisionOSIPC/Tests/VisionOSIPCTests.c:69 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/javascript.lang.security.audit.detect-non-literal-regexp VPhoneWebsite/scripts/sync-docs.mjs:165 RegExp() called with a `paragraph` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to... Static analysis (opengrep)
medium opengrep/javascript.lang.security.html-in-template-string VPhoneWebsite/scripts/sync-docs.mjs:359 This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... Static analysis (opengrep)
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/appkit-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/appkit-merge.zsh:17 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/appkit-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/appkit-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/appkit-merge.zsh:25 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/appkit-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/appkit-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/appkit-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/appkit-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/appkit-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/chrome-build.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/chrome-build.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/chrome-build.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh:31 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh:35 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh:35 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh:37 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh:38 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/springboard-run.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-app-keys.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-chrome-keys.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-compare.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-compare.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-compare.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-convert.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-convert.zsh:38 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/vm-convert.zsh:38 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-command-substitution-in-command Research/Guest/Evidence/duo-sim-baseline/probes/vm-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-merge.zsh:25 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/vm-merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-merge.zsh:38 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/vm-merge.zsh:38 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/vm-merge.zsh:39 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/probes/vm-retag.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-retag.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-retag.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-retag.zsh: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 Research/Guest/Evidence/duo-sim-baseline/probes/vm-summary.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/appkit/probe-app/build.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/appkit/probe-app/build.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/appkit/probe-app/build.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/appkit/probe-app/build.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/appkit/probe-app/build.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/appkit/probe-app/build.zsh:8 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/capture.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/diffstates.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/diffstates.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/diffstates.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/diffstates.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/diffstates.zsh:8 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/display/gen-probe.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/gen-probe.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/iterate.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/iterate.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/iterate.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/iterate.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/iterate.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/iterate.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/iterate.zsh:8 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/display/iterate.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh:19 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh:19 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh:8 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/display/merge.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/orient-cycle.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/orient-cycle.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/orient-cycle.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/orient-cycle.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/orient-cycle.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/orient-cycle.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/orient-cycle.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/orient-cycle.zsh:19 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/display/orient-cycle.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/orient-cycle.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/orient.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/display/orient.zsh:8 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:111 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:25 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:30 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:36 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:38 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:39 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:43 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:45 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:54 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:61 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:71 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:71 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:79 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:80 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:86 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:88 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/sensors/run-sensors.zsh:94 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/vm/merge-fix.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/vm/merge-fix.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/vm/merge-fix.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/vm/merge-fix.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/vm/merge-fix.zsh:35 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/vm/merge-fix.zsh:35 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/vm/merge-fix.zsh:36 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/src/vm/run-lockchrome.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/vm/run-lockchrome.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/vm/run-lockchrome.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/vm/run-lockchrome.zsh: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 Research/Guest/Evidence/duo-sim-baseline/src/vm/run-lockchrome.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:100 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:107 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is 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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:108 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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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-command-substitution-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:109 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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:109 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:109 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:114 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:116 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:119 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:120 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:39 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:66 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:71 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh: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 Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:96 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:96 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:98 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:98 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command Research/Guest/Evidence/duo-sim-baseline/tools/sim.zsh:99 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command VPhoneDaemon/Tests/run-cached-binary-identity-tests.sh:8 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command VPhoneDaemon/Tests/run-methods-live-stub-tests.sh:182 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command VPhoneDaemon/Tests/run-methods-live-stub-tests.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 VPhoneDaemon/Tests/run-methods-live-stub-tests.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 VPhoneDaemon/Tests/run-methods-live-stub-tests.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 VPhoneDaemon/Tests/run-methods-live-stub-tests.sh:190 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command VPhoneDaemon/Tests/run-methods-live-stub-tests.sh:192 Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... Lint
low opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command VPhoneDaemon/Tests/run-methods-live-stub-tests.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 VPhoneDaemon/Tests/run-methods-live-stub-tests.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 VPhoneDaemon/Tests/run-methods-live-stub-tests.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 VPhoneExecutable/VPhoneVirtualization/Build/StageBundle.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 gitleaks/generic-api-key VPhoneKit/VPhoneCoreKit/Firmware/VPhoneFirmwareCatalog.swift:625 Possible generic-api-key secret in the current tree Secrets (gitleaks)
low gitleaks/generic-api-key VPhoneKit/VPhoneCoreKitTests/Firmware/FirmwareCatalogReportTests.swift:15 Possible generic-api-key secret in the current tree Secrets (gitleaks)

Tools and coverage

Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.

AnalyzerPillarStatusVersionFindingsNote
AI tool configurationAI provenanceoksignatures-v10
Explicit AI attributionAI provenanceoksignatures-v10
Release velocityAI provenanceokprov-50
Coding styleAI provenanceok—0
Commit velocityAI provenanceokprov-50
Findings in AI-written linesAI provenanceokgit-blame0
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)Securityokzizmor 1.32.019
Dependencies (osv-scanner)Securityokosv-scanner version: 2.7.10
Release downloadsSecurityok—0
Security postureSecurityok—0
Package registriesSecurityok—0
Static analysis (opengrep)Securityokopengrep 1.33.1; rules f1d2b562b414147
OpenSSF ScorecardSecurityskipped—0no published OpenSSF Scorecard result for this repo
Secrets (gitleaks)Securityokgitleaks 8.30.12

Score history

ScoredCommitScoringAI provenanceQualitySecurity
2026-11-14131694050139prov-5+qual-2+sec-267%6070

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/Lakr233/vphone-cli/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/Lakr233/vphone-cli/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/Lakr233/vphone-cli/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/Lakr233/vphone-cli/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/Lakr233/vphone-cli/security.svg)](https://repotrust.synapticcyber.com/r/github.com/Lakr233/vphone-cli/)
Full text report
  • Repository: https://github.com/Lakr233/vphone-cli
  • Commit: 1316940501398ea279f960ee7d838f93885730d4
  • Generated: 2026-11-14T16:23:57+00:00
  • Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2

Scores

Unreviewed AI code risk: a large share of this code is explicitly AI-attributed, and its tests or review process are weak while quality or security scores are low.

Pillar Score Signal Confidence Coverage
AI provenance (estimated AI-generated share) 67 explicit 95% 100%
Code quality 60 weak 90% 100%
Security 70 adequate 85% 100%

AI provenance

Explicit AI attribution on 67% of first-party code added; an estimated 67% including velocity signals.

  • Explicitly attributed share (lower bound): 66.9%
  • Unattributed share in AI-consistent velocity bursts: 10.4%
  • Estimated AI-generated share: 66.9%
AI tool Attributed commits Lines added
Claude Code 920 287,017
OpenAI Codex 56 7,229
Devin 1 2
  • AI tooling configured in repo: generic-agent

Current source lines last changed by AI-attributed commits: 228,500 of 309,882.

Findings per 1,000 lines AI-attributed Other Ratio
Quality 0.853 0.061 13.98x
Security 0.591 0.172 3.44x
  • Stylometry index: 0.17 per 1,000 lines (narrated steps 34, placeholders 0, assistant phrasing 1, emoji 31). Reported as a signal, not scored.
Month Lines added Attributed to AI
2026-02 7,559 0%
2026-03 50,750 6%
2026-04 498 27%
2026-05 4,191 0%
2026-06 8,468 86%
2026-07 9,061 91%
2026-08 1,880 97%
2026-09 163,029 86%
2026-10 149,605 78%
2026-11 44,808 38%

Evidence

  • Claude Code: trailer 'Co-Authored-By: Claude' (131694050139)
  • Claude Code: trailer 'Co-Authored-By: Claude' (a08b5b1008ab)
  • Claude Code: trailer 'Co-Authored-By: Claude' (c9b2f334405a)
  • Claude Code: trailer 'Co-Authored-By: Claude' (fd2ff6f25733)
  • Claude Code: trailer 'Co-Authored-By: Claude' (9495c388e2f4)
  • Claude Code: trailer 'Co-Authored-By: Claude' (8a4d35cf897e)
  • Claude Code: trailer 'Co-Authored-By: Claude' (c67a8c4f7d6f)
  • Claude Code: trailer 'Co-Authored-By: Claude' (33723dd97093)
  • Claude Code: trailer 'Co-Authored-By: Claude' (050bf3bd1038)
  • Claude Code: trailer 'Co-Authored-By: Claude' (53c75b8252f2)
  • Claude Code: trailer 'Co-Authored-By: Claude' (f84e8214dff7)
  • Claude Code: trailer 'Co-Authored-By: Claude' (d57bd43dd04c)
  • Claude Code: trailer 'Co-Authored-By: Claude' (91eb87fb93e7)
  • Claude Code: trailer 'Co-Authored-By: Claude' (24fc4034b1c3)
  • Claude Code: trailer 'Co-Authored-By: Claude' (22703e398e80)

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.00, no CI test run detected; 23% of function code in complex or long functions; 4% duplicated lines. Weakest area: testing.

Area Score
Complexity (lizard) 50
Duplication 80
Code smells (Opengrep) 96
Tests and CI 36
Documentation 65
Type safety 40
Process (Scorecard review/maintenance) n/a
  • Functions: 11,308; mean complexity 4.4, 90th percentile 10; 503 complex and 89 long functions
  • Duplicated lines: 3.7% of 235,226 compared
  • Tests: 142 test lines for 309,882 source lines (ratio 0.00); CI test commands: none detected; 2% of recent source commits also change tests
  • Docs missing or thin: contributing, changelog

Most complex functions:

Security

Security posture is adequate: 14 high-severity workflow issues. Weakest area: posture.

Area Score
Secrets (gitleaks, tree + history) 94
Static analysis (Opengrep) 96
Vulnerable dependencies (OSV) 100
CI workflows (zizmor) 6
Posture (policy, updates, signing, lockfiles) 0
OpenSSF Scorecard n/a
  • Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits

Top findings

Severity Finding Location
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/build.yml:17
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/build.yml:66
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/package.yml:14
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/package.yml:57
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/package.yml:68
high zizmor/excessive-permissions: overly broad permissions [confidence high] .github/workflows/release.yml:19
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/release.yml:26
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/release.yml:59
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/release.yml:102
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/release.yml:133
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/website.yml:37
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/website.yml:40
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/website.yml:54
high zizmor/unpinned-uses: unpinned action reference [confidence high] .github/workflows/website.yml:71
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] VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:824
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] VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:825
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] VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:854
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] VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1024
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] VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1279
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] VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1286
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] VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1438
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] VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1497
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] VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1541
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] VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:1619
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] VPhoneExecutable/VPhoneCommand/VPhoneRestore/MobileRecoveryCore/libirecovery.c:2059

Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.

Distribution signals

Signals consistent with a repository that exists to distribute a download. They are heuristics, not a verdict; release files were not downloaded or inspected.

Repository profile

  • Source lines: 309,882; test lines: 142
Language Lines
Swift 235,670
C 43,077
Objective-C 24,985
Shell 5,816
JavaScript 397
TypeScript 79