mudler / LocalAI

Large result: showing the top 417 of 605 findings (up to 200 per engine, most severe and most likely real first). Totals above include everything.

1. high Semgrep Detected non-static command inside Exec. Audit the input to 'syscall.Exec'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /core/cli/worker/worker_ds4.go:104 100%
2. high Semgrep Detected non-static command inside Exec. Audit the input to 'syscall.Exec'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /core/cli/worker/worker_ds4.go:107 100%
3. high Semgrep Detected non-static command inside Exec. Audit the input to 'syscall.Exec'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /core/cli/worker/worker_llamacpp.go:88 100%
4. high Semgrep Detected non-static command inside Exec. Audit the input to 'syscall.Exec'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /core/cli/worker/worker_mlx_distributed.go:57 100%
5. high Semgrep Found an insecure gRPC connection using 'insecure.NewCredentials()'. This creates a connection without encryption to a gRPC server. A malicious attacker could tamper with the gRPC message, which could compromise the machine. Instead, establish a secure connection with an SSL certificate using the 'grpc.WithTransportCredentials()' function. You can create a create credentials using a 'tls.Config{}' struct with 'credentials.NewTLS()'. The final fix looks like this: 'grpc.WithTransportCredentials(credentials.NewTLS(<config>))'. /pkg/grpc/client.go:74 99%
6. high Semgrep Detected user input entering a `subprocess` call unsafely. This could result in a command injection vulnerability. An attacker could use this vulnerability to execute arbitrary commands on the host, which allows them to download malware, scan sensitive data, or run any command they wish on the server. Do not let users choose the command to run. In general, prefer to use Python API versions of system commands. If you must use subprocess, use a dictionary to allowlist a set of commands. /backend/python/mlx-video/backend.py:111 99%
7. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:101 99%
8. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:495 99%
9. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:473 99%
10. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:447 99%
11. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:426 99%
12. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:405 99%
13. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:362 99%
14. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:341 99%
15. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:320 99%
16. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:299 99%
17. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:148 99%
18. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:124 99%
19. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/lint.yml:69 99%
20. high Semgrep A `run:` step pipes the output of `curl` or `wget` directly into a shell interpreter. This is the "curl | bash" install pattern — if the remote server is compromised or the URL is hijacked, an attacker can execute arbitrary code in your CI runner. Consider downloading the file first, verifying its checksum or signature, and then executing it. /.github/workflows/test-extra.yml:1247 99%
21. high Semgrep This GitHub Actions workflow file uses `pull_request_target` and checks out code from the incoming pull request. When using `pull_request_target`, the Action runs in the context of the target repository, which includes access to all repository secrets. Normally, this is safe because the Action only runs code from the target repository, not the incoming PR. However, by checking out the incoming PR code, you're now using the incoming code for the rest of the action. You may be inadvertently executing arbitrary code from the incoming PR with access to repository secrets, which would let an attacker steal repository secrets. This normally happens by running build scripts (e.g., `npm build` and `make`) or dependency installation scripts (e.g., `python setup.py install`). Audit your workflow file to make sure no code from the incoming PR is executed. Please see https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ for additional mitigations. /.github/workflows/disabled/comment-pr.yaml:11 99%
22. high Semgrep This GitHub Actions workflow file uses `pull_request_target` and checks out code from the incoming pull request. When using `pull_request_target`, the Action runs in the context of the target repository, which includes access to all repository secrets. Normally, this is safe because the Action only runs code from the target repository, not the incoming PR. However, by checking out the incoming PR code, you're now using the incoming code for the rest of the action. You may be inadvertently executing arbitrary code from the incoming PR with access to repository secrets, which would let an attacker steal repository secrets. This normally happens by running build scripts (e.g., `npm build` and `make`) or dependency installation scripts (e.g., `python setup.py install`). Audit your workflow file to make sure no code from the incoming PR is executed. Please see https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ for additional mitigations. /.github/workflows/disabled/notify-models.yaml:18 99%
23. high Semgrep This GitHub Actions workflow file uses `pull_request_target` and checks out code from the incoming pull request. When using `pull_request_target`, the Action runs in the context of the target repository, which includes access to all repository secrets. Normally, this is safe because the Action only runs code from the target repository, not the incoming PR. However, by checking out the incoming PR code, you're now using the incoming code for the rest of the action. You may be inadvertently executing arbitrary code from the incoming PR with access to repository secrets, which would let an attacker steal repository secrets. This normally happens by running build scripts (e.g., `npm build` and `make`) or dependency installation scripts (e.g., `python setup.py install`). Audit your workflow file to make sure no code from the incoming PR is executed. Please see https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ for additional mitigations. /.github/workflows/disabled/notify-models.yaml:98 99%
24. high GuardDog Detects download-and-execute patterns: fetching a remote file then executing it [threat-process-download-exec] /backend/python/moonshine/test.py:24 95%
25. high GuardDog Detects download-and-execute patterns: fetching a remote file then executing it [threat-process-download-exec] /backend/python/nemo/test.py:62 95%
26. high GuardDog Detects download-and-execute patterns: fetching a remote file then executing it [threat-process-download-exec] /backend/python/moonshine/test.py:79 95%
27. high GuardDog Detects base64 decoding followed by code execution [threat-runtime-obfuscation-base64exec] /core/http/static/assets/pdf.min.js:22 91%
28. high Semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR". /.github/workflows/disabled/test-gpu.yml:51 57%
29. high Semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR". /.github/workflows/backend_build_darwin.yml:260 57%
30. high Semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR". /.github/workflows/backend_build_darwin.yml:343 57%
31. high Semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR". /.github/workflows/backend_build_darwin.yml:349 57%
32. high Semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR". /.github/workflows/disabled/test-gpu.yml:39 57%
33. high Semgrep Functions reliant on pickle can result in arbitrary code execution. Consider loading from `state_dict`, using fickling, or switching to a safer serialization method like ONNX /backend/python/vibevoice/backend.py:470 51%
34. high Semgrep Insecure WebSocket Detected. WebSocket Secure (wss) should be used for all WebSocket connections. /core/http/endpoints/localai/nodes.go:831 51%
35. high Semgrep Insecure WebSocket Detected. WebSocket Secure (wss) should be used for all WebSocket connections. /core/http/endpoints/openresponses/websocket.go:68 51%
36. high Semgrep Insecure WebSocket Detected. WebSocket Secure (wss) should be used for all WebSocket connections. /core/http/static/assets/htmx.js:1 51%
37. high Semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /backend/go/vllm-cpp/video.go:364 47%
38. high Semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /backend/go/vllm-cpp/video.go:536 47%
39. high Semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /cmd/launcher/internal/launcher.go:256 46%
40. high Semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /cmd/launcher/internal/release_manager.go:524 46%
41. high Semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /core/cli/chat/server.go:115 46%
42. high Semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /core/cli/worker/worker_mlx_common.go:21 46%
43. high Semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /core/cli/worker/worker_p2p.go:90 46%
44. high Semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /core/cli/worker/worker_vllm.go:120 46%
45. high Semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /core/http/endpoints/mcp/tools.go:246 46%
46. high Semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /core/http/endpoints/mcp/tools.go:364 46%
47. high Semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. /core/services/agents/mcp.go:40 46%
48. high Bandit By default, jinja2 sets autoescape to False. Consider using autoescape=True or use the select_autoescape function to mitigate XSS vulnerabilities. /backend/python/tinygrad/backend.py:246 42%
49. high Semgrep By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'. /Dockerfile:441 22%
50. high YARA YARA rule matched: detect_base64_exec — Encoded payload decoded and then executed /core/http/static/assets/pdf.min.js 3%
51. high YARA YARA rule matched: detect_base64_exec — Encoded payload decoded and then executed /core/http/static/assets/tailwindcss.js 3%
52. high YARA YARA rule matched: detect_base64_exec — Encoded payload decoded and then executed /core/http/static/assets/pdf.worker.min.js 3%
53. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /core/http/static/assets/highlightjs.js 1%
54. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /backend/python/common/libbackend.sh 1%
55. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /backend/Dockerfile.python 1%
56. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /Makefile 1%
57. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /website/static/js/site.js 1%
58. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /website/static/install.sh 1%
59. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /.github/workflows/test-extra.yml 1%
60. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /website/layouts/index.html 1%
61. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /.github/workflows/lint.yml 1%
62. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /scripts/latest_hf.py 1%
63. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /backend/Dockerfile.rust 1%
64. high YARA YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone /backend/Dockerfile.golang 1%
65. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/http/static/assets/pdf.worker.min.js 1%
66. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/http/static/assets/js-yaml.min.js 1%
67. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/http/static/assets/marked.js 1%
68. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/http/static/assets/codemirror.min.js 1%
69. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/http/static/assets/pdf.min.js 1%
70. high YARA YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together /core/http/static/assets/tailwindcss.js 1%
71. medium Semgrep RegExp() called with a `s` 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 use hardcoded regexes instead. If your regex is run on user-controlled input, consider performing input validation or use a regex checking/sanitization library such as https://www.npmjs.com/package/recheck to verify that the regex does not appear vulnerable to ReDoS. /core/http/static/assets/tw-elements.js:17 100%
72. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/voxcpm/backend.py:206 100%
73. medium Semgrep Variable `r` is likely modified and later used on error. In some cases this could result in panics due to a nil dereference /core/http/endpoints/openai/realtime_voicegate.go:254 100%
74. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/vllm-omni/backend.py:738 100%
75. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/transformers/backend.py:624 100%
76. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/transformers/backend.py:549 100%
77. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/qwen-tts/backend.py:930 100%
78. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/neutts/backend.py:135 100%
79. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/kokoro/backend.py:78 100%
80. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/kitten-tts/backend.py:72 100%
81. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/fish-speech/backend.py:440 100%
82. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/faster-qwen3-tts/backend.py:156 100%
83. medium Semgrep Iteration over a possibly empty map `neededDefs`. This is likely a bug or redundant code /core/http/endpoints/localai/api_instructions.go:199 100%
84. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/liquid-audio/backend.py:346 99%
85. medium Semgrep Found user-controlled request data passed into '.write(...)'. This could be dangerous if a malicious actor is able to control data into sensitive files. For example, a malicious actor could force rolling of critical log files, or cause a denial-of-service by using up available disk space. Instead, ensure that request data is properly escaped or sanitized. /backend/python/pocket-tts/backend.py:206 99%
86. medium Semgrep Iteration over a possibly empty map `neededDefs`. This is likely a bug or redundant code /core/http/endpoints/localai/api_instructions.go:199 99%
87. medium Semgrep Iteration over a possibly empty map `votes`. This is likely a bug or redundant code /core/services/routing/router/knn.go:129 99%
88. medium Semgrep `e.item.replace("[","").replace` method will only replace the first occurrence when used with a string argument ("]"). If this method is used for escaping of dangerous data then there is a possibility for a bypass. Try to use sanitization library instead or use a Regex with a global flag. /core/http/static/assets/alpine.js:5 99%
89. medium Semgrep `e.item.replace` method will only replace the first occurrence when used with a string argument ("{"). If this method is used for escaping of dangerous data then there is a possibility for a bypass. Try to use sanitization library instead or use a Regex with a global flag. /core/http/static/assets/alpine.js:5 99%
90. medium Semgrep `e.item.replace("{","").replace` method will only replace the first occurrence when used with a string argument ("}"). If this method is used for escaping of dangerous data then there is a possibility for a bypass. Try to use sanitization library instead or use a Regex with a global flag. /core/http/static/assets/alpine.js:5 99%
91. medium Semgrep `e.item.replace` method will only replace the first occurrence when used with a string argument ("["). If this method is used for escaping of dangerous data then there is a possibility for a bypass. Try to use sanitization library instead or use a Regex with a global flag. /core/http/static/assets/alpine.js:5 99%
92. medium Semgrep This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown /.github/dependabot.yml:58 99%
93. medium Semgrep This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown /.github/dependabot.yml:62 99%
94. medium Semgrep This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown /.github/dependabot.yml:54 99%
95. medium Semgrep This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown /.github/dependabot.yml:36 99%
96. medium Semgrep This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown /.github/dependabot.yml:32 99%
97. medium Semgrep This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown /.github/dependabot.yml:26 99%
98. medium Semgrep This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown /.github/dependabot.yml:20 99%
99. medium Semgrep This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown /.github/dependabot.yml:14 99%
100. medium Semgrep This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown /.github/dependabot.yml:8 99%
101. medium Semgrep This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown /.github/dependabot.yml:4 99%
102. medium Semgrep This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown /.github/dependabot.yml:40 99%
103. medium GuardDog Detects access to sensitive files (credentials, configs, keys) [threat-filesystem-read] /cmd/local-ai/main.go:30 96%
104. medium GuardDog Detects access to sensitive files (credentials, configs, keys) [threat-filesystem-read] /cmd/local-ai/main.go:28 96%
105. medium GuardDog Detects access to sensitive files (credentials, configs, keys) [threat-filesystem-read] /cmd/local-ai/main.go:25 96%
106. medium Semgrep Semgrep could not determine that the argument to 'template.HTML()' is a constant. 'template.HTML()' and similar does not escape contents. Be absolutely sure there is no user-controlled data in this template. If user data can reach this template, you may have a XSS vulnerability. Instead, do not use this function and use 'template.Execute()'. /core/http/render.go:88 82%
107. medium Semgrep Downcasting or changing sign of an integer with `int32` method /backend/go/localvqe/golocalvqe.go:123 82%
108. medium Semgrep Downcasting or changing sign of an integer with `int32` method /backend/go/trellis2cpp/trellis2.go:252 82%
109. medium Semgrep Downcasting or changing sign of an integer with `int32` method /backend/go/sherpa-onnx/backend.go:1308 81%
110. medium Semgrep Downcasting or changing sign of an integer with `int32` method /backend/go/sherpa-onnx/backend.go:1408 81%
111. medium Semgrep The Origin header in the HTTP WebSocket handshake is used to guarantee that the connection accepted by the WebSocket is from a trusted origin domain. Failure to enforce can lead to Cross Site Request Forgery (CSRF). As per "gorilla/websocket" documentation: "A CheckOrigin function should carefully validate the request origin to prevent cross-site request forgery." /core/services/nodes/file_transfer_server.go:1197 77%
112. medium Semgrep A session cookie was detected without setting the 'Secure' flag. The 'secure' flag for cookies prevents the client from transmitting the cookie over insecure channels such as HTTP. Set the 'Secure' flag by setting 'Secure' to 'true' in the Options struct. /core/http/auth/session.go:172 53%
113. medium Semgrep A session cookie was detected without setting the 'Secure' flag. The 'secure' flag for cookies prevents the client from transmitting the cookie over insecure channels such as HTTP. Set the 'Secure' flag by setting 'Secure' to 'true' in the Options struct. /core/http/auth/session.go:158 53%
114. medium Semgrep A session cookie was detected without setting the 'Secure' flag. The 'secure' flag for cookies prevents the client from transmitting the cookie over insecure channels such as HTTP. Set the 'Secure' flag by setting 'Secure' to 'true' in the Options struct. /core/http/auth/session.go:144 53%
115. medium Semgrep A session cookie was detected without setting the 'Secure' flag. The 'secure' flag for cookies prevents the client from transmitting the cookie over insecure channels such as HTTP. Set the 'Secure' flag by setting 'Secure' to 'true' in the Options struct. /core/http/auth/oauth.go:197 53%
116. medium Semgrep A session cookie was detected without setting the 'Secure' flag. The 'secure' flag for cookies prevents the client from transmitting the cookie over insecure channels such as HTTP. Set the 'Secure' flag by setting 'Secure' to 'true' in the Options struct. /core/http/auth/oauth.go:165 53%
117. medium Semgrep A session cookie was detected without setting the 'Secure' flag. The 'secure' flag for cookies prevents the client from transmitting the cookie over insecure channels such as HTTP. Set the 'Secure' flag by setting 'Secure' to 'true' in the Options struct. /core/http/auth/oauth.go:242 53%
118. medium Semgrep A session cookie was detected without setting the 'Secure' flag. The 'secure' flag for cookies prevents the client from transmitting the cookie over insecure channels such as HTTP. Set the 'Secure' flag by setting 'Secure' to 'true' in the Options struct. /core/http/auth/oauth.go:153 53%
119. medium Semgrep Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. /pkg/modelartifacts/materializer.go:598 53%
120. medium Semgrep Detected MD5 hash algorithm which is considered insecure. MD5 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. /pkg/utils/hash.go:9 53%
121. medium Semgrep `MinVersion` is missing from this TLS configuration. By default, as of Go 1.22, TLS 1.2 is currently used as the minimum. General purpose web applications should default to TLS 1.3 with all other protocols disabled. Only where it is known that a web server must support legacy clients with unsupported an insecure browsers (such as Internet Explorer 10), it may be necessary to enable TLS 1.0 to provide support. Add `MinVersion: tls.VersionTLS13' to the TLS configuration to bump the minimum version to TLS 1.3. /core/services/cloudproxy/mitm/proxy.go:242 53%
122. medium Semgrep Detected a dynamic value being used with urllib. urllib supports 'file://' schemes, so a dynamic value controlled by a malicious actor may allow them to read arbitrary files. Audit uses of urllib calls to ensure user data cannot control the URLs, or consider using the 'requests' library instead. /backend/python/insightface/smoke.py:151 52%
123. medium Semgrep Detected a dynamic value being used with urllib. urllib supports 'file://' schemes, so a dynamic value controlled by a malicious actor may allow them to read arbitrary files. Audit uses of urllib calls to ensure user data cannot control the URLs, or consider using the 'requests' library instead. /backend/python/insightface/test.py:74 52%
124. medium Semgrep `MinVersion` is missing from this TLS configuration. By default, as of Go 1.22, TLS 1.2 is currently used as the minimum. General purpose web applications should default to TLS 1.3 with all other protocols disabled. Only where it is known that a web server must support legacy clients with unsupported an insecure browsers (such as Internet Explorer 10), it may be necessary to enable TLS 1.0 to provide support. Add `MinVersion: tls.VersionTLS13' to the TLS configuration to bump the minimum version to TLS 1.3. /core/services/cloudproxy/mitm/handler.go:55 52%
125. medium Semgrep `MinVersion` is missing from this TLS configuration. By default, as of Go 1.22, TLS 1.2 is currently used as the minimum. General purpose web applications should default to TLS 1.3 with all other protocols disabled. Only where it is known that a web server must support legacy clients with unsupported an insecure browsers (such as Internet Explorer 10), it may be necessary to enable TLS 1.0 to provide support. Add `MinVersion: tls.VersionTLS13' to the TLS configuration to bump the minimum version to TLS 1.3. /core/services/cloudproxy/mitm/proxy.go:78 52%
126. medium Semgrep `MinVersion` is missing from this TLS configuration. By default, as of Go 1.22, TLS 1.2 is currently used as the minimum. General purpose web applications should default to TLS 1.3 with all other protocols disabled. Only where it is known that a web server must support legacy clients with unsupported an insecure browsers (such as Internet Explorer 10), it may be necessary to enable TLS 1.0 to provide support. Add `MinVersion: tls.VersionTLS13' to the TLS configuration to bump the minimum version to TLS 1.3. /backend/go/valkey-store/store.go:293 52%
127. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump_deps.yaml:256 52%
128. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump_deps.yaml:237 52%
129. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump_deps.yaml:218 52%
130. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump_deps.yaml:200 52%
131. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump_deps.yaml:183 52%
132. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump_deps.yaml:167 52%
133. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump_deps.yaml:143 52%
134. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump-inference-defaults.yml:37 52%
135. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump-inference-defaults.yml:19 52%
136. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump-inference-defaults.yml:17 52%
137. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build-test.yaml:97 52%
138. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build-test.yaml:88 52%
139. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build-test.yaml:82 52%
140. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build-test.yaml:72 52%
141. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build-test.yaml:64 52%
142. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build-test.yaml:60 52%
143. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build-test.yaml:44 52%
144. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/labeler.yml:12 52%
145. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/build-test.yaml:40 52%
146. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/deploy-explorer.yaml:22 52%
147. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/dependabot_auto.yml:23 52%
148. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/dependabot_auto.yml:17 52%
149. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/comment-pr.yaml:77 52%
150. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/comment-pr.yaml:20 52%
151. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/comment-pr.yaml:16 52%
152. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/comment-pr.yaml:12 52%
153. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/deploy-explorer.yaml:57 52%
154. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/deploy-explorer.yaml:46 52%
155. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/deploy-explorer.yaml:37 52%
156. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump_deps.yaml:275 52%
157. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/deploy-explorer.yaml:19 52%
158. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/ci-tools-tests.yaml:22 52%
159. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/ci-tools-tests.yaml:21 52%
160. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/checksum_checker.yaml:33 52%
161. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/checksum_checker.yaml:20 52%
162. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/checksum_checker.yaml:11 52%
163. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump_docs.yaml:25 52%
164. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/bump_docs.yaml:16 52%
165. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build.yml:169 52%
166. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:214 52%
167. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:181 52%
168. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:145 52%
169. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:85 52%
170. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:65 52%
171. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:60 52%
172. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build.yml:258 52%
173. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build.yml:250 52%
174. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build.yml:186 52%
175. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:270 52%
176. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build.yml:162 52%
177. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build.yml:158 52%
178. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build.yml:152 52%
179. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build.yml:139 52%
180. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build.yml:123 52%
181. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build.yml:104 52%
182. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend.yml:64 52%
183. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend.yml:61 52%
184. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/actions/free-disk-space/action.yml:21 52%
185. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_merge.yml:79 52%
186. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/base-images.yml:141 52%
187. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/base-images.yml:140 52%
188. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/base-images.yml:137 52%
189. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/base-images.yml:130 52%
190. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_pr.yml:43 52%
191. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_pr.yml:40 52%
192. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_merge.yml:101 52%
193. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_merge.yml:92 52%
194. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_merge.yml:85 52%
195. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/base-images.yml:146 52%
196. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_merge.yml:70 52%
197. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_merge.yml:63 52%
198. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_merge.yml:52 52%
199. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:330 52%
200. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:316 52%
201. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:296 52%
202. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:285 52%
203. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/backend_build_darwin.yml:277 52%
204. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/notify-models.yaml:18 52%
205. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/gh-pages.yml:46 52%
206. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/generate_intel_image.yaml:50 52%
207. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/generate_intel_image.yaml:44 52%
208. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/localaibot_automerge.yml:17 52%
209. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/notify-models.yaml:22 52%
210. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/notify-models.yaml:26 52%
211. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/notify-models.yaml:82 52%
212. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/notify-models.yaml:87 52%
213. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/notify-models.yaml:98 52%
214. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/notify-models.yaml:108 52%
215. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/notify-models.yaml:159 52%
216. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/notify-models.yaml:170 52%
217. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/prlint.yaml:17 52%
218. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/test-gpu.yml:24 52%
219. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/gallery-agent.yaml:34 52%
220. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/disabled/test-gpu.yml:28 52%
221. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/generate_intel_image.yaml:47 52%
222. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/generate_intel_image.yaml:37 52%
223. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/generate_intel_image.yaml:30 52%
224. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/generate_intel_image.yaml:25 52%
225. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/gallery_variant_proposals.yaml:46 52%
226. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/gallery_variant_proposals.yaml:12 52%
227. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/gallery_variant_proposals.yaml:11 52%
228. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/gallery-agent.yaml:174 52%
229. medium Semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`. /.github/workflows/gallery-agent.yaml:39 52%
230. medium Bandit Use of unsafe PyTorch load /backend/python/vibevoice/backend.py:470 49%
231. medium Bandit Audit url open for permitted schemes. Allowing use of file:/ or custom schemes is often unexpected. /backend/python/insightface/smoke.py:151 49%
232. medium Bandit Audit url open for permitted schemes. Allowing use of file:/ or custom schemes is often unexpected. /backend/python/insightface/test.py:74 48%
233. medium Bandit Use of exec detected. /backend/python/trl/reward_functions.py:173 40%
234. medium Bandit Pickle and modules that wrap it can be unsafe when used to deserialize untrusted data, possible security issue. /backend/python/qwen-tts/backend.py:568 38%
235. medium Bandit Probable insecure usage of temp file/directory. /backend/python/speaker-recognition/test.py:55 25%
236. medium Bandit Probable insecure usage of temp file/directory. /backend/python/vllm-omni/test.py:67 25%
237. medium Bandit Probable insecure usage of temp file/directory. /backend/python/speaker-recognition/test.py:55 25%
238. medium Bandit Probable insecure usage of temp file/directory. /backend/python/mlx-video/test.py:81 25%
239. medium Bandit Probable insecure usage of temp file/directory. /backend/python/mlx-video/test.py:80 25%
240. medium Bandit Probable insecure usage of temp file/directory. /backend/python/mlx-video/test.py:59 25%
241. medium Bandit Probable insecure usage of temp file/directory. /backend/python/mlx-video/test.py:35 25%
242. medium Bandit Probable insecure usage of temp file/directory. /backend/python/mlx-video/test.py:33 25%
243. medium Bandit Probable insecure usage of temp file/directory. /backend/python/liquid-audio/backend.py:659 25%
244. medium Bandit Probable insecure usage of temp file/directory. /backend/python/funasr/test.py:285 25%
245. medium Bandit Probable insecure usage of temp file/directory. /backend/python/mlx-video/test.py:36 25%
246. medium Bandit Probable insecure usage of temp file/directory. /backend/python/fish-speech/test.py:17 25%
247. medium Bandit Call to requests without timeout /.github/check_and_update.py:68 22%
248. medium Bandit Call to requests without timeout /scripts/latest_hf.py:19 22%
249. medium Bandit Call to requests without timeout /.github/check_and_update.py:30 22%
250. medium Bandit Unsafe Hugging Face Hub download without revision pinning in hf_hub_download() /backend/python/trl/backend.py:782 19%
251. medium Bandit Unsafe Hugging Face Hub download without revision pinning in load_dataset() /backend/python/trl/backend.py:346 19%
252. medium Bandit Unsafe Hugging Face Hub download without revision pinning in load_dataset() /backend/python/trl/backend.py:343 19%
253. medium Bandit Unsafe Hugging Face Hub download without revision pinning in load_dataset() /backend/python/trl/backend.py:341 19%
254. medium Bandit Unsafe Hugging Face Hub download without revision pinning in load_dataset() /backend/python/trl/backend.py:339 19%
255. medium Bandit Unsafe Hugging Face Hub download without revision pinning in load_dataset() /backend/python/trl/backend.py:337 19%
256. medium Bandit Unsafe Hugging Face Hub download without revision pinning in load_dataset() /backend/python/trl/backend.py:323 19%
257. medium Bandit Unsafe Hugging Face Hub download without revision pinning in load_dataset() /backend/python/trl/backend.py:321 19%
258. medium Bandit Unsafe Hugging Face Hub download without revision pinning in load_dataset() /backend/python/trl/backend.py:317 19%
259. medium Bandit Unsafe Hugging Face Hub download without revision pinning in hf_hub_download() /backend/python/tinygrad/backend.py:396 19%
260. medium Bandit Unsafe Hugging Face Hub download without revision pinning in snapshot_download() /backend/python/tinygrad/backend.py:89 19%
261. medium Bandit Unsafe Hugging Face Hub download without revision pinning in snapshot_download() /backend/python/llama-cpp-quantization/backend.py:178 19%
262. medium Bandit Unsafe Hugging Face Hub download without revision pinning in snapshot_download() /backend/python/fish-speech/backend.py:183 19%
263. medium Bandit Unsafe Hugging Face Hub download without revision pinning in hf_hub_download() /.github/check_and_update.py:63 19%
264. medium Bandit Unsafe Hugging Face Hub download without revision pinning in load_dataset() /backend/python/trl/backend.py:319 19%
265. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/trl/backend.py:758 17%
266. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/whisper-medusa/backend.py:85 17%
267. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/trl/backend.py:770 17%
268. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/trl/backend.py:753 17%
269. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/trl/backend.py:735 17%
270. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/trl/backend.py:730 17%
271. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/trl/backend.py:280 17%
272. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/trl/backend.py:279 17%
273. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/transformers/backend.py:262 17%
274. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/transformers/backend.py:244 17%
275. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/transformers/backend.py:145 17%
276. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/speaker-recognition/engines.py:112 17%
277. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/speaker-recognition/engines.py:111 17%
278. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/sglang/backend.py:261 17%
279. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/diffusers/backend.py:276 17%
280. medium Bandit Unsafe Hugging Face Hub download without revision pinning in from_pretrained() /backend/python/transformers/backend.py:497 17%
281. low Bandit Possible hardcoded password: '</think>' /backend/python/vllm/test.py:566 95%
282. low Bandit Possible hardcoded password: '<think>' /backend/python/vllm/test.py:565 95%
283. low Bandit Possible hardcoded password: '' /scripts/model_gallery_info.py:57 45%
284. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/trl/backend.py:740 14%
285. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/llama-cpp-quantization/test.py:9 13%
286. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/mlx/test.py:4 13%
287. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/chatterbox/test.py:5 13%
288. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/coqui/test.py:5 13%
289. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/diffusers/test.py:5 13%
290. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/faster-qwen3-tts/test.py:5 13%
291. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/fish-speech/test.py:7 13%
292. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/kitten-tts/test.py:5 13%
293. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/kokoro/test.py:5 13%
294. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/liquid-audio/test.py:10 13%
295. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/llama-cpp-quantization/backend.py:13 13%
296. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/longcat-video/backend.py:11 13%
297. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/mlx-audio/test.py:2 13%
298. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/mlx-distributed/test.py:5 13%
299. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/mlx-video/backend.py:8 13%
300. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/mlx-vlm/test.py:5 13%
301. low Bandit Consider possible security implications associated with the subprocess module. /scripts/latest_hf.py:7 13%
302. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/whisperx/test.py:5 13%
303. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/voxcpm/test.py:5 13%
304. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/vllm/test.py:2 13%
305. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/vllm-omni/test.py:2 13%
306. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/vibevoice/test.py:5 13%
307. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/trl/test.py:5 13%
308. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/transformers/test.py:5 13%
309. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/tinygrad/test.py:13 13%
310. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/qwen-tts/test.py:5 13%
311. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/qwen-asr/test.py:5 13%
312. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/pocket-tts/test.py:5 13%
313. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/outetts/test.py:5 13%
314. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/neutts/test.py:5 13%
315. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/nemo/test.py:5 13%
316. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/moonshine/test.py:5 13%
317. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/rerankers/test.py:5 13%
318. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/mlx-audio/test.py:10 12%
319. low Bandit Consider possible security implications associated with the subprocess module. /backend/python/vllm/test.py:10 12%
320. low Bandit Starting a process with a partial executable path /backend/python/nemo/test.py:62 12%
321. low Bandit Starting a process with a partial executable path /backend/python/neutts/test.py:21 12%
322. low Bandit Starting a process with a partial executable path /backend/python/outetts/test.py:15 12%
323. low Bandit Starting a process with a partial executable path /backend/python/pocket-tts/test.py:23 12%
324. low Bandit Starting a process with a partial executable path /backend/python/qwen-asr/test.py:21 12%
325. low Bandit Starting a process with a partial executable path /backend/python/qwen-asr/test.py:61 12%
326. low Bandit Starting a process with a partial executable path /backend/python/qwen-tts/test.py:25 12%
327. low Bandit Starting a process with a partial executable path /backend/python/rerankers/test.py:21 12%
328. low Bandit Starting a process with a partial executable path /backend/python/tinygrad/test.py:30 12%
329. low Bandit Starting a process with a partial executable path /backend/python/transformers/test.py:21 12%
330. low Bandit Starting a process with a partial executable path /backend/python/trl/test.py:17 12%
331. low Bandit Starting a process with a partial executable path /backend/python/vibevoice/test.py:28 12%
332. low Bandit Starting a process with a partial executable path /backend/python/vibevoice/test.py:150 12%
333. low Bandit Starting a process with a partial executable path /backend/python/vllm-omni/test.py:16 12%
334. low Bandit Starting a process with a partial executable path /backend/python/voxcpm/test.py:21 12%
335. low Bandit Starting a process with a partial executable path /backend/python/vllm/test.py:23 12%
336. low Bandit Starting a process with a partial executable path /backend/python/nemo/test.py:21 12%
337. low Bandit Starting a process with a partial executable path /backend/python/moonshine/test.py:79 12%
338. low Bandit Starting a process with a partial executable path /backend/python/moonshine/test.py:24 12%
339. low Bandit Starting a process with a partial executable path /backend/python/mlx/test.py:25 12%
340. low Bandit Starting a process with a partial executable path /backend/python/mlx-vlm/test.py:25 12%
341. low Bandit Starting a process with a partial executable path /backend/python/mlx-distributed/test.py:21 12%
342. low Bandit Starting a process with a partial executable path /backend/python/mlx-audio/test.py:23 12%
343. low Bandit Starting a process with a partial executable path /backend/python/llama-cpp-quantization/test.py:29 12%
344. low Bandit Starting a process with a partial executable path /backend/python/kokoro/test.py:21 12%
345. low Bandit Starting a process with a partial executable path /backend/python/kitten-tts/test.py:21 12%
346. low Bandit Starting a process with a partial executable path /backend/python/fish-speech/test.py:67 12%
347. low Bandit Starting a process with a partial executable path /backend/python/faster-qwen3-tts/test.py:17 12%
348. low Bandit Starting a process with a partial executable path /backend/python/diffusers/test.py:36 12%
349. low Bandit Starting a process with a partial executable path /backend/python/coqui/test.py:21 12%
350. low Bandit Starting a process with a partial executable path /backend/python/chatterbox/test.py:21 12%
351. low Bandit Starting a process with a partial executable path /backend/python/whisperx/test.py:24 12%
352. low Bandit Starting a process with a partial executable path /backend/python/whisperx/test.py:79 12%
353. low Bandit Starting a process with a partial executable path /scripts/latest_hf.py:26 12%
354. low Bandit subprocess call - check for execution of untrusted input. /backend/python/whisperx/test.py:24 3%
355. low Bandit subprocess call - check for execution of untrusted input. /backend/python/mlx-vlm/test.py:25 3%
356. low Bandit subprocess call - check for execution of untrusted input. /backend/python/voxcpm/test.py:21 3%
357. low Bandit subprocess call - check for execution of untrusted input. /backend/python/vllm/test.py:23 3%
358. low Bandit subprocess call - check for execution of untrusted input. /backend/python/vllm-omni/test.py:16 3%
359. low Bandit subprocess call - check for execution of untrusted input. /backend/python/vibevoice/test.py:150 3%
360. low Bandit subprocess call - check for execution of untrusted input. /backend/python/vibevoice/test.py:28 3%
361. low Bandit subprocess call - check for execution of untrusted input. /backend/python/trl/test.py:17 3%
362. low Bandit subprocess call - check for execution of untrusted input. /backend/python/trl/backend.py:819 3%
363. low Bandit subprocess call - check for execution of untrusted input. /backend/python/transformers/test.py:21 3%
364. low Bandit subprocess call - check for execution of untrusted input. /backend/python/tinygrad/test.py:30 3%
365. low Bandit subprocess call - check for execution of untrusted input. /backend/python/rerankers/test.py:21 3%
366. low Bandit subprocess call - check for execution of untrusted input. /backend/python/qwen-tts/test.py:25 3%
367. low Bandit subprocess call - check for execution of untrusted input. /backend/python/qwen-asr/test.py:61 3%
368. low Bandit subprocess call - check for execution of untrusted input. /backend/python/qwen-asr/test.py:21 3%
369. low Bandit subprocess call - check for execution of untrusted input. /backend/python/pocket-tts/test.py:23 3%
370. low Bandit subprocess call - check for execution of untrusted input. /backend/python/outetts/test.py:15 3%
371. low Bandit subprocess call - check for execution of untrusted input. /backend/python/neutts/test.py:21 3%
372. low Bandit subprocess call - check for execution of untrusted input. /backend/python/nemo/test.py:62 3%
373. low Bandit subprocess call - check for execution of untrusted input. /backend/python/nemo/test.py:21 3%
374. low Bandit subprocess call - check for execution of untrusted input. /backend/python/moonshine/test.py:79 3%
375. low Bandit subprocess call - check for execution of untrusted input. /backend/python/moonshine/test.py:24 3%
376. low Bandit subprocess call - check for execution of untrusted input. /backend/python/mlx/test.py:25 3%
377. low Bandit subprocess call - check for execution of untrusted input. /backend/python/mlx-video/backend.py:111 3%
378. low Bandit subprocess call - check for execution of untrusted input. /backend/python/longcat-video/backend.py:873 3%
379. low Bandit subprocess call - check for execution of untrusted input. /backend/python/chatterbox/test.py:21 3%
380. low Bandit subprocess call - check for execution of untrusted input. /backend/python/coqui/test.py:21 3%
381. low Bandit subprocess call - check for execution of untrusted input. /backend/python/diffusers/test.py:36 3%
382. low Bandit subprocess call - check for execution of untrusted input. /backend/python/faster-qwen3-tts/test.py:17 3%
383. low Bandit subprocess call - check for execution of untrusted input. /backend/python/fish-speech/test.py:67 3%
384. low Bandit subprocess call - check for execution of untrusted input. /backend/python/kitten-tts/test.py:21 3%
385. low Bandit subprocess call - check for execution of untrusted input. /backend/python/kokoro/test.py:21 3%
386. low Bandit subprocess call - check for execution of untrusted input. /backend/python/liquid-audio/test.py:29 3%
387. low Bandit subprocess call - check for execution of untrusted input. /backend/python/llama-cpp-quantization/backend.py:226 3%
388. low Bandit subprocess call - check for execution of untrusted input. /backend/python/llama-cpp-quantization/backend.py:269 3%
389. low Bandit subprocess call - check for execution of untrusted input. /backend/python/llama-cpp-quantization/test.py:29 3%
390. low Bandit subprocess call - check for execution of untrusted input. /backend/python/whisperx/test.py:79 3%
391. low Bandit subprocess call - check for execution of untrusted input. /backend/python/mlx-audio/test.py:23 3%
392. low Bandit subprocess call - check for execution of untrusted input. /backend/python/mlx-distributed/test.py:21 3%
393. low Bandit subprocess call - check for execution of untrusted input. /scripts/latest_hf.py:26 3%
394. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /.docker/install-base-deps.sh 0%
395. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /website/static/install.sh 0%
396. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /.github/workflows/deploy-explorer.yaml 0%
397. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /.github/check_and_update.py 0%
398. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /CONTRIBUTING.md 0%
399. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /Dockerfile 0%
400. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /scripts/latest_hf.py 0%
401. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /backend/Dockerfile.rust 0%
402. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /backend/Dockerfile.golang 0%
403. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /backend/Dockerfile.python 0%
404. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /backend/python/faster-whisper/install.sh 0%
405. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /backend/python/vibevoice/Makefile 0%
406. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /backend/python/insightface/test.py 0%
407. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /backend/python/insightface/smoke.py 0%
408. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /backend/python/common/libbackend.sh 0%
409. low YARA YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version /core/http/static/assets/highlightjs.js 0%
410. low Bandit Use of assert detected. The enclosed code will be removed when compiling to optimised byte code. /backend/python/tinygrad/vendor/unet.py:242 0%
411. low Bandit Use of assert detected. The enclosed code will be removed when compiling to optimised byte code. /backend/python/tinygrad/vendor/unet.py:161 0%
412. low Bandit Use of assert detected. The enclosed code will be removed when compiling to optimised byte code. /backend/python/tinygrad/vendor/unet.py:158 0%
413. low Bandit Use of assert detected. The enclosed code will be removed when compiling to optimised byte code. /backend/python/tinygrad/vendor/unet.py:111 0%
414. low Bandit Use of assert detected. The enclosed code will be removed when compiling to optimised byte code. /backend/python/tinygrad/vendor/unet.py:109 0%
415. low Bandit Use of assert detected. The enclosed code will be removed when compiling to optimised byte code. /backend/python/tinygrad/vendor/clip.py:405 0%
416. low Bandit Use of assert detected. The enclosed code will be removed when compiling to optimised byte code. /backend/python/tinygrad/vendor/clip.py:345 0%
417. low Bandit Use of assert detected. The enclosed code will be removed when compiling to optimised byte code. /backend/python/tinygrad/vendor/clip.py:248 0%