Leaderboard github.com
unconed/TermKit
Experimental Terminal platform built on WebKit + node.js. Currently only for Mac and Windows, though the prototype works 90% in any WebKit browser.
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
52/100
weak
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
67/100
weak
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% none-detected
No AI attribution or AI-consistent velocity signals detected.
How the score is built
- Explicitly attributed share0%
- Unattributed share in AI-pace bursts0%
- Estimated AI-generated share0%
- AI tool configuration files0
- Work sessions at AI pace0
- Releases at AI pacenot measured
- Coding-style index (1.0+ means possible)0.24
Lines added per month all AI-attributed share
- 2010-02121 · 0% AI
- 2010-031,482 · 0% AI
- 2010-04234 · 0% AI
- 2010-05336 · 0% AI
- 2010-06188 · 0% AI
- 2010-07169 · 0% AI
- 2010-0837 · 0% AI
- 2010-091,330 · 0% AI
- 2010-101,501 · 0% AI
- 2010-114,685 · 0% AI
- 2010-1245 · 0% AI
- 2011-03476 · 0% AI
- 2011-046,810 · 0% AI
- 2011-0519,304 · 0% AI
- 2011-061,479 · 0% AI
- 2011-070 · 0% AI
Evidence by analyzer
Explicit AI attributionok
- attributed_commit_share
- 0.0%
- attributed_commits
- 0
- attributed_loc
- 0
- attributed_loc_share
- 0.0%
- commits
- 295
- effective_loc
- 38,197
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 24,534
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 591.50
- measured_loc
- 13,663
- median_loc_per_hour
- 74.59
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 13,663
- work_units
- 81
Release velocityskipped
Coding styleok6 items
- assistant-style phrasing left in code: // Format a name, short or long as requested
- step-by-step narration comment: //Now we fake the start of dragging for the sortable instance,
- step-by-step narration comment: //Now we remove our currentItem, the list group clone again, and the placeholder, and animate the helper back to it's or
- step-by-step narration comment: // Finally, go through the final list of matches and pull the all
- step-by-step narration comment: // finally, split all lines so that they wrap well
- step-by-step narration comment: // finally, process the links
- count:assistant_voice
- 1
- count:emoji_in_code
- 0
- count:narrated_steps
- 5
- count:placeholder
- 0
- files:assistant_voice
- 1
- files:emoji_in_code
- 0
- files:narrated_steps
- 2
- files:placeholder
- 0
- index
- 0.24
- lines_scanned
- 28,532
- per_kloc:assistant_voice
- 0.04
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0.17
- per_kloc:placeholder
- 0
Code quality
52 weak
Code quality is weak: test-to-source ratio 0.00, no CI test run detected; 12% of function code in complex or long functions; 18% duplicated lines. Weakest area: testing.
How the score is built
- Complexity69
- Duplication34
- Lint and smells87
- Tests and CI21
- Documentation65
- Type safetynot measured
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok10 items
- _generateHTML in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js: complexity 90, 166 lines
- drag in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.js: complexity 44, 39 lines
- _doKeyDown in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js: complexity 43, 64 lines
- parseDate in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js: complexity 39, 92 lines
- _mouseDrag in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js: complexity 32, 57 lines
- _clear in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js: complexity 32, 53 lines
- (anonymous) in Node/misc.js: complexity 32, 70 lines
- _generatePosition in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js: complexity 30, 38 lines
- _generatePosition in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.js: complexity 29, 35 lines
- $.ui.intersect in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.droppable.js: complexity 29, 39 lines
- complex_functions
- 43
- function_nloc
- 20,478
- functions
- 1,878
- long_functions
- 3
- many_param_functions
- 1
- mean_ccn
- 2.96
- p90_ccn
- 6
- risky_nloc_share
- 12.4%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: HTML/external/jquery-ui/development-bundle/ui/i18n/jquery-ui-i18n.js:1 and HTML/external/jquery-ui/development-bundle/ui/i18n/jquery.ui.datepicker-af.js:1
- 6+ duplicated lines: HTML/external/jquery-ui/development-bundle/ui/i18n/jquery-ui-i18n.js:16 and HTML/external/jquery-ui/development-bundle/ui/i18n/jquery-ui-i18n.js:265
- 6+ duplicated lines: HTML/external/jquery-ui/development-bundle/ui/i18n/jquery-ui-i18n.js:24 and HTML/external/jquery-ui/development-bundle/ui/i18n/jquery.ui.datepicker-ar-DZ.js:1
- 6+ duplicated lines: HTML/external/jquery-ui/development-bundle/ui/i18n/jquery-ui-i18n.js:47 and HTML/external/jquery-ui/development-bundle/ui/i18n/jquery.ui.datepicker-ar.js:1
- 6+ duplicated lines: HTML/external/jquery-ui/development-bundle/ui/i18n/jquery-ui-i18n.js:70 and HTML/external/jquery-ui/development-bundle/ui/i18n/jquery.ui.datepicker-az.js:2
- 6+ duplicated lines: HTML/external/jquery-ui/development-bundle/ui/i18n/jquery-ui-i18n.js:92 and HTML/external/jquery-ui/development-bundle/ui/i18n/jquery.ui.datepicker-bg.js:2
- 6+ duplicated lines: HTML/external/jquery-ui/development-bundle/ui/i18n/jquery-ui-i18n.js:115 and HTML/external/jquery-ui/development-bundle/ui/i18n/jquery.ui.datepicker-bs.js:1
- 6+ duplicated lines: HTML/external/jquery-ui/development-bundle/ui/i18n/jquery-ui-i18n.js:138 and HTML/external/jquery-ui/development-bundle/ui/i18n/jquery.ui.datepicker-ca.js:2
- 6+ duplicated lines: HTML/external/jquery-ui/development-bundle/ui/i18n/jquery-ui-i18n.js:160 and HTML/external/jquery-ui/development-bundle/ui/i18n/jquery.ui.datepicker-cs.js:2
- 6+ duplicated lines: HTML/external/jquery-ui/development-bundle/ui/i18n/jquery-ui-i18n.js:182 and HTML/external/jquery-ui/development-bundle/ui/i18n/jquery.ui.datepicker-da.js:1
- compared_lines
- 20,154
- duplicated_lines
- 3,625
- duplicated_share
- 18.0%
- files
- 199
Lintok
- category:best-practice
- 3
- category:correctness
- 25
- findings
- 28
- scanned_lines
- 27,887
- weighted_findings
- 15.25
Tests and CIok
- check:ci_present
- no
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- yes
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 0
- cochange_commits
- 156
- cochange_share
- 3.2%
- source_lines
- 28,532
- test_lines
- 65
- test_ratio
- 0.00
Documentationok2 items
- Readme.md
Readme.md - License.txt
License.txt
- check:changelog
- no
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 53
Type safetyskipped
Security
67 weak
Security posture is weak: 2 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets100
- Static analysis (SAST)59
- Vulnerable dependenciesnot measured
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesskipped
no registry dependencies declared
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 166
- findings_high
- 2
- findings_low
- 0
- findings_medium
- 164
- parse_errors
- 9
- scanned_lines
- 27,887
- weighted_findings
- 42.50
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok
- check:dependency_updates
- no
- check:lockfiles
- yes
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 0.0%
- unpinned_manifests
- 0
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
2 high175 medium17 low
194 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/javascript.browser.security.insecure-document-method |
HTML/external/syntaxhighlighter_3.0.83/src/shCore.js:1648 | User controlled data in methods like `innerHTML`, `outerHTML` or `document.write` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-innerhtml |
HTML/external/syntaxhighlighter_3.0.83/src/shCore.js:1648 | User controlled data in a `div.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
HTML/client/shell.js:145 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
HTML/client/shell.js:152 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
HTML/client/shell.js:165 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
HTML/client/shell.js:173 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
HTML/client/shell.js:175 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
HTML/client/shell.js:182 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
HTML/external/syntaxhighlighter_3.0.83/src/shCore.js:1218 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
HTML/external/syntaxhighlighter_3.0.83/src/shCore.js:692 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
HTML/termkit.js:19 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
Node/misc.js:164 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
Node/misc.js:165 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.lang.security.audit.prototype-pollution.prototype-pollution-assignment |
HTML/client/shell.js:165 | Possibility of prototype polluting assignment detected. By adding or modifying attributes of an object prototype, it is possible to create attributes that exist on every object, or replace critical attributes with malicious ones. This... | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
HTML/commandview/command.js:78 | 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 |
HTML/commandview/command.js:80 | 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.prohibit-jquery-html |
HTML/commandview/commandcontext.js:34 | 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 |
HTML/commandview/commandcontext.js:35 | 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 |
HTML/commandview/commandview.js:70 | 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 |
HTML/commandview/commandview.js:70 | 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.detect-non-literal-regexp |
HTML/external/jquery-ui/development-bundle/external/jquery.cookie.js:88 | RegExp() called with a `key` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use... | Static analysis (opengrep) |
| medium | opengrep/javascript.browser.security.eval-detected |
HTML/external/jquery-ui/development-bundle/external/jquery.metadata.js:101 | Detected the use of eval(). eval() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.effects.core.js:243 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.effects.core.js:251 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.effects.core.js:477 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.effects.core.js:586 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.effects.transfer.js:18 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.accordion.js:241 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.accordion.js:339 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.accordion.js:339 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.accordion.js:467 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.autocomplete.js:147 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.autocomplete.js:408 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.autocomplete.js:421 | RegExp() called with a `$` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.autocomplete.js:421 | RegExp() called with a `term` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use... | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.autocomplete.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.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.autocomplete.js:540 | 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.prohibit-jquery-html |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.button.js:228 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.button.js:232 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.button.js:291 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.button.js:34 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.button.js:74 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.core.js:178 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.core.js:213 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.core.js:277 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.browser.security.eval-detected |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:147 | Detected the use of eval(). eval() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by... | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:181 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:205 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:217 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:218 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:219 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:219 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:219 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:220 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:220 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:221 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:221 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:221 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:222 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:222 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:222 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.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-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:295 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:329 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:351 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:374 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:455 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:625 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:658 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:662 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:705 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:707 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:767 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:787 | 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-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:801 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:817 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:828 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:841 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:860 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:884 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:885 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:889 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:898 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:905 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js:934 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.dialog.js:179 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.dialog.js:401 | 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-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.dialog.js:643 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.dialog.js:643 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.dialog.js:742 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.dialog.js:785 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.js:244 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.js:340 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.js:341 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.js:639 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.js:645 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.js:75 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.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.jquery-insecure-selector |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.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.jquery-insecure-selector |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.js:789 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.js:795 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.mouse.js:58 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.position.js:135 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.position.js:224 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.position.js:28 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.resizable.js:151 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.resizable.js:200 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.resizable.js:535 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.resizable.js:562 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.resizable.js:593 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.selectable.js:117 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.selectable.js:89 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.slider.js:302 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:100 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:106 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:394 | User controlled data in a jQuery's `.after(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:396 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:409 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:410 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:427 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:658 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:681 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:681 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:762 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js:860 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.tabs.js:306 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.tabs.js:314 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.tabs.js:493 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.tabs.js:493 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.tabs.js:508 | User controlled data in a jQuery's `.appendTo(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-method |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.tabs.js:511 | User controlled data in a jQuery's `.insertBefore(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.tabs.js:627 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.tabs.js:627 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.tabs.js:633 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.tabs.js:96 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.tabs.js:96 | 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 |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.widget.js:149 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.browser.security.eval-detected |
HTML/external/syntaxhighlighter_3.0.83/scripts/shAutoloader.js:17 | Detected the use of eval(). eval() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
HTML/external/syntaxhighlighter_3.0.83/scripts/shAutoloader.js:17 | RegExp() called with a `c` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use... | Static analysis (opengrep) |
| medium | opengrep/javascript.browser.security.eval-detected |
HTML/external/syntaxhighlighter_3.0.83/scripts/shCore.js:17 | Detected the use of eval(). eval() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
HTML/external/syntaxhighlighter_3.0.83/scripts/shCore.js:17 | RegExp() called with a `c` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use... | Static analysis (opengrep) |
| medium | opengrep/javascript.browser.security.eval-detected |
HTML/external/syntaxhighlighter_3.0.83/scripts/shLegacy.js:17 | Detected the use of eval(). eval() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
HTML/external/syntaxhighlighter_3.0.83/scripts/shLegacy.js:17 | RegExp() called with a `c` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
HTML/external/syntaxhighlighter_3.0.83/src/shCore.js:191 | RegExp() called with a `name` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
HTML/external/syntaxhighlighter_3.0.83/src/shXRE.js:320 | RegExp() called with a `regex` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
HTML/external/syntaxhighlighter_3.0.83/src/shXRE.js:76 | RegExp() called with a `flags` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use... | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
HTML/outputview/outputfactory.js:112 | 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 |
HTML/outputview/outputnode.js:87 | 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 |
HTML/termkit.js:13 | 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 |
HTML/tokenfield/autocomplete.js:89 | 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 |
HTML/tokenfield/selection.js:79 | 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 |
HTML/tokenfield/token.js:67 | 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 |
HTML/tokenfield/tokenfield.js:60 | 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 |
HTML/tokenfield/tokenfield.js:70 | 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 |
HTML/tokenfield/tokenfield.js:70 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/config.js:61 | Detected that function argument `paths` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/autocomplete.js:178 | Detected that function argument `path` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/autocomplete.js:178 | Detected that function argument `prefix` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/autocomplete.js:196 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/autocomplete.js:196 | Detected that function argument `path` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/autocomplete.js:196 | Detected that function argument `prefix` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/builtin/ls.js:57 | Detected that function argument `path` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/builtin/ls.js:63 | Detected that function argument `path` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/formatter.js:348 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/formatter.js:348 | Detected that function argument `path` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/reader.js:202 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/reader.js:208 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/reader.js:218 | Detected that function argument `fd` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/reader.js:246 | Detected that function argument `fd` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/reader.js:340 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/reader.js:350 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/reader.js:358 | Detected that function argument `fd` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
Node/shell/reader.js:526 | Detected that function argument `files` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
Shared/protocol.js:62 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| low | opengrep/javascript.lang.correctness.useless-assignment |
HTML/external/jquery-ui/development-bundle/ui/jquery.effects.core.js:255 | `that.attr('style').cssText` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.resizable.js:133 | `padWrapper` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.eqeq-is-bad |
Node/shell/builtin/cat.js:72 | Detected a useless comparison operation `errors == errors` or `errors != errors`. This operation is always true. If testing for floating point NaN, use `math.isnan`, or `cmath.isnan` if the number is complex. | Lint |
| low | opengrep/javascript.lang.correctness.eqeq-is-bad |
Node/shell/builtin/get.js:23 | Detected a useless comparison operation `errors == errors` or `errors != errors`. This operation is always true. If testing for floating point NaN, use `math.isnan`, or `cmath.isnan` if the number is complex. | Lint |
| low | opengrep/javascript.lang.correctness.eqeq-is-bad |
Node/shell/builtin/grep.js:152 | Detected a useless comparison operation `errors == errors` or `errors != errors`. This operation is always true. If testing for floating point NaN, use `math.isnan`, or `cmath.isnan` if the number is complex. | Lint |
| low | opengrep/javascript.lang.correctness.eqeq-is-bad |
Node/shell/builtin/hex.js:49 | Detected a useless comparison operation `errors == errors` or `errors != errors`. This operation is always true. If testing for floating point NaN, use `math.isnan`, or `cmath.isnan` if the number is complex. | Lint |
| low | opengrep/javascript.lang.correctness.eqeq-is-bad |
Node/shell/builtin/ls.js:46 | Detected a useless comparison operation `errors == errors` or `errors != errors`. This operation is always true. If testing for floating point NaN, use `math.isnan`, or `cmath.isnan` if the number is complex. | Lint |
| low | opengrep/javascript.lang.correctness.eqeq-is-bad |
Node/shell/reader.js:228 | Detected a useless comparison operation `position == position` or `position != position`. This operation is always true. If testing for floating point NaN, use `math.isnan`, or `cmath.isnan` if the number is complex. | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
Node/test.js:579 | `pipe` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
Node/test.js:585 | `pipe` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
Node/test.js:591 | `pipe` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
Node/test.js:597 | `pipe` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
Node/test.js:603 | `pipe` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
Node/test.js:609 | `pipe` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
sloc.sh:11 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
sloc.sh:12 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
sloc.sh:13 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
Tools and coverage
Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.
| Analyzer | Pillar | Status | Version | Findings | Note |
|---|---|---|---|---|---|
| AI tool configuration | AI provenance | ok | signatures-v1 | 0 | |
| Explicit AI attribution | AI provenance | ok | signatures-v1 | 0 | |
| Release velocity | AI provenance | skipped | — | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-4 | 0 | |
| 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 | 28 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | skipped | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| 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 | 166 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 0 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 2d368b849d61 | prov-5+qual-2+sec-2 | 0% | 52 | 67 |
| 2026-11-14 | 2d368b849d61 | prov-4+qual-2+sec-2 | 0% | 52 | 67 |
Full text report
- Repository: https://github.com/unconed/TermKit
- Commit:
2d368b849d6185df661bf89f742455875c00da2a - Generated: 2026-11-14T14:52:08+00:00
- Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | none-detected | 65% | 100% |
| Code quality | 52 | weak | 90% | 100% |
| Security | 67 | weak | 85% | 100% |
AI provenance
No AI attribution or AI-consistent velocity signals detected.
-
Explicitly attributed share (lower bound): 0.0%
-
Unattributed share in AI-consistent velocity bursts: 0.0%
-
Estimated AI-generated share: 0.0%
-
Stylometry index: 0.24 per 1,000 lines (narrated steps 5, placeholders 0, assistant phrasing 1, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2010-05 | 336 | 0% |
| 2010-06 | 188 | 0% |
| 2010-07 | 169 | 0% |
| 2010-08 | 37 | 0% |
| 2010-09 | 1,330 | 0% |
| 2010-10 | 1,501 | 0% |
| 2010-11 | 4,685 | 0% |
| 2010-12 | 45 | 0% |
| 2011-03 | 476 | 0% |
| 2011-04 | 6,810 | 0% |
| 2011-05 | 19,304 | 0% |
| 2011-06 | 1,479 | 0% |
Evidence
- assistant-style phrasing left in code: // Format a name, short or long as requested (HTML/externa)
- step-by-step narration comment: //Now we fake the start of dragging for the sortable instance, (HTML/externa)
- step-by-step narration comment: //Now we remove our currentItem, the list group clone again, and the placeholder, and animate the helper back to it's or (HTML/externa)
- step-by-step narration comment: // Finally, go through the final list of matches and pull the all (HTML/externa)
- step-by-step narration comment: // finally, split all lines so that they wrap well (HTML/externa)
- step-by-step narration comment: // finally, process the links (HTML/externa)
AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.
Code quality
Code quality is weak: test-to-source ratio 0.00, no CI test run detected; 12% of function code in complex or long functions; 18% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 69 |
| Duplication | 34 |
| Code smells (Opengrep) | 87 |
| Tests and CI | 21 |
| Documentation | 65 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 1,878; mean complexity 3.0, 90th percentile 6; 43 complex and 3 long functions
- Duplicated lines: 18.0% of 20,154 compared
- Tests: 65 test lines for 28,532 source lines (ratio 0.00); CI test commands: none detected; 3% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Most complex functions:
- _generateHTML in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js: complexity 90, 166 lines
- drag in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.draggable.js: complexity 44, 39 lines
- _doKeyDown in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js: complexity 43, 64 lines
- parseDate in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.datepicker.js: complexity 39, 92 lines
- _mouseDrag in HTML/external/jquery-ui/development-bundle/ui/jquery.ui.sortable.js: complexity 32, 57 lines
Security
Security posture is weak: 2 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 59 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/javascript.browser.security.insecure-document-method: User controlled data in methods like innerHTML, outerHTML or document.write is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
HTML/external/syntaxhighlighter_3.0.83/src/shCore.js:1648 |
| high | opengrep/javascript.browser.security.insecure-innerhtml: User controlled data in a div.innerHTML is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
HTML/external/syntaxhighlighter_3.0.83/src/shCore.js:1648 |
| medium | opengrep/javascript.lang.security.audit.prototype-pollution.prototype-pollution-assignment: Possibility of prototype polluting assignment detected. By adding or modifying attributes of an object prototype, it is possible to create attributes that exist on every object, or replace critical attributes with malicious ones. This can be problematic if the software depends on existence or non-ex [confidence low] |
HTML/client/shell.js:165 |
| 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] |
HTML/commandview/command.js:78 |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method: 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] |
HTML/commandview/command.js:80 |
| 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] |
HTML/commandview/commandcontext.js:34 |
| 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] |
HTML/commandview/commandcontext.js:35 |
| 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] |
HTML/commandview/commandview.js:70 |
| 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] |
HTML/commandview/commandview.js:70 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp: RegExp() called with a key function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled [confidence low] |
HTML/external/jquery-ui/development-bundle/external/jquery.cookie.js:88 |
| medium | opengrep/javascript.browser.security.eval-detected: Detected the use of eval(). eval() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by external sources. [confidence low] |
HTML/external/jquery-ui/development-bundle/external/jquery.metadata.js:101 |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method: 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.effects.core.js:243 |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method: 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.effects.core.js:251 |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method: 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.effects.core.js:477 |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method: 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.effects.core.js:586 |
| 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.effects.transfer.js:18 |
| 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.accordion.js:241 |
| 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.accordion.js:339 |
| 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.accordion.js:339 |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method: 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.accordion.js:467 |
| 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.autocomplete.js:147 |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method: 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.autocomplete.js:408 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp: RegExp() called with a $ function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled in [confidence low] |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.autocomplete.js:421 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp: RegExp() called with a term function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled [confidence low] |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.autocomplete.js:421 |
| 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] |
HTML/external/jquery-ui/development-bundle/ui/jquery.ui.autocomplete.js:459 |
Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.
Repository profile
- Source lines: 28,532; test lines: 65
| Language | Lines |
|---|---|
| JavaScript | 27,041 |
| PHP | 650 |
| Objective-C | 645 |
| C | 209 |
| Shell | 27 |
| Ruby | 25 |