Leaderboard github.com
brackets-userland/brackets-git
brackets-git — git extension for adobe/brackets
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
70/100
adequate
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
70/100
adequate
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
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.18
Lines added per month all AI-attributed share
- 2013-083,048 · 0% AI
- 2013-091,649 · 0% AI
- 2013-10239 · 0% AI
- 2013-1169 · 0% AI
- 2013-12670 · 0% AI
- 2014-01674 · 0% AI
- 2014-021,553 · 0% AI
- 2014-0310,312 · 0% AI
- 2014-049,840 · 0% AI
- 2014-05244 · 0% AI
- 2014-06115 · 0% AI
- 2014-07491 · 0% AI
- 2014-08220 · 0% AI
- 2014-091,039 · 0% AI
- 2014-10398 · 0% AI
- 2014-11145 · 0% AI
- 2014-12472 · 0% AI
- 2015-011 · 0% AI
- 2015-02116 · 0% AI
- 2015-03747 · 0% AI
- 2015-04139 · 0% AI
- 2015-0521 · 0% AI
- 2015-070 · 0% AI
- 2015-0881 · 0% AI
- 2015-090 · 0% AI
- 2015-12113 · 0% AI
- 2016-01228 · 0% AI
- 2016-021 · 0% AI
- 2016-032 · 0% AI
- 2016-042 · 0% AI
- 2016-05169 · 0% AI
- 2016-088 · 0% AI
- 2016-097,488 · 0% AI
- 2016-10447 · 0% AI
- 2016-11833 · 0% AI
- 2016-12396 · 0% AI
- 2017-01631 · 0% AI
- 2017-07242 · 0% AI
- 2018-011 · 0% AI
- 2018-040 · 0% AI
- 2018-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,319
- effective_loc
- 42,844
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 2,267
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 932.25
- measured_loc
- 40,577
- median_loc_per_hour
- 70.50
- pr_timed_units
- 1
- pre_ai_era_burst_loc
- 7,906
- pre_ai_era_bursts
- 3
- pre_ai_era_measured_loc
- 40,577
- work_units
- 619
Release velocityok
- flagged_releases
- 0
- max_loc_per_day
- 1.40
- releases
- 2
Coding styleok2 items
- step-by-step narration comment: // now we launch a diff to fill the gutters in our editors
- step-by-step narration comment: // now we are going to be paranoid and we will check if some mofo didn't change our diff
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 2
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 2
- files:placeholder
- 0
- index
- 0.18
- lines_scanned
- 10,886
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0.18
- per_kloc:placeholder
- 0
Code quality
70 adequate
Code quality is adequate: test-to-source ratio 0.00, no CI test run detected; 4% of function code in complex or long functions; 1% duplicated lines. Weakest area: testing.
How the score is built
- Complexity90
- Duplication94
- Lint and smells99
- Tests and CI15
- Documentation100
- Type safety40
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok4 items
- handleToggleHistory in src/History.ts: complexity 21, 50 lines
- (anonymous) in src/Utils.ts: complexity 21, 85 lines
- (anonymous) in src/git/GitCli.ts: complexity 21, 69 lines
- (anonymous) in src/git/Git.ts: complexity 19, 31 lines
- complex_functions
- 4
- function_nloc
- 6,597
- functions
- 1,014
- long_functions
- 0
- many_param_functions
- 0
- mean_ccn
- 1.80
- p90_ccn
- 3
- risky_nloc_share
- 3.6%
Duplication (jscpd)ok5 items
- 6+ duplicated lines: src/History.ts:84 and src/History.ts:137
- 6+ duplicated lines: src/dialogs/Pull.ts:29 and src/dialogs/Push.ts:28
- 6+ duplicated lines: src/git/GitCli.ts:1016 and src/git/GitCli.ts:1032
- 6+ duplicated lines: src/node/cli.ts:226 and src/node/cli.ts:243
- 6+ duplicated lines: src/node/process-utils.ts:49 and src/node/process-utils.ts:64
- compared_lines
- 7,998
- duplicated_lines
- 84
- duplicated_share
- 1.1%
- files
- 58
Lintok
- category:best-practice
- 2
- findings
- 2
- scanned_lines
- 10,886
- weighted_findings
- 0.50
Tests and CIok1 item
- CI config: .travis.yml
.travis.yml
- check:ci_present
- yes
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- no
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 1
- cochange_commits
- 181
- cochange_share
- 0.0%
- source_lines
- 10,886
- test_lines
- 0
- test_ratio
- 0
Documentationok4 items
- README.md
README.md - LICENSE
LICENSE - CONTRIBUTING.md
CONTRIBUTING.md - CHANGELOG.md
CHANGELOG.md
- check:changelog
- yes
- check:contributing
- yes
- check:license
- yes
- check:readme
- yes
- readme_lines
- 82
Type safetyok
- check:low_escape_density
- yes
- check:strict_config
- no
- escapes
- 11
- escapes_per_kloc
- 1.36
Security
70 adequate
Security posture is adequate: 5 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets100
- Static analysis (SAST)68
- 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 registriesok
- checked
- 29
- declared
- 29
- lookup_errors
- 0
- missing
- 0
- recent
- 0
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 37
- findings_high
- 5
- findings_low
- 0
- findings_medium
- 32
- parse_errors
- 0
- scanned_lines
- 10,886
- weighted_findings
- 11.75
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok2 items
- package.json has no lockfile alongside it (unpinned dependencies)
package.json - src/node/package.json has no lockfile alongside it (unpinned dependencies)
src/node/package.json
- check:dependency_updates
- no
- check:lockfiles
- no
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 2.0%
- unpinned_manifests
- 2
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
5 high32 medium2 low
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/javascript.lang.security.detect-child-process |
src/node/cli.ts:40 | Detected calls to child_process from a function argument `args`. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized... | Static analysis (opengrep) |
| high | opengrep/javascript.lang.security.detect-child-process |
src/node/cli.ts:40 | Detected calls to child_process from a function argument `command`. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly... | Static analysis (opengrep) |
| high | opengrep/javascript.lang.security.detect-child-process |
src/node/cli.ts:70 | Detected calls to child_process from a function argument `command`. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly... | Static analysis (opengrep) |
| high | opengrep/javascript.lang.security.detect-child-process |
src/node/process-utils.ts:32 | Detected calls to child_process from a function argument `pid`. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized... | Static analysis (opengrep) |
| high | opengrep/javascript.lang.security.detect-child-process |
src/node/process-utils.ts:37 | Detected calls to child_process from a function argument `pid`. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
nls/generate.js:18 | Detected that function argument `lang` 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 |
nls/generate.js:58 | Detected that function argument `lang` 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.jquery.security.audit.prohibit-jquery-html |
src/Branch.ts:144 | 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/Branch.ts:336 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-method |
src/ChangelogDialog.ts:19 | 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/ChangelogDialog.ts:19 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
src/Cli.ts:168 | 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 |
src/HistoryViewer.ts:52 | 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/Panel.ts:1144 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
src/Panel.ts:957 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
src/Panel.ts:961 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
src/Panel.ts:965 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
src/Panel.ts:968 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
src/Panel.ts:977 | 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-regexp |
src/ProjectTreeMarks.ts:87 | RegExp() called with a `_line` 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 |
src/Remotes.ts:312 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector |
src/Remotes.ts:322 | User controlled data in a `$(...)` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
src/Remotes.ts: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.lang.security.audit.unsafe-dynamic-method |
src/Utils.ts:339 | 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 |
src/dialogs/RemoteCommon.ts:15 | JQuery's `html` function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider `text` instead. Otherwise, use a function that escapes HTML such as edX's `HtmlUtils.setHtml()`. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html |
src/ftp/Ftp.ts:131 | 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-fs-filename |
src/node/cli.ts: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 |
src/node/process-utils.ts:89 | 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.express.security.audit.xss.mustache.template-explicit-unescape |
templates/format-diff.html:11 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
templates/git-diff-dialog.html:3 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
templates/git-output.html:8 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
templates/git-question-dialog.html:6 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
templates/git-settings-dialog.html:138 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
templates/git-settings-dialog.html:163 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
templates/git-settings-dialog.html:230 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
templates/git-settings-dialog.html:240 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| medium | opengrep/javascript.express.security.audit.xss.mustache.template-explicit-unescape |
templates/history-viewer.html:53 | Detected an explicit unescape in a Mustache template, using triple braces '{{{...}}}' or ampersand '&'. If external data can reach these locations, your application is exposed to a cross-site scripting (XSS) vulnerability. If you must... | Static analysis (opengrep) |
| low | opengrep/typescript.lang.best-practice.moment-deprecated |
src/History.ts:3 | Moment is a legacy project in maintenance mode. Consider using libraries that are actively supported, e.g. `dayjs`. | Lint |
| low | opengrep/typescript.lang.best-practice.moment-deprecated |
src/Panel.ts:8 | Moment is a legacy project in maintenance mode. Consider using libraries that are actively supported, e.g. `dayjs`. | 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 | 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 | 2 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | ok | — | 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 | 37 | |
| 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 | 334b702d2a35 | prov-5+qual-2+sec-2 | 0% | 70 | 70 |
| 2026-11-14 | 334b702d2a35 | prov-4+qual-2+sec-2 | 0% | 70 | 70 |
Full text report
- Repository: https://github.com/brackets-userland/brackets-git
- Commit:
334b702d2a35f62a2a863b9aaa25d1bec95c7ed7 - Generated: 2026-11-14T14:52:03+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 | 70 | adequate | 90% | 100% |
| Security | 70 | adequate | 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.18 per 1,000 lines (narrated steps 2, placeholders 0, assistant phrasing 0, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2016-02 | 1 | 0% |
| 2016-03 | 2 | 0% |
| 2016-04 | 2 | 0% |
| 2016-05 | 169 | 0% |
| 2016-08 | 8 | 0% |
| 2016-09 | 7,488 | 0% |
| 2016-10 | 447 | 0% |
| 2016-11 | 833 | 0% |
| 2016-12 | 396 | 0% |
| 2017-01 | 631 | 0% |
| 2017-07 | 242 | 0% |
| 2018-01 | 1 | 0% |
Evidence
- step-by-step narration comment: // now we launch a diff to fill the gutters in our editors (src/GutterMa)
- step-by-step narration comment: // now we are going to be paranoid and we will check if some mofo didn't change our diff (src/Panel.ts)
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 adequate: test-to-source ratio 0.00, no CI test run detected; 4% of function code in complex or long functions; 1% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 90 |
| Duplication | 94 |
| Code smells (Opengrep) | 99 |
| Tests and CI | 15 |
| Documentation | 100 |
| Type safety | 40 |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 1,014; mean complexity 1.8, 90th percentile 3; 4 complex and 0 long functions
- Duplicated lines: 1.1% of 7,998 compared
- Tests: 0 test lines for 10,886 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
- Docs missing or thin: none
Most complex functions:
- handleToggleHistory in src/History.ts: complexity 21, 50 lines
- (anonymous) in src/Utils.ts: complexity 21, 85 lines
- (anonymous) in src/git/GitCli.ts: complexity 21, 69 lines
- (anonymous) in src/git/Git.ts: complexity 19, 31 lines
Security
Security posture is adequate: 5 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 68 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: none; missing: security policy, dependency updates, signed commits, lockfiles
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/javascript.lang.security.detect-child-process: Detected calls to child_process from a function argument args. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized or sandboxed. [confidence low] |
src/node/cli.ts:40 |
| high | opengrep/javascript.lang.security.detect-child-process: Detected calls to child_process from a function argument command. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized or sandboxed. [confidence low] |
src/node/cli.ts:40 |
| high | opengrep/javascript.lang.security.detect-child-process: Detected calls to child_process from a function argument command. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized or sandboxed. [confidence low] |
src/node/cli.ts:70 |
| high | opengrep/javascript.lang.security.detect-child-process: Detected calls to child_process from a function argument pid. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized or sandboxed. [confidence low] |
src/node/process-utils.ts:32 |
| high | opengrep/javascript.lang.security.detect-child-process: Detected calls to child_process from a function argument pid. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized or sandboxed. [confidence low] |
src/node/process-utils.ts:37 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename: Detected that function argument lang 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 variables in file paths are validated. [confidence low] |
nls/generate.js:18 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename: Detected that function argument lang 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 variables in file paths are validated. [confidence low] |
nls/generate.js:58 |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html: JQuery's html function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider text instead. Otherwise, use a function that escapes HTML such as edX's HtmlUtils.setHtml(). [confidence low] |
src/Branch.ts:144 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector: User controlled data in a $(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
src/Branch.ts:336 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-method: User controlled data in a jQuery's .html(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
src/ChangelogDialog.ts:19 |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html: JQuery's html function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider text instead. Otherwise, use a function that escapes HTML such as edX's HtmlUtils.setHtml(). [confidence low] |
src/ChangelogDialog.ts:19 |
| 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] |
src/Cli.ts:168 |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html: JQuery's html function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider text instead. Otherwise, use a function that escapes HTML such as edX's HtmlUtils.setHtml(). [confidence low] |
src/HistoryViewer.ts:52 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector: User controlled data in a $(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
src/Panel.ts:957 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector: User controlled data in a $(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
src/Panel.ts:961 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector: User controlled data in a $(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
src/Panel.ts:965 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector: User controlled data in a $(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
src/Panel.ts:968 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector: User controlled data in a $(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
src/Panel.ts:977 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector: User controlled data in a $(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
src/Panel.ts:1144 |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp: RegExp() called with a _line 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-controlle [confidence low] |
src/ProjectTreeMarks.ts:87 |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html: JQuery's html function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider text instead. Otherwise, use a function that escapes HTML such as edX's HtmlUtils.setHtml(). [confidence low] |
src/Remotes.ts:96 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector: User controlled data in a $(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
src/Remotes.ts:312 |
| medium | opengrep/javascript.jquery.security.audit.jquery-insecure-selector: User controlled data in a $(...) is an anti-pattern that can lead to XSS vulnerabilities [confidence low] |
src/Remotes.ts:322 |
| 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] |
src/Utils.ts:339 |
| medium | opengrep/javascript.jquery.security.audit.prohibit-jquery-html: JQuery's html function is susceptible to Cross Site Scripting (XSS) attacks. If you're just passing text, consider text instead. Otherwise, use a function that escapes HTML such as edX's HtmlUtils.setHtml(). [confidence low] |
src/dialogs/RemoteCommon.ts:15 |
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: 10,886; test lines: 0
| Language | Lines |
|---|---|
| TypeScript | 8,058 |
| JavaScript | 2,814 |
| Shell | 14 |