Leaderboard github.com

Jackett/Jackett

API Support for your favorite torrent trackers

View repository ↗
C#
★ 16,372
commit 95d94bdefc0f
scored 2026-11-14
scoring prov-5+qual-2+sec-2

AI provenance

explicit

Confidence: 95%
Coverage: 100%

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

Code quality

63/100

weak

Confidence: 90%
Coverage: 100%

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

Security

59/100

weak

Confidence: 85%
Coverage: 100%

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

Dispute or request a re-score Full report JSON

AI provenance

0% explicit

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

How the score is built

Explicitly attributed share0%
Unattributed share in AI-pace bursts1%
Estimated AI-generated share0%
AI tool configuration files0
Work sessions at AI pace1
Releases at AI pace0
Coding-style index (1.0+ means possible)0.02

Attributed AI tools

Tool	Commits	Lines added	First seen	Last seen
GitHub Copilot coding agent	1	0	2026-04-15	2026-04-15
Claude Code	2	0	2026-05-31	2026-09-30

Lines added per month all AI-attributed share

2015-0417,728 · 0% AI
2015-051,540 · 0% AI
2015-061,569 · 0% AI
2015-0731,144 · 0% AI
2015-0811,259 · 0% AI
2015-093,900 · 0% AI
2015-101,232 · 0% AI
2015-111,390 · 0% AI
2015-122,940 · 0% AI
2016-013,953 · 0% AI
2016-02337 · 0% AI
2016-031,530 · 0% AI
2016-042,043 · 0% AI
2016-05445 · 0% AI
2016-06202 · 0% AI
2016-07151 · 0% AI
2016-08781 · 0% AI
2016-093,079 · 0% AI
2016-102,494 · 0% AI
2016-111,705 · 0% AI
2016-123,249 · 0% AI
2017-016,375 · 0% AI
2017-022,433 · 0% AI
2017-031,019 · 0% AI
2017-0420,047 · 0% AI
2017-05877 · 0% AI
2017-062,001 · 0% AI
2017-072,255 · 0% AI
2017-085,444 · 0% AI
2017-09718 · 0% AI
2017-104,380 · 0% AI
2017-112,381 · 0% AI
2017-12309 · 0% AI
2018-01583 · 0% AI
2018-02409 · 0% AI
2018-031,245 · 0% AI
2018-04835 · 0% AI
2018-053,757 · 0% AI
2018-062,952 · 0% AI
2018-071,034 · 0% AI
2018-081,433 · 0% AI
2018-09469 · 0% AI
2018-10485 · 0% AI
2018-11478 · 0% AI
2018-12487 · 0% AI
2019-01760 · 0% AI
2019-02798 · 0% AI
2019-03729 · 0% AI
2019-04594 · 0% AI
2019-05227 · 0% AI
2019-061,096 · 0% AI
2019-0722 · 0% AI
2019-08356 · 0% AI
2019-09670 · 0% AI
2019-10369 · 0% AI
2019-1182 · 0% AI
2019-12818 · 0% AI
2020-011,930 · 0% AI
2020-025,497 · 0% AI
2020-035,346 · 0% AI
2020-045,989 · 0% AI
2020-052,451 · 0% AI
2020-062,177 · 0% AI
2020-07116 · 0% AI
2020-08262 · 0% AI
2020-093,491 · 0% AI
2020-106,203 · 0% AI
2020-112,789 · 0% AI
2020-121,517 · 0% AI
2021-01391 · 0% AI
2021-02481 · 0% AI
2021-031,880 · 0% AI
2021-041,017 · 0% AI
2021-052,890 · 0% AI
2021-06746 · 0% AI
2021-07357 · 0% AI
2021-08101 · 0% AI
2021-09676 · 0% AI
2021-10775 · 0% AI
2021-11564 · 0% AI
2021-1297 · 0% AI
2022-011,282 · 0% AI
2022-02543 · 0% AI
2022-03102 · 0% AI
2022-04377 · 0% AI
2022-05363 · 0% AI
2022-061,136 · 0% AI
2022-07536 · 0% AI
2022-08490 · 0% AI
2022-09497 · 0% AI
2022-10487 · 0% AI
2022-1184 · 0% AI
2022-1247 · 0% AI
2023-012,089 · 0% AI
2023-022,566 · 0% AI
2023-036,743 · 0% AI
2023-041,117 · 0% AI
2023-05393 · 0% AI
2023-06483 · 0% AI
2023-07197 · 0% AI
2023-08144 · 0% AI
2023-09805 · 0% AI
2023-10476 · 0% AI
2023-11569 · 0% AI
2023-12269 · 0% AI
2024-01834 · 0% AI
2024-02696 · 0% AI
2024-03879 · 0% AI
2024-04433 · 0% AI
2024-05102 · 0% AI
2024-06614 · 0% AI
2024-071,360 · 0% AI
2024-0899 · 0% AI
2024-09321 · 0% AI
2024-10928 · 0% AI
2024-1168 · 0% AI
2024-121,547 · 0% AI
2025-01441 · 0% AI
2025-02261 · 0% AI
2025-03237 · 0% AI
2025-0474 · 0% AI
2025-05512 · 0% AI
2025-06577 · 0% AI
2025-0735 · 0% AI
2025-0881 · 0% AI
2025-0954 · 0% AI
2025-10264 · 0% AI
2025-11250 · 0% AI
2025-12427 · 0% AI
2026-011,188 · 0% AI
2026-02255 · 0% AI
2026-03467 · 0% AI
2026-0475 · 0% AI
2026-05361 · 0% AI
2026-06574 · 0% AI
2026-07133 · 0% AI
2026-08313 · 0% AI
2026-09555 · 0% AI
2026-101,406 · 0% AI
2026-111,091 · 0% AI

Findings in AI-attributed lines vs the rest

From git blame: 0 lines trace to AI-attributed commits, 48,476 to others. Too few lines in one group for a fair comparison. Reported, not scored.

Findings per 1,000 lines	AI-attributed	Other	Ratio
Code quality	—	2.64	—
Security	—	3.69	—

Evidence by analyzer

Explicit AI attributionok5 items

Claude Code: 2 attributed commits, 0 lines added
GitHub Copilot coding agent: 1 attributed commits, 0 lines added
Claude Code: trailer 'Co-authored-by: Claude'
Claude Code: trailer 'Co-authored-by: Claude'
GitHub Copilot coding agent: trailer 'Co-authored-by: Copilot'

attributed_commit_share: 0.0%
attributed_commits: 3
attributed_loc: 0
attributed_loc_share: 0.0%
commits: 19,124
effective_loc: 248,648
tools_detected: 2

AI tool configurationok

artifacts: 0
tools_configured: 0
workflow_agents: 0

Commit velocityok1 item

1,545 lines of first-party code in ~0.5h (3,090 lines/hour, PR #13868)

excluded_import_loc: 33,636
flagged_loc: 1,545
flagged_loc_share: 0.7%
flagged_units: 1
max_loc_per_hour: 4,333.41
measured_loc: 212,516
median_loc_per_hour: 53.50
pr_timed_units: 940
pre_ai_era_burst_loc: 22,226
pre_ai_era_bursts: 4
pre_ai_era_measured_loc: 175,653
work_units: 4,036

Release velocityok

flagged_releases: 0
max_loc_per_day: 963
releases: 99

Coding styleok

count:assistant_voice: 0
count:emoji_in_code: 2
count:narrated_steps: 0
count:placeholder: 0
files:assistant_voice: 0
files:emoji_in_code: 1
files:narrated_steps: 0
files:placeholder: 0
index: 0.02
lines_scanned: 48,476
per_kloc:assistant_voice: 0
per_kloc:emoji_in_code: 0.04
per_kloc:narrated_steps: 0
per_kloc:placeholder: 0

Findings in AI-written linesok

ai_lines: 0
blame_failures: 0
files_blamed: 280
other_lines: 48,476
quality:ai_findings: 0
quality:other_findings: 128
quality:other_per_kloc: 2.64
security:ai_findings: 0
security:other_findings: 179
security:other_per_kloc: 3.69

Code quality

63 weak

Code quality is weak: test-to-source ratio 0.08, CI runs tests; 35% of function code in complex or long functions; 7% duplicated lines. Weakest area: complexity.

How the score is built

Complexity35
Duplication65
Lint and smells85
Tests and CI70
Documentation80
Type safetynot measured
Review process50

Evidence by analyzer

Complexity (lizard)ok10 items

complex_functions: 77
function_nloc: 32,297
functions: 1,665
long_functions: 40
many_param_functions: 11
mean_ccn: 3.64
p90_ccn: 8
risky_nloc_share: 35.2%

Duplication (jscpd)ok10 items

compared_lines: 29,532
duplicated_lines: 2,119
duplicated_share: 7.2%
files: 280

Lintok

category:best-practice: 127
category:correctness: 1
findings: 128
scanned_lines: 48,476
weighted_findings: 32

Tests and CIok8 items

CI config: .github/workflows/codeql-analysis.yml .github/workflows/codeql-analysis.yml
CI config: .github/workflows/definitions-update.yml .github/workflows/definitions-update.yml
CI config: .github/workflows/issuebot.yml .github/workflows/issuebot.yml
CI config: .github/workflows/schema-docs.yml .github/workflows/schema-docs.yml
CI config: .github/workflows/winget.yml .github/workflows/winget.yml
CI config: azure-pipelines.yml azure-pipelines.yml
CI runs tests (rspec, unittest)
CI runs linters (dotnet format)

check:ci_present: yes
check:ci_runs_lint: yes
check:ci_runs_tests: yes
check:has_tests: yes
check:test_ratio: no
check:tests_cochange: no
ci_files: 6
cochange_commits: 50
cochange_share: 2.0%
source_lines: 48,476
test_lines: 3,924
test_ratio: 0.08

Documentationok3 items

README.md README.md
LICENSE LICENSE
CONTRIBUTING.md CONTRIBUTING.md

check:changelog: no
check:contributing: yes
check:license: yes
check:readme: yes
readme_lines: 1,231

Type safetyskipped

Security

59 weak

Security posture is weak: 1 high-severity SAST findings; 14 high-severity workflow issues. Weakest area: ci actions.

How the score is built

Secrets88
Static analysis (SAST)64
Vulnerable dependenciesnot measured
CI workflows5
Security posture80
OpenSSF Scorecard38

Evidence by analyzer

OpenSSF Scorecardok13 items

aggregate: 4.40
check:Binary-Artifacts: yes
check:Branch-Protection: yes
check:CII-Best-Practices: no
check:Code-Review: no
check:Dangerous-Workflow: yes
check:Fuzzing: no
check:License: yes
check:Maintained: yes
check:Pinned-Dependencies: no
check:SAST: yes
check:Security-Policy: yes
check:Signed-Releases: no
check:Token-Permissions: no

Package registriesskipped

no registry dependencies declared

Secrets (gitleaks)ok

secrets_current: 0
secrets_history: 0
secrets_low_confidence: 4
secrets_nonprod: 0

Static analysis (opengrep)ok

findings: 238
findings_high: 1
findings_low: 3
findings_medium: 234
parse_errors: 1
scanned_lines: 48,476
weighted_findings: 61.90

Dependencies (osv-scanner)skipped

CI workflows (zizmor)ok

findings: 26
findings_high: 14
findings_low: 10
findings_medium: 2
penalty: 177.60
workflows: 5

Security postureok2 items

Security policy: SECURITY.md SECURITY.md
Dependency updates: .github/dependabot.yml .github/dependabot.yml

check:dependency_updates: yes
check:lockfiles: yes
check:security_policy: yes
check:signed_commits: no
signed_commit_share: 15.5%
unpinned_manifests: 0

Release downloadsok6 items

release v0.24.3065 ships Jackett.Binaries.LinuxAMDx64.tar.gz (9734 downloads)
release v0.24.3065 ships Jackett.Binaries.LinuxARM32.tar.gz (185 downloads)
release v0.24.3065 ships Jackett.Binaries.LinuxARM64.tar.gz (853 downloads)
release v0.24.3065 ships Jackett.Binaries.LinuxMuslAMDx64.tar.gz (8678 downloads)
release v0.24.3065 ships Jackett.Binaries.LinuxMuslARM32.tar.gz (31 downloads)
links directly to a downloadable archive or installer README.md

binary_assets: 110
signals: 2
suspicious: 0

Findings

15 high236 medium141 low4 info

Severity	Rule	Location	Message	Tool
high	`zizmor/unpinned-uses`	.github/workflows/codeql-analysis.yml:60	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/codeql-analysis.yml:64	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/codeql-analysis.yml:76	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/codeql-analysis.yml:90	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/github-app`	.github/workflows/definitions-update.yml:24	dangerous use of GitHub App tokens [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/definitions-update.yml:24	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/definitions-update.yml:37	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/definitions-update.yml:47	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/issuebot.yml:23	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/issuebot.yml:27	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/schema-docs.yml:17	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/schema-docs.yml:20	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/schema-docs.yml:30	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`zizmor/unpinned-uses`	.github/workflows/winget.yml:11	unpinned action reference [confidence high]	CI workflows (zizmor)
high	`opengrep/csharp.lang.security.open-redirect`	src/Jackett.Server/Controllers/DownloadController.cs:70	A query string parameter may contain a URL value that could cause the web application to redirect the request to a malicious website controlled by an attacker. Make sure to sanitize this parameter sufficiently. [confidence low]	Static analysis (opengrep)
medium	`zizmor/dependabot-cooldown`	.github/dependabot.yml:3	insufficient cooldown in Dependabot updates [confidence high]	CI workflows (zizmor)
medium	`zizmor/excessive-permissions`	.github/workflows/schema-docs.yml:11	overly broad permissions [confidence medium]	CI workflows (zizmor)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1051	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:1054	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/custom.js:1057	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1057	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/custom.js:1152	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1152	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1152	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/custom.js:1160	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1160	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1160	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/custom.js:1167	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1167	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1167	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:1296	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:1309	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1309	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:1461	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:1465	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1514	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:1519	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/custom.js:1602	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1602	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1616	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:1620	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/custom.js:1621	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:1621	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:242	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/custom.js:253	User controlled data in a jQuery's `.append(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:267	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:269	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:270	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/custom.js:310	User controlled data in a jQuery's `.append(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:315	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:317	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/custom.js:469	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:469	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:504	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:531	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:768	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:771	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:771	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:773	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:800	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:802	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:803	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:804	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:805	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/custom.js:807	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:807	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:811	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:813	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:873	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:875	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:875	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:891	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:924	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/custom.js:97	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:97	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:970	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:971	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:972	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:973	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:974	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:975	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:976	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:977	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:978	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:979	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:980	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:980	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:981	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:981	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/custom.js:982	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/custom.js:982	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:253	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:253	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:253	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:254	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape`	src/Jackett.Common/Content/index.html:255	Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:255	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:260	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:261	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:262	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:263	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:264	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:269	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:274	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:275	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:276	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:277	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:278	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:283	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:285	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:286	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:286	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:287	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:288	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:288	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:289	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:290	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:291	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:296	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:297	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:298	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:299	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:299	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:300	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:301	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:301	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:302	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:303	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape`	src/Jackett.Common/Content/index.html:308	Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:308	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape`	src/Jackett.Common/Content/index.html:311	Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:311	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:315	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:322	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:323	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:323	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:324	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape`	src/Jackett.Common/Content/index.html:331	Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:331	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:331	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:331	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:331	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:784	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:784	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:785	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:786	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:786	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:786	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:786	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:786	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.express.security.audit.xss.mustache.var-in-script-tag`	src/Jackett.Common/Content/index.html:787	Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the...	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1025	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1028	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1032	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1032	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1039	User controlled data in a jQuery's `.prepend(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1069	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1074	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1149	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1150	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1153	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1154	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1158	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1166	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1172	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1217	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1218	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1392	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1402	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1437	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1447	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:164	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1671	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1671	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.lang.security.audit.unsafe-dynamic-method`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:1761	Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:188	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:261	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:262	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:319	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:319	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:328	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:459	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:470	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:509	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:550	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:579	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:623	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:626	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:63	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:671	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:774	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:777	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:797	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:801	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:802	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:808	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:809	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:830	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:861	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:872	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:879	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:885	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:885	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:898	User controlled data in a jQuery's `.prepend(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:936	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:946	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:947	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:954	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:954	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:965	User controlled data in a jQuery's `.prepend(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:968	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:988	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:991	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:994	User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/libs/bootstrap-multiselect.js:994	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`	src/Jackett.Common/Content/libs/bootstrap-notify.js:146	JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-notify.js:159	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-notify.js:159	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-notify.js:209	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-notify.js:209	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`	src/Jackett.Common/Content/libs/bootstrap-notify.js:229	User controlled data in a jQuery's `.append(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-notify.js:229	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`	src/Jackett.Common/Content/libs/bootstrap-notify.js:343	User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.regular-expression-dos.regular-expression-dos`	src/Jackett.Common/Indexers/Definitions/Abstract/PublicBrazilianIndexerBase.cs:220	When using `System.Text.RegularExpressions` to process untrusted input, pass a timeout. A malicious user can provide input to `RegularExpressions` that abuses the backtracking behaviour of this regular expression engine. This will lead...	Static analysis (opengrep)
medium	`opengrep/csharp.dotnet.security.mvc-missing-antiforgery`	src/Jackett.Server/Controllers/ServerConfigurationController.cs:291	Shutdown is a state-changing MVC method that does not validate the antiforgery token or do strict content-type checking. State-changing controller methods should either enforce antiforgery tokens or do strict content-type checking to...	Static analysis (opengrep)
medium	`opengrep/csharp.dotnet.security.mvc-missing-antiforgery`	src/Jackett.Server/Controllers/ServerConfigurationController.cs:50	AdminPassword is a state-changing MVC method that does not validate the antiforgery token or do strict content-type checking. State-changing controller methods should either enforce antiforgery tokens or do strict content-type checking...	Static analysis (opengrep)
medium	`opengrep/csharp.dotnet.security.mvc-missing-antiforgery`	src/Jackett.Server/Controllers/ServerConfigurationController.cs:76	UpdateConfig is a state-changing MVC method that does not validate the antiforgery token or do strict content-type checking. State-changing controller methods should either enforce antiforgery tokens or do strict content-type checking...	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:132	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:134	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.stacktrace-disclosure`	src/Jackett.Server/Startup.cs:134	Stacktrace information is displayed in a non-Development environment. Accidentally disclosing sensitive stack trace information in a production environment aids an attacker in reconnaissance and information gathering. [confidence high]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:136	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:142	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:145	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:152	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:154	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:156	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:159	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:161	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:169	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:171	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.stacktrace-disclosure`	src/Jackett.Server/Startup.cs:171	Stacktrace information is displayed in a non-Development environment. Accidentally disclosing sensitive stack trace information in a production environment aids an attacker in reconnaissance and information gathering. [confidence high]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:173	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:179	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:182	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:189	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:191	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:193	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:195	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:198	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.missing-hsts-header`	src/Jackett.Server/Startup.cs:200	The HSTS HTTP response security header is missing, allowing interaction and communication to be sent over the insecure HTTP protocol. [confidence low]	Static analysis (opengrep)
medium	`opengrep/csharp.lang.security.filesystem.unsafe-path-combine`	src/Jackett.Test/TestHelpers/TestUtil.cs:60	String argument fileName is used to read or write data from a file via Path.Combine without direct sanitization via Path.GetFileName. If the path is user-supplied data this can lead to path traversal. [confidence medium]	Static analysis (opengrep)
low	`opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command`	jackett_launcher.sh:21	Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/BaseIndexer.cs:324	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/BaseIndexer.cs:336	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/AniDUB.cs:388	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/AniDUB.cs:518	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/BigBbs.cs:348	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/BigBbs.cs:520	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/BigBbs.cs:522	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/BigBbs.cs:526	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/BigBbs.cs:549	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/BrasilTracker.cs:210	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/BrasilTracker.cs:346	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/CardigannIndexer.cs:1253	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/CardigannIndexer.cs:1260	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/CardigannIndexer.cs:2005	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/CardigannIndexer.cs:2059	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/CardigannIndexer.cs:2065	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/CardigannIndexer.cs:2166	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/CardigannIndexer.cs:2183	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/CardigannIndexer.cs:849	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/CardigannIndexer.cs:972	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/DivxTotal.cs:182	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/EraiRaws.cs:231	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/EraiRaws.cs:247	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/EraiRaws.cs:253	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/LostFilm.cs:815	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/LostFilm.cs:820	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/MyAnonamouse.cs:335	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/RuTracker.cs:1662	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/Shazbat.cs:147	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/TamilMV.cs:221	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/TamilMV.cs:327	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/TamilMV.cs:459	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/TamilMV.cs:508	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/Toloka.cs:362	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Indexers/Definitions/XSpeeds.cs:192	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/CacheService.cs:102	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/CacheService.cs:108	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/CacheService.cs:141	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/CacheService.cs:158	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/CacheService.cs:205	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/CacheService.cs:231	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/CacheService.cs:256	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/CacheService.cs:79	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/ConfigurationService.cs:174	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/ConfigurationService.cs:192	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/ConfigurationService.cs:99	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerConfigurationService.cs:113	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerConfigurationService.cs:124	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerConfigurationService.cs:56	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerConfigurationService.cs:64	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerConfigurationService.cs:69	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerConfigurationService.cs:72	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerConfigurationService.cs:86	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerManagerService.cs:203	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerManagerService.cs:221	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerManagerService.cs:232	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerManagerService.cs:241	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerManagerService.cs:242	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerManagerService.cs:246	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerManagerService.cs:282	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerManagerService.cs:327	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerManagerService.cs:350	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/IndexerManagerService.cs:368	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/UpdateService.cs:174	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/UpdateService.cs:209	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/UpdateService.cs:225	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/UpdateService.cs:231	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/UpdateService.cs:375	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/UpdateService.cs:395	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/UpdateService.cs:397	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Services/UpdateService.cs:79	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Utils/Clients/WebClient.cs:183	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Utils/Clients/WebClient.cs:209	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Common/Utils/Clients/WebClient.cs:74	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/BlackholeController.cs:46	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/DownloadController.cs:48	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ImageController.cs:45	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:328	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:330	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:349	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:394	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:400	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:406	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:415	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:421	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:430	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:464	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:466	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:566	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Controllers/ResultsController.cs:568	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Initialisation.cs:16	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Initialisation.cs:163	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Middleware/CustomExceptionHandler.cs:56	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Program.cs:123	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Program.cs:131	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Program.cs:69	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/FilePermissionService.cs:19	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:103	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:120	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:124	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:141	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:186	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:202	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:211	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:230	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:265	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:286	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:304	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:328	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:337	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:82	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:88	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Services/ServerService.cs:98	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Startup.cs:207	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Server/Startup.cs:210	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Tray/Main.cs:111	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Tray/Main.cs:85	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Updater/Program.cs:102	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Updater/Program.cs:105	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Updater/Program.cs:1082	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Updater/Program.cs:1108	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Updater/Program.cs:111	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Updater/Program.cs:115	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Updater/Program.cs:119	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Updater/Program.cs:146	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Updater/Program.cs:197	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`opengrep/csharp.lang.best-practice.structured-logging`	src/Jackett.Updater/Program.cs:72	String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging...	Lint
low	`zizmor/artipacked`	.github/workflows/codeql-analysis.yml:59	credential persistence through GitHub Actions artifacts [confidence low]	CI workflows (zizmor)
low	`zizmor/artipacked`	.github/workflows/definitions-update.yml:36	credential persistence through GitHub Actions artifacts [confidence low]	CI workflows (zizmor)
low	`zizmor/artipacked`	.github/workflows/issuebot.yml:22	credential persistence through GitHub Actions artifacts [confidence low]	CI workflows (zizmor)
low	`zizmor/adhoc-packages`	.github/workflows/issuebot.yml:33	ad-hoc installation of packages [confidence high]	CI workflows (zizmor)
low	`zizmor/artipacked`	.github/workflows/schema-docs.yml:16	credential persistence through GitHub Actions artifacts [confidence low]	CI workflows (zizmor)
low	`zizmor/adhoc-packages`	.github/workflows/schema-docs.yml:23	ad-hoc installation of packages [confidence high]	CI workflows (zizmor)
low	`gitleaks/generic-api-key`	src/Jackett.Common/Indexers/Definitions/Wolfmax4K.cs:44	Possible generic-api-key secret in history (commit 2a16d0dabd); removed from the current tree but still retrievable	Secrets (gitleaks)
low	`gitleaks/generic-api-key`	src/Jackett.Common/Indexers/Wolfmax4K.cs:37	Possible generic-api-key secret in history (commit 0eb5861c37); removed from the current tree but still retrievable	Secrets (gitleaks)
low	`opengrep/csharp.dotnet.security.audit.missing-or-broken-authorization`	src/Jackett.Server/Controllers/IndexerApiController.cs:56	Anonymous access shouldn't be allowed unless explicit by design. Access control checks are missing and potentially can be bypassed. This finding violates the principle of least privilege or deny by default, where access should only be...	Static analysis (opengrep)
low	`opengrep/csharp.dotnet.security.audit.missing-or-broken-authorization`	src/Jackett.Server/Controllers/ServerConfigurationController.cs:18	Anonymous access shouldn't be allowed unless explicit by design. Access control checks are missing and potentially can be bypassed. This finding violates the principle of least privilege or deny by default, where access should only be...	Static analysis (opengrep)
low	`opengrep/csharp.dotnet.security.audit.missing-or-broken-authorization`	src/Jackett.Server/Controllers/UIController.cs:15	Anonymous access shouldn't be allowed unless explicit by design. Access control checks are missing and potentially can be bypassed. This finding violates the principle of least privilege or deny by default, where access should only be...	Static analysis (opengrep)
low	`gitleaks/generic-api-key`	src/Jackett.Server/Services/ProtectionService.cs:10	Possible generic-api-key secret in the current tree	Secrets (gitleaks)
low	`gitleaks/generic-api-key`	src/Jackett/Services/ProtectionService.cs:21	Possible generic-api-key secret in history (commit 3bdf3c8a6a); removed from the current tree but still retrievable	Secrets (gitleaks)
info	`zizmor/template-injection`	.github/workflows/definitions-update.yml:32	code injection via template expansion [confidence low]	CI workflows (zizmor)
info	`zizmor/template-injection`	.github/workflows/definitions-update.yml:57	code injection via template expansion [confidence low]	CI workflows (zizmor)
info	`zizmor/template-injection`	.github/workflows/definitions-update.yml:58	code injection via template expansion [confidence low]	CI workflows (zizmor)
info	`zizmor/template-injection`	.github/workflows/definitions-update.yml:58	code injection via template expansion [confidence low]	CI workflows (zizmor)

Tools and coverage

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

Analyzer	Pillar	Status	Version	Findings	Note
AI tool configuration	AI provenance	ok	`signatures-v1`	0
Explicit AI attribution	AI provenance	ok	`signatures-v1`	0
Release velocity	AI provenance	ok	`prov-5`	0
Coding style	AI provenance	ok	`—`	0
Commit velocity	AI provenance	ok	`prov-5`	0
Findings in AI-written lines	AI provenance	ok	`git-blame`	0
Complexity (lizard)	Code quality	ok	`lizard 1.25.1`	0
Documentation	Code quality	ok	`—`	0
Duplication (jscpd)	Code quality	ok	`repotrust-dup-w6`	0
Lint	Code quality	ok	`opengrep 1.33.1; rules f1d2b562b414`	128
Tests and CI	Code quality	ok	`—`	0
Type safety	Code quality	skipped	`—`	0
CI workflows (zizmor)	Security	ok	`zizmor 1.32.0`	26
Dependencies (osv-scanner)	Security	skipped	`—`	0
Release downloads	Security	ok	`—`	0
Security posture	Security	ok	`—`	0
Package registries	Security	skipped	`—`	0	no registry dependencies declared
Static analysis (opengrep)	Security	ok	`opengrep 1.33.1; rules f1d2b562b414`	238
OpenSSF Scorecard	Security	ok	`scorecard v5.6.0`	0
Secrets (gitleaks)	Security	ok	`gitleaks 8.30.1`	4

Score history

Scored	Commit	Scoring	AI provenance	Quality	Security
2026-11-14	`95d94bdefc0f`	`prov-5+qual-2+sec-2`	0%	63	59

Embed a badge

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

[![RepoTrust ai](https://repotrust.synapticcyber.com/badge/github.com/Jackett/Jackett/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/Jackett/Jackett/)

[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/Jackett/Jackett/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/Jackett/Jackett/)

[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/Jackett/Jackett/security.svg)](https://repotrust.synapticcyber.com/r/github.com/Jackett/Jackett/)

Full text report

Repository: https://github.com/Jackett/Jackett
Commit: 95d94bdefc0fa2e149bdda9ef6ce73bbd52aa2c9
Generated: 2026-11-14T15:55:43+00:00
Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2

Scores

Pillar	Score	Signal	Confidence	Coverage
AI provenance (estimated AI-generated share)	0	explicit	95%	100%
Code quality	63	weak	90%	100%
Security	59	weak	85%	100%

AI provenance

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

Explicitly attributed share (lower bound): 0.0%
Unattributed share in AI-consistent velocity bursts: 0.6%
Estimated AI-generated share: 0.0%

AI tool	Attributed commits	Lines added
Claude Code	2	0
GitHub Copilot coding agent	1	0

Current source lines last changed by AI-attributed commits: 0 of 48,476.

Too few lines in one group to compare finding densities.

Stylometry index: 0.02 per 1,000 lines (narrated steps 0, placeholders 0, assistant phrasing 0, emoji 2). Reported as a signal, not scored.

Month	Lines added	Attributed to AI
2025-12	427	0%
2026-01	1,188	0%
2026-02	255	0%
2026-03	467	0%
2026-04	75	0%
2026-05	361	0%
2026-06	574	0%
2026-07	133	0%
2026-08	313	0%
2026-09	555	0%
2026-10	1,406	0%
2026-11	1,091	0%

Evidence

Claude Code: trailer 'Co-authored-by: Claude' (8dc28132f81b)
Claude Code: trailer 'Co-authored-by: Claude' (9165e438cca3)
GitHub Copilot coding agent: trailer 'Co-authored-by: Copilot' (6b4d3c1d3778)
1,545 lines of first-party code in ~0.5h (3,090 lines/hour, PR #13868) (ac535dc7ad04)

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

Code quality

Code quality is weak: test-to-source ratio 0.08, CI runs tests; 35% of function code in complex or long functions; 7% duplicated lines. Weakest area: complexity.

Area	Score
Complexity (lizard)	35
Duplication	65
Code smells (Opengrep)	85
Tests and CI	70
Documentation	80
Type safety	n/a
Process (Scorecard review/maintenance)	50

Functions: 1,665; mean complexity 3.6, 90th percentile 8; 77 complex and 40 long functions
Duplicated lines: 7.2% of 29,532 compared
Tests: 3,924 test lines for 48,476 source lines (ratio 0.08); CI test commands: rspec, unittest; 2% of recent source commits also change tests
Docs missing or thin: changelog

Most complex functions:

Security

Security posture is weak: 1 high-severity SAST findings; 14 high-severity workflow issues. Weakest area: ci actions.

Area	Score
Secrets (gitleaks, tree + history)	88
Static analysis (Opengrep)	64
Vulnerable dependencies (OSV)	n/a
CI workflows (zizmor)	5
Posture (policy, updates, signing, lockfiles)	80
OpenSSF Scorecard	38

Posture checks passed: security policy, dependency updates, lockfiles; missing: signed commits
OpenSSF Scorecard aggregate: 4.4/10 (published 2026-11-09)

Top findings

Severity	Finding	Location
high	`opengrep/csharp.lang.security.open-redirect`: A query string parameter may contain a URL value that could cause the web application to redirect the request to a malicious website controlled by an attacker. Make sure to sanitize this parameter sufficiently. [confidence low]	src/Jackett.Server/Controllers/DownloadController.cs:70
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/codeql-analysis.yml:60
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/codeql-analysis.yml:64
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/codeql-analysis.yml:76
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/codeql-analysis.yml:90
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/definitions-update.yml:24
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/definitions-update.yml:37
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/definitions-update.yml:47
high	`zizmor/github-app`: dangerous use of GitHub App tokens [confidence high]	.github/workflows/definitions-update.yml:24
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/issuebot.yml:23
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/issuebot.yml:27
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/schema-docs.yml:17
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/schema-docs.yml:20
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/schema-docs.yml:30
high	`zizmor/unpinned-uses`: unpinned action reference [confidence high]	.github/workflows/winget.yml:11
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`: User controlled data in a jQuery's `.html(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	src/Jackett.Common/Content/custom.js:97
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`: JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	src/Jackett.Common/Content/custom.js:97
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`: JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	src/Jackett.Common/Content/custom.js:242
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`: User controlled data in a jQuery's `.append(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	src/Jackett.Common/Content/custom.js:253
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`: JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	src/Jackett.Common/Content/custom.js:267
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`: User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	src/Jackett.Common/Content/custom.js:269
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-selector`: User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	src/Jackett.Common/Content/custom.js:270
medium	`opengrep/javascript.jquery.security.audit.jquery-insecure-method`: User controlled data in a jQuery's `.append(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low]	src/Jackett.Common/Content/custom.js:310
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`: JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	src/Jackett.Common/Content/custom.js:315
medium	`opengrep/javascript.jquery.security.audit.prohibit-jquery-html`: JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low]	src/Jackett.Common/Content/custom.js:317

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

Distribution signals

binary-release-asset: release v0.24.3065 ships Jackett.Binaries.LinuxAMDx64.tar.gz (9734 downloads)
binary-release-asset: release v0.24.3065 ships Jackett.Binaries.LinuxARM32.tar.gz (185 downloads)
binary-release-asset: release v0.24.3065 ships Jackett.Binaries.LinuxARM64.tar.gz (853 downloads)
binary-release-asset: release v0.24.3065 ships Jackett.Binaries.LinuxMuslAMDx64.tar.gz (8678 downloads)
binary-release-asset: release v0.24.3065 ships Jackett.Binaries.LinuxMuslARM32.tar.gz (31 downloads)
readme-download-lure: links directly to a downloadable archive or installer

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

Repository profile

Source lines: 48,476; test lines: 3,924

Language	Lines
C#	47,884
JavaScript	4,221
Shell	295