Leaderboard github.com
fex-team/kityminder
百度脑图
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
49/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
54/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 pace0
- Coding-style index (1.0+ means possible)0.00
Lines added per month all AI-attributed share
- 2013-126,157 · 0% AI
- 2014-017,125 · 0% AI
- 2014-0219,622 · 0% AI
- 2014-0325,105 · 0% AI
- 2014-042,151 · 0% AI
- 2014-055,826 · 0% AI
- 2014-068,176 · 0% AI
- 2014-073,984 · 0% AI
- 2014-083,765 · 0% AI
- 2014-098,110 · 0% AI
- 2014-1031,824 · 0% AI
- 2014-1138,557 · 0% AI
- 2014-12148 · 0% AI
- 2015-014 · 0% AI
- 2015-0217 · 0% AI
- 2015-03463 · 0% AI
- 2015-04887 · 0% AI
- 2015-05221 · 0% AI
- 2015-080 · 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
- 1,553
- effective_loc
- 162,142
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 81,529
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 3,087.73
- measured_loc
- 80,613
- median_loc_per_hour
- 60.00
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 20,855
- pre_ai_era_bursts
- 5
- pre_ai_era_measured_loc
- 80,613
- work_units
- 675
Release velocityok
- flagged_releases
- 0
- max_loc_per_day
- 924.80
- releases
- 16
Coding styleok
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 0
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 0
- files:placeholder
- 0
- index
- 0
- lines_scanned
- 51,177
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 0
Code quality
49 poor
Code quality is poor: test-to-source ratio 0.08, no CI test run detected; 24% of function code in complex or long functions; 12% duplicated lines. Weakest area: process.
How the score is built
- Complexity48
- Duplication49
- Lint and smells96
- Tests and CI24
- Documentation85
- Type safetynot measured
- Review process5
Evidence by analyzer
Complexity (lizard)ok10 items
- smarty_function_html_select_time in native-support/archive/libs/plugins/function.html_select_time.php: complexity 134, 282 lines
- smarty_function_html_select_date in native-support/archive/libs/plugins/function.html_select_date.php: complexity 126, 275 lines
- Smarty_Internal_Utility::testInstall in native-support/archive/libs/sysplugins/smarty_internal_utility.php: complexity 91, 483 lines
- that.proc in lib/inflate.js: complexity 73, 413 lines
- that.proc in lib/inflate.js: complexity 58, 305 lines
- smarty_function_fetch in native-support/archive/libs/plugins/function.fetch.php: complexity 55, 175 lines
- getLostPoint in lib/qrcode.js: complexity 42, 10 lines
- KityMinder.browser in src/core/browser.js: complexity 38, 64 lines
- Smarty_Resource::buildFilepath in native-support/archive/libs/sysplugins/smarty_resource.php: complexity 37, 106 lines
- smarty_function_html_checkboxes in native-support/archive/libs/plugins/function.html_checkboxes.php: complexity 35, 106 lines
- complex_functions
- 45
- function_nloc
- 26,121
- functions
- 2,303
- long_functions
- 20
- many_param_functions
- 7
- mean_ccn
- 2.84
- p90_ccn
- 5
- risky_nloc_share
- 24.4%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: lib/inflate.js:2 and lib/zip.js:2
- 6+ duplicated lines: lib/inflate.js:495 and lib/inflate.js:1229
- 6+ duplicated lines: lib/qrcode.js:181 and lib/qrcode.js:234
- 6+ duplicated lines: native-support/archive/libs/Smarty.class.php:6 and native-support/archive/libs/SmartyBC.class.php:6
- 6+ duplicated lines: native-support/archive/libs/SmartyBC.class.php:5 and native-support/archive/libs/sysplugins/smarty_internal_utility.php:5
- 6+ duplicated lines: native-support/archive/libs/plugins/function.fetch.php:33 and native-support/archive/libs/plugins/function.html_image.php:99
- 6+ duplicated lines: native-support/archive/libs/plugins/function.html_checkboxes.php:54 and native-support/archive/libs/plugins/function.html_radios.php:54
- 6+ duplicated lines: native-support/archive/libs/plugins/function.html_checkboxes.php:85 and native-support/archive/libs/plugins/function.html_options.php:67
- 6+ duplicated lines: native-support/archive/libs/plugins/function.html_select_date.php:1 and native-support/archive/libs/plugins/function.html_select_time.php:1
- 6+ duplicated lines: native-support/archive/libs/plugins/modifier.escape.php:45 and native-support/archive/libs/plugins/modifier.escape.php:65
- compared_lines
- 34,277
- duplicated_lines
- 4,030
- duplicated_share
- 11.8%
- files
- 293
Lintok
- category:best-practice
- 6
- category:correctness
- 5
- findings
- 11
- scanned_lines
- 51,177
- weighted_findings
- 8
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
- 222
- cochange_share
- 0.0%
- source_lines
- 51,177
- test_lines
- 4,239
- test_ratio
- 0.08
Documentationok3 items
- README.md
README.md - LICENSE
LICENSE - CHANGELOG.md
CHANGELOG.md
- check:changelog
- yes
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 54
Type safetyskipped
Security
54 weak
Security posture is weak: 60 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets85
- Static analysis (SAST)59
- Vulnerable dependenciesnot measured
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecard18
Evidence by analyzer
OpenSSF Scorecardok10 items
- Scorecard Maintained: 0/10 (0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0)
- Scorecard Code-Review: 1/10 (Found 3/16 approved changesets -- score normalized to 1)
- Scorecard Binary-Artifacts: 9/10 (binaries present in source code)
- Scorecard CII-Best-Practices: 0/10 (no effort to earn an OpenSSF best practices badge detected)
- Scorecard Security-Policy: 0/10 (security policy file not detected)
- Scorecard License: 10/10 (license file detected)
- Scorecard Fuzzing: 0/10 (project is not fuzzed)
- Scorecard Signed-Releases: 0/10 (Project has not signed or included provenance with any releases.)
- Scorecard SAST: 0/10 (SAST tool is not run on all commits -- score normalized to 0)
- Scorecard Branch-Protection: 0/10 (branch protection not enabled on development/release branches)
- aggregate
- 1.70
- check:Binary-Artifacts
- yes
- check:Branch-Protection
- no
- check:CII-Best-Practices
- no
- check:Code-Review
- yes
- check:Fuzzing
- no
- check:License
- yes
- check:Maintained
- no
- check:SAST
- no
- check:Security-Policy
- no
- check:Signed-Releases
- no
Package registriesok
- checked
- 10
- declared
- 10
- lookup_errors
- 0
- missing
- 0
- recent
- 0
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 5
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 172
- findings_high
- 60
- findings_low
- 0
- findings_medium
- 112
- parse_errors
- 1
- scanned_lines
- 51,177
- weighted_findings
- 76.50
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok1 item
- package.json has no lockfile alongside it (unpinned dependencies)
package.json
- check:dependency_updates
- no
- check:lockfiles
- no
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 0.0%
- unpinned_manifests
- 1
Release downloadsok1 item
- binary_assets
- 1
- signals
- 1
- suspicious
- 0
Findings
60 high119 medium9 low
188 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/php.lang.security.injection.echoed-request |
download.php:37 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
lib/qrcode.js:253 | 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 |
lib/qrcode.js:253 | User controlled data in a `_el.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/Smarty.class.php:1313 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/SmartyBC.class.php:464 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/plugins/function.math.php:76 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/plugins/shared.literal_compiler_param.php:32 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_cacheresource_custom.php:144 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_cacheresource_custom.php:221 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_cacheresource_custom.php:88 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_cacheresource_keyvaluestore.php:106 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_cacheresource_keyvaluestore.php:200 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_cacheresource_file.php:175 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_cacheresource_file.php:61 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_compile_extends.php:59 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_compile_function.php:72 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_compile_include.php:164 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_compile_include.php:171 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_compile_include_php.php:63 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_compile_insert.php:63 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_compile_insert.php:75 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_config.php:105 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_function_call_handler.php:48 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_resource_eval.php:31 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_resource_extends.php:54 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_resource_file.php:35 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_resource_php.php:47 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_resource_registered.php:32 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_resource_string.php:31 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_template.php:241 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_template.php:271 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_template.php:691 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_templatebase.php:146 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_templatebase.php:157 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_templatebase.php:171 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
native-support/archive/libs/sysplugins/smarty_internal_templatebase.php:265 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_internal_utility.php:211 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/libs/sysplugins/smarty_resource_custom.php:51 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/src/Parser.freemind.class.php:94 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
native-support/archive/src/Parser.xmind.class.php:222 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
src/core/utils.js:76 | 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 |
src/core/utils.js:76 | User controlled data in a `node.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
src/core/utils.js:80 | 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 |
src/core/utils.js:80 | User controlled data in a `node.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
src/module/editor.receiver.js:328 | 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 |
src/module/editor.receiver.js:328 | User controlled data in a `this.container.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
ui/axss.js:12 | 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 |
ui/axss.js:12 | User controlled data in a `div.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
ui/ribbon/idea/image.js:143 | 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 |
ui/ribbon/idea/image.js:143 | User controlled data in a `$G('img_searchListUl').innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
ui/ribbon/idea/image.js:163 | 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 |
ui/ribbon/idea/image.js:163 | User controlled data in a `$G('img_searchListUl').innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
ui/ribbon/idea/image.js:180 | 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 |
ui/ribbon/idea/image.js:180 | User controlled data in a `title.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
ui/ribbon/idea/image.js:191 | 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 |
ui/ribbon/idea/image.js:191 | User controlled data in a `listUl.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
ui/ribbon/idea/image.js:50 | 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 |
ui/ribbon/idea/image.js:50 | User controlled data in a `tabs.getPanel(0).getContentElement().innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
ui/ribbon/idea/image.js:55 | 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 |
ui/ribbon/idea/image.js:55 | User controlled data in a `tabs.getPanel(1).getContentElement().innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
src/module/dropfile.js:25 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
src/module/dropfile.js:42 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
src/module/dropfile.js:57 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
ui/menu/share/share.js:369 | 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-confirm |
ui/topbar/title.js:43 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
ui/widget/netdiskfinder.js:123 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
ui/widget/netdiskfinder.js:374 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.security.audit.unknown-value-with-script-tag |
import.js:301 | Cannot determine what 'info' is and it is used with a '<script>' tag. This could be susceptible to cross-site scripting (XSS). Ensure 'info' is not externally controlled, or sanitize this data. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.injection.tainted-filename |
native-support/archive/libs/plugins/function.html_image.php:125 | File name based on user input risks server-side request forgery. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.injection.tainted-filename |
native-support/archive/libs/plugins/function.html_image.php:126 | File name based on user input risks server-side request forgery. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.injection.tainted-filename |
native-support/archive/libs/plugins/function.html_image.php:130 | File name based on user input risks server-side request forgery. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
native-support/archive/libs/sysplugins/smarty_internal_cacheresource_file.php:239 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
native-support/archive/libs/sysplugins/smarty_internal_cacheresource_file.php:292 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
native-support/archive/libs/sysplugins/smarty_internal_utility.php:272 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
native-support/archive/libs/sysplugins/smarty_internal_write_file.php:58 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
native-support/archive/libs/sysplugins/smarty_internal_write_file.php:66 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.injection.tainted-filename |
native-support/export.php:18 | File name based on user input risks server-side request forgery. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.injection.tainted-filename |
native-support/export.php:26 | File name based on user input risks server-side request forgery. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.injection.tainted-filename |
native-support/export.php:40 | File name based on user input risks server-side request forgery. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.injection.tainted-filename |
native-support/export.php:41 | File name based on user input risks server-side request forgery. [confidence medium] | Static analysis (opengrep) |
| medium | opengrep/php.lang.security.unlink-use |
native-support/export.php:41 | Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.prototype-pollution.prototype-pollution-loop |
src/core/lang.js:11 | Possibility of prototype polluting function 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... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
src/module/editor.range.js:38 | 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 |
src/module/editor.range.js:48 | 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/module/node.js:101 | 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.raw-html-join |
src/module/node.js:103 | User controlled data in a HTML string may result in XSS [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-method |
src/module/node.js:103 | 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/module/node.js:103 | 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/module/node.js:216 | 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.raw-html-join |
src/module/node.js:218 | User controlled data in a HTML string may result in XSS [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-method |
src/module/node.js:218 | 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/module/node.js:218 | 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/protocol/png.js:55 | 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/protocol/png.js:55 | 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/protocol/svg.js:42 | 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/protocol/svg.js:42 | 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/protocol/svg.js:44 | 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/protocol/svg.js:44 | 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 |
ui/contextmenu.js:31 | 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 |
ui/menu/help/feedback.js:11 | 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 |
ui/menu/help/feedback.js:25 | 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 |
ui/menu/help/help.js:11 | 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 |
ui/menu/help/help.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 |
ui/menu/help/help.js:39 | 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 |
ui/menu/new/new.js:41 | 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 |
ui/menu/open/draft.js:36 | 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 |
ui/menu/open/draft.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 |
ui/menu/open/local.js:130 | 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 |
ui/menu/open/local.js:134 | 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 |
ui/menu/open/local.js:29 | 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 |
ui/menu/open/local.js:52 | 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-method |
ui/menu/open/local.js:53 | 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 |
ui/menu/open/local.js:53 | 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 |
ui/menu/open/netdisk.js:21 | 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 |
ui/menu/open/netdisk.js:48 | 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 |
ui/menu/open/netdisk.js:82 | 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 |
ui/menu/open/recent.js:21 | 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 |
ui/menu/open/recent.js:47 | 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 |
ui/menu/save/download.js:14 | 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 |
ui/menu/save/download.js:42 | 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 |
ui/menu/save/netdisk.js:32 | 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 |
ui/menu/share/m-share.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 |
ui/menu/share/share.js:12 | 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 |
ui/menu/share/share.js:13 | 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 |
ui/menu/share/share.js:130 | 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 |
ui/menu/share/share.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-method |
ui/menu/share/share.js:223 | 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 |
ui/menu/share/share.js:223 | 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 |
ui/menu/share/share.js:233 | 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.lang.security.audit.unsafe-dynamic-method |
ui/menu/share/share.js:244 | 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 |
ui/menu/share/share.js:263 | 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 |
ui/menu/share/share.js:400 | 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 |
ui/menu/share/view.js:68 | 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 |
ui/ribbon/idea/image.js:113 | 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-redos |
ui/ribbon/idea/image.js:263 | Detected the use of a regular expression `^https?\:\/\/(\w+\.)+\w+` which appears to be vulnerable to a Regular expression Denial-of-Service (ReDoS). For this reason, it is recommended to review the regex and ensure it is not vulnerable... | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
ui/ribbon/idea/image.js:36 | 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 |
ui/ribbon/idea/image.js:43 | 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 |
ui/ribbon/idea/image.js:43 | 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 |
ui/ribbon/idea/link.js:37 | 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 |
ui/ribbon/idea/link.js:39 | 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 |
ui/ribbon/idea/link.js:39 | 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-redos |
ui/ribbon/idea/link.js:65 | Detected the use of a regular expression `(http|ftp|https):\/\/[\w\-_]+(\.[\w\-_]+)+([\w\-\.,@?^=%&:/~\+#]*[\w\-\@?^=%&/~\+#])?` which appears to be vulnerable to a Regular expression Denial-of-Service (ReDoS). For this reason,... | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
ui/ribbon/idea/link.js:88 | 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 |
ui/ribbon/idea/link.js:89 | 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 |
ui/ribbon/idea/note.js:103 | 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.prohibit-jquery-html |
ui/ribbon/idea/note.js:125 | 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 |
ui/ribbon/idea/note.js:86 | 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 |
ui/ribbon/idea/notepreview.js:51 | RegExp() called with a `keyword` 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 |
ui/ribbon/idea/notepreview.js:53 | 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 |
ui/ribbon/idea/notepreview.js:82 | 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 |
ui/ribbon/idea/resource.js:54 | 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 |
ui/ribbon/tabs.js:24 | 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.lang.security.audit.unsafe-dynamic-method |
ui/ribbon/view/select.js:102 | 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 |
ui/topbar/moreservice.js:14 | 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-method |
ui/topbar/quickvisit.js:37 | 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 |
ui/topbar/switch-view.js:142 | 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 |
ui/topbar/switch-view.js:147 | 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 |
ui/topbar/switch-view.js:158 | 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-method |
ui/topbar/switch-view.js:174 | 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-method |
ui/topbar/switch-view.js:27 | 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-method |
ui/topbar/switch-view.js:28 | 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-method |
ui/topbar/user.js:136 | 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 |
ui/topbar/user.js:136 | 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 |
ui/widget/fileloader.js:14 | 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 |
ui/widget/netdiskfinder.js:103 | 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 |
ui/widget/netdiskfinder.js:192 | 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 |
ui/widget/netdiskfinder.js:198 | 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 |
ui/widget/netdiskfinder.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 |
ui/widget/netdiskfinder.js:215 | 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 |
ui/widget/netdiskfinder.js:243 | 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 |
ui/widget/netdiskfinder.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 |
ui/widget/netdiskfinder.js:268 | 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 |
ui/widget/netdiskfinder.js:272 | 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 |
ui/widget/netdiskfinder.js:278 | 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 |
ui/widget/netdiskfinder.js:279 | 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 |
ui/widget/netdiskfinder.js:280 | 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 |
ui/widget/netdiskfinder.js:282 | 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 |
ui/widget/netdiskfinder.js:289 | 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 |
ui/widget/notice.js:114 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| low | opengrep/javascript.lang.correctness.useless-assignment |
lib/inflate.js:592 | `s.window[q++]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
src/module/editor.range.js:99 | `this.startContainer` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
src/protocol/svg.js:42 | `svgXml` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
ui/menu/share/share.js:448 | `shareConfig.bdText` is assigned twice; the first assignment is useless | Lint |
| low | gitleaks/generic-api-key |
dist/kityminder.all.js:24985 | Possible generic-api-key secret in history (commit 46e8984347); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
dist/kityminder.all.min.js:23 | Possible generic-api-key secret in history (commit f0a86d7d00); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
index.html:27 | Possible generic-api-key secret in the current tree | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
ui/fiox.js:16 | Possible generic-api-key secret in the current tree | Secrets (gitleaks) |
| low | gitleaks/generic-api-key |
ui/user.js:62 | Possible generic-api-key secret in history (commit f5e580268b); removed from the current tree but still retrievable | Secrets (gitleaks) |
Tools and coverage
Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.
| 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-4 | 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 | 11 | |
| 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 | ok | — | 0 | |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 172 | |
| OpenSSF Scorecard | Security | ok | scorecard v5.6.0 | 0 | |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 5 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | e74a4d668b0f | prov-5+qual-2+sec-2 | 0% | 49 | 54 |
| 2026-11-14 | e74a4d668b0f | prov-4+qual-2+sec-2 | 0% | 49 | 54 |
Full text report
- Repository: https://github.com/fex-team/kityminder
- Commit:
e74a4d668b0f1c194a3b13ccb5fc1c1f7bbd47a0 - Generated: 2026-11-14T14:52:04+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 | 49 | poor | 90% | 100% |
| Security | 54 | weak | 85% | 100% |
AI provenance
No AI attribution or AI-consistent velocity signals detected.
- Explicitly attributed share (lower bound): 0.0%
- Unattributed share in AI-consistent velocity bursts: 0.0%
- Estimated AI-generated share: 0.0%
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2014-06 | 8,176 | 0% |
| 2014-07 | 3,984 | 0% |
| 2014-08 | 3,765 | 0% |
| 2014-09 | 8,110 | 0% |
| 2014-10 | 31,824 | 0% |
| 2014-11 | 38,557 | 0% |
| 2014-12 | 148 | 0% |
| 2015-01 | 4 | 0% |
| 2015-02 | 17 | 0% |
| 2015-03 | 463 | 0% |
| 2015-04 | 887 | 0% |
| 2015-05 | 221 | 0% |
AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.
Code quality
Code quality is poor: test-to-source ratio 0.08, no CI test run detected; 24% of function code in complex or long functions; 12% duplicated lines. Weakest area: process.
| Area | Score |
|---|---|
| Complexity (lizard) | 48 |
| Duplication | 49 |
| Code smells (Opengrep) | 96 |
| Tests and CI | 24 |
| Documentation | 85 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | 5 |
- Functions: 2,303; mean complexity 2.8, 90th percentile 5; 45 complex and 20 long functions
- Duplicated lines: 11.8% of 34,277 compared
- Tests: 4,239 test lines for 51,177 source lines (ratio 0.08); CI test commands: none detected; 0% of recent source commits also change tests
- Docs missing or thin: contributing
Most complex functions:
- smarty_function_html_select_time in native-support/archive/libs/plugins/function.html_select_time.php: complexity 134, 282 lines
- smarty_function_html_select_date in native-support/archive/libs/plugins/function.html_select_date.php: complexity 126, 275 lines
- Smarty_Internal_Utility::testInstall in native-support/archive/libs/sysplugins/smarty_internal_utility.php: complexity 91, 483 lines
- that.proc in lib/inflate.js: complexity 73, 413 lines
- that.proc in lib/inflate.js: complexity 58, 305 lines
Security
Security posture is weak: 60 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 85 |
| Static analysis (Opengrep) | 59 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | 18 |
- Posture checks passed: none; missing: security policy, dependency updates, signed commits, lockfiles
- OpenSSF Scorecard aggregate: 1.7/10 (published 2026-11-09)
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
download.php:37 |
| 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] |
lib/qrcode.js:253 |
| high | opengrep/javascript.browser.security.insecure-innerhtml: User controlled data in a _el.innerHTML is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
lib/qrcode.js:253 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
native-support/archive/libs/Smarty.class.php:1313 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/SmartyBC.class.php:464 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/plugins/function.math.php:76 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/plugins/shared.literal_compiler_param.php:32 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
native-support/archive/libs/sysplugins/smarty_cacheresource_custom.php:88 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/sysplugins/smarty_cacheresource_custom.php:144 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
native-support/archive/libs/sysplugins/smarty_cacheresource_custom.php:221 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/sysplugins/smarty_cacheresource_keyvaluestore.php:106 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
native-support/archive/libs/sysplugins/smarty_cacheresource_keyvaluestore.php:200 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_cacheresource_file.php:61 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_cacheresource_file.php:175 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_compile_extends.php:59 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_compile_function.php:72 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_compile_include.php:164 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_compile_include.php:171 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_compile_include_php.php:63 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_compile_insert.php:63 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_compile_insert.php:75 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_config.php:105 |
| high | opengrep/php.lang.security.eval-use: Evaluating non-constant commands. This can lead to command injection. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_function_call_handler.php:48 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_resource_eval.php:31 |
| high | opengrep/php.lang.security.weak-crypto: Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] |
native-support/archive/libs/sysplugins/smarty_internal_resource_extends.php:54 |
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 v1.3.5 ships KityMinder-v1.3.5.zip (3143 downloads)
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: 51,177; test lines: 4,239
| Language | Lines |
|---|---|
| PHP | 28,725 |
| JavaScript | 26,691 |