Repository Analysis

electerm/electerm

📻Terminal/ssh/sftp/ftp/telnet/serialport/RDP/VNC/Spice client(linux, mac, win)

4.1 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of electerm/electerm, a JavaScript project with 14,482 GitHub stars. SynthScan v2.0 examined 107,839 lines of code across 711 source files, recording 199 pattern matches distributed across 7 syntactic categories. The overall adjusted score of 4.1 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

4.1
Adjusted Score
4.1
Raw Score
100%
Time Factor
2026-07-13
Last Push
14.5K
Stars
JavaScript
Language
107.8K
Lines of Code
711
Files
199
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 0MEDIUM 94LOW 105

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 199 distinct pattern matches across 7 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Decorative Section Separators94 hits · 291 pts
SeverityFileLineSnippetContext
MEDIUMtest/unit/resolve.spec.js13 // ── Unix paths ──────────────────────────────────────────────COMMENT
MEDIUMtest/unit/resolve.spec.js39 // ── Windows paths ───────────────────────────────────────────COMMENT
MEDIUMtest/unit/resolve.spec.js69 // ── Absolute paths in nameOrDot ─────────────────────────────COMMENT
MEDIUMtest/unit/resolve.spec.js91 // ── Edge cases ──────────────────────────────────────────────COMMENT
MEDIUMtest/unit/resolve.spec.js101 // ── WSL paths (wsl.localhost) ───────────────────────────────COMMENT
MEDIUMtest/unit/resolve.spec.js135 // ── WSL paths (wsl$) ───────────────────────────────────────COMMENT
MEDIUMtest/unit/resolve.spec.js145 // ── WSL cross-path switching ────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js17// ── Electron mock ─────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js29// ── Mock renderer (win) ───────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js48// ── Intercept require() before loading the widget ─────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js64// ── SSE helper (mirrors mcp.spec.js) ─────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js101// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js103// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js136// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js138// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js183// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js185// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js216// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js218// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js262// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js264// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js352// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js354// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js421// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js423// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js457// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js459// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js502// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js504// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js590// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp-widget.spec.js592// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp.spec.js238 // ─── Renderer-dependent terminal tests ──────────────────────────────────COMMENT
MEDIUMtest/unit/mcp.spec.js101 // ─── Protocol-level tests (no renderer needed) ──────────────────────────COMMENT
MEDIUMtest/unit/mcp.spec.js202 // ─── Tool call protocol tests ───────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp.spec.js418 // ─── Direct tab open tests ─────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp.spec.js527 // ─── onData test ────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit/mcp.spec.js544 // ─── Terminal idle tests ────────────────────────────────────────────────COMMENT
MEDIUMtest/unit-ci/session-ssh-agent.spec.js39// ─── constants ────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit-ci/session-ssh-agent.spec.js48// ─── helpers ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit-ci/session-ssh-agent.spec.js227// ─── fixture management ────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit-ci/session-ssh-agent.spec.js265 // ── test 1 ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit-ci/session-ssh-agent.spec.js327 // ── test 2 ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit-ci/session-ssh-agent.spec.js377 // ── test 3 ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/unit-ci/session-ssh-agent.spec.js424 // ── test 4 ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/e2e/023.batch-op.spec.js25// ─── helpers ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/e2e/023.batch-op.spec.js61// ─── tests ────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/e2e/023.batch-op.spec.js73 // ── open widgets panel ─────────────────────────────────────────────────COMMENT
MEDIUMtest/e2e/023.batch-op.spec.js77 // ── click the Batch Operation widget ──────────────────────────────────COMMENT
MEDIUMtest/e2e/023.batch-op.spec.js89 // ── Load Template and verify editor populated ──────────────────────────COMMENT
MEDIUMtest/e2e/023.batch-op.spec.js99 // ── set the full example workflow (connect + commands + sftp) ──────────COMMENT
MEDIUMtest/e2e/023.batch-op.spec.js103 // ── execute workflow ───────────────────────────────────────────────────COMMENT
MEDIUMtest/e2e/021.cmd-history.spec.js23// ─── helpers ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/e2e/021.cmd-history.spec.js92// ─── test ─────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtest/e2e/021.cmd-history.spec.js96 // ── first session ──────────────────────────────────────────────────────────COMMENT
MEDIUMtest/e2e/021.cmd-history.spec.js112 // ── step 1: run cmd1 in terminal → should appear in history ───────────────COMMENT
MEDIUMtest/e2e/021.cmd-history.spec.js127 // ── step 2: click the item to re-run the command ──────────────────────────COMMENT
MEDIUMtest/e2e/021.cmd-history.spec.js147 // ── step 3: delete the item ────────────────────────────────────────────────COMMENT
MEDIUMtest/e2e/021.cmd-history.spec.js157 // ── step 4: run cmd2 that should persist after restart ────────────────────COMMENT
MEDIUMtest/e2e/021.cmd-history.spec.js165 // ── second session (restart) ───────────────────────────────────────────────COMMENT
MEDIUMtest/e2e/020.trzsz-rzsz.spec.js34// ─── helpers ──────────────────────────────────────────────────────────────────COMMENT
34 more matches not shown…
Verbosity Indicators34 hits · 56 pts
SeverityFileLineSnippetContext
LOWtest/unit/mcp2.spec.js320 // Step 1: Create SSH bookmarkCOMMENT
LOWtest/unit/mcp2.spec.js334 // Step 2: Open the bookmarkCOMMENT
LOWtest/unit/mcp2.spec.js341 // Step 3: List /tmp directoryCOMMENT
LOWtest/unit/mcp2.spec.js352 // Step 4: Stat /tmpCOMMENT
LOWtest/unit/mcp2.spec.js362 // Step 5: Read /etc/hostnameCOMMENT
LOWtest/unit/mcp2.spec.js372 // Step 6: Clean up - delete test bookmarkCOMMENT
LOWtest/unit/mcp.spec.js243 // Step 1: Open a local terminalCOMMENT
LOWtest/unit/mcp.spec.js253 // Step 2: Send a commandCOMMENT
LOWtest/unit/mcp.spec.js370 // Step 5: Clean up - delete the test bookmarkCOMMENT
LOWtest/unit/mcp.spec.js379 // Step 6: Verify the bookmark was actually deletedCOMMENT
LOWtest/unit/mcp.spec.js487 // Step 4: Verify no bookmark was created for this connectionCOMMENT
LOWtest/unit/mcp.spec.js494 // Step 5: Close the tabCOMMENT
LOWtest/unit/mcp.spec.js267 // Step 3: Get terminal output and verify command was executedCOMMENT
LOWtest/unit/mcp.spec.js307 // Step 1: Create SSH bookmarkCOMMENT
LOWtest/unit/mcp.spec.js322 // Step 2: Open/connect to the bookmarkCOMMENT
LOWtest/unit/mcp.spec.js333 // Step 3: Send a command with retryCOMMENT
LOWtest/unit/mcp.spec.js357 // Step 4: Get terminal output and verify command was executedCOMMENT
LOWtest/unit/mcp.spec.js433 // Step 1: Open SSH tab directly (no bookmark created)COMMENT
LOWtest/unit/mcp.spec.js451 // Step 2: Send a command with retryCOMMENT
LOWtest/unit/mcp.spec.js475 // Step 3: Get terminal output and verify command was executedCOMMENT
LOWnpm/install.js303 // Step 1: Mount the DMGCOMMENT
LOWnpm/install.js321 // Step 2: Find the .app bundleCOMMENT
LOWnpm/install.js343 // Step 3: Copy the app to /ApplicationsCOMMENT
LOWnpm/install.js346 // Step 4: Detach the DMG (always, regardless of copy result)COMMENT
LOWsrc/app/server/rdp-proxy.js617 // Step 1: Parse RDCleanPath requestCOMMENT
LOWsrc/app/server/rdp-proxy.js621 // Step 2: Parse destinationCOMMENT
LOWsrc/app/server/rdp-proxy.js633 // Step 6: Build and send RDCleanPath responseCOMMENT
LOWsrc/app/server/rdp-proxy.js641 // Step 7: Bidirectional relay via node-forgeCOMMENT
LOWsrc/app/server/rdp-proxy.js379 // Step 1: TCP connect (direct or through proxy)COMMENT
LOWsrc/app/server/rdp-proxy.js401 // Step 3: Read X.224 Connection ConfirmCOMMENT
LOWsrc/app/server/rdp-proxy.js415 // Step 4: TLS handshake via node-forge (pure JS — no BoringSSL)COMMENT
LOWsrc/app/server/rdp-proxy.js435 // Step 5: Convert captured certificates to DERCOMMENT
LOWsrc/client/components/file-transfer/transfer.jsx707 // Step 1: Create all folders concurrently in batchesCOMMENT
LOWsrc/client/components/file-transfer/transfer.jsx731 // Step 2: Process contents of each folder sequentiallyCOMMENT
Structural Annotation Overuse34 hits · 56 pts
SeverityFileLineSnippetContext
LOWtest/unit/mcp2.spec.js320 // Step 1: Create SSH bookmarkCOMMENT
LOWtest/unit/mcp2.spec.js334 // Step 2: Open the bookmarkCOMMENT
LOWtest/unit/mcp2.spec.js341 // Step 3: List /tmp directoryCOMMENT
LOWtest/unit/mcp2.spec.js352 // Step 4: Stat /tmpCOMMENT
LOWtest/unit/mcp2.spec.js362 // Step 5: Read /etc/hostnameCOMMENT
LOWtest/unit/mcp2.spec.js372 // Step 6: Clean up - delete test bookmarkCOMMENT
LOWtest/unit/mcp.spec.js243 // Step 1: Open a local terminalCOMMENT
LOWtest/unit/mcp.spec.js253 // Step 2: Send a commandCOMMENT
LOWtest/unit/mcp.spec.js370 // Step 5: Clean up - delete the test bookmarkCOMMENT
LOWtest/unit/mcp.spec.js379 // Step 6: Verify the bookmark was actually deletedCOMMENT
LOWtest/unit/mcp.spec.js487 // Step 4: Verify no bookmark was created for this connectionCOMMENT
LOWtest/unit/mcp.spec.js494 // Step 5: Close the tabCOMMENT
LOWtest/unit/mcp.spec.js267 // Step 3: Get terminal output and verify command was executedCOMMENT
LOWtest/unit/mcp.spec.js307 // Step 1: Create SSH bookmarkCOMMENT
LOWtest/unit/mcp.spec.js322 // Step 2: Open/connect to the bookmarkCOMMENT
LOWtest/unit/mcp.spec.js333 // Step 3: Send a command with retryCOMMENT
LOWtest/unit/mcp.spec.js357 // Step 4: Get terminal output and verify command was executedCOMMENT
LOWtest/unit/mcp.spec.js433 // Step 1: Open SSH tab directly (no bookmark created)COMMENT
LOWtest/unit/mcp.spec.js451 // Step 2: Send a command with retryCOMMENT
LOWtest/unit/mcp.spec.js475 // Step 3: Get terminal output and verify command was executedCOMMENT
LOWnpm/install.js303 // Step 1: Mount the DMGCOMMENT
LOWnpm/install.js321 // Step 2: Find the .app bundleCOMMENT
LOWnpm/install.js343 // Step 3: Copy the app to /ApplicationsCOMMENT
LOWnpm/install.js346 // Step 4: Detach the DMG (always, regardless of copy result)COMMENT
LOWsrc/app/server/rdp-proxy.js617 // Step 1: Parse RDCleanPath requestCOMMENT
LOWsrc/app/server/rdp-proxy.js621 // Step 2: Parse destinationCOMMENT
LOWsrc/app/server/rdp-proxy.js633 // Step 6: Build and send RDCleanPath responseCOMMENT
LOWsrc/app/server/rdp-proxy.js641 // Step 7: Bidirectional relay via node-forgeCOMMENT
LOWsrc/app/server/rdp-proxy.js379 // Step 1: TCP connect (direct or through proxy)COMMENT
LOWsrc/app/server/rdp-proxy.js401 // Step 3: Read X.224 Connection ConfirmCOMMENT
LOWsrc/app/server/rdp-proxy.js415 // Step 4: TLS handshake via node-forge (pure JS — no BoringSSL)COMMENT
LOWsrc/app/server/rdp-proxy.js435 // Step 5: Convert captured certificates to DERCOMMENT
LOWsrc/client/components/file-transfer/transfer.jsx707 // Step 1: Create all folders concurrently in batchesCOMMENT
LOWsrc/client/components/file-transfer/transfer.jsx731 // Step 2: Process contents of each folder sequentiallyCOMMENT
Hyper-Verbose Identifiers20 hits · 20 pts
SeverityFileLineSnippetContext
LOWtest/unit-ci/session-ssh.spec.js184function sameRoundKeyboardInteractiveAuth () {CODE
LOWtest/unit-ci/session-ssh.spec.js205function splitRoundKeyboardInteractiveAuth (rounds = []) {CODE
LOWtest/e2e/019.drag-folder.spec.js166async function ensureItemVisibleAtCurrentOrParent (client, type, itemName, maxHops = 8) {CODE
LOWtest/e2e/009.8.file-op-with-keyboard.spec.js38async function testCopyPasteOperationWithKeyboard (client, type) {CODE
LOWtest/e2e/common/common.js241async function confirmSshHostKeyVerificationIfNeeded (client, timeout = 4000) {CODE
LOWtest/e2e/common/common.js408async function verifyFileTransfersComplete (client, timeout = 30000, interval = 1000) {CODE
LOWsrc/app/server/sftp-file.js7function createReadStreamFromString (str) {CODE
LOWsrc/app/server/session-api.js38async function toggleTerminalLogTimestamp (body) {CODE
LOWsrc/app/server/terminal-api.js44function toggleTerminalLogTimestamp (ws, msg) {CODE
LOWsrc/app/lib/deep-link.js62function checkProtocolRegistration () {CODE
LOWsrc/client/components/terminal/shell.js107export function getInlineShellIntegration (shellType) {CODE
LOWsrc/client/components/terminal/shell.js141export function getShellIntegrationCommand (shellType = 'bash') {CODE
LOWsrc/client/components/terminal/terminal-apis.js38export function toggleTerminalLogTimestamp (pid) {CODE
LOW…/client/components/bookmark-form/common/init-values.js68export function getTerminalBackgroundDefaults (defaultSetting) {CODE
LOW…/components/common/connection-hopping-warning-text.jsx13export default function ConnectionHoppingWarningText (props) {CODE
LOWsrc/client/components/theme/theme-list-item.jsx51 function handleTooltipVisibleChange (visible) {CODE
LOWsrc/client/components/ai/agent-tools.js4function buildAddBookmarkParameters () {CODE
LOWsrc/client/components/ai/agent.js35async function callBackendAIchatWithTools (messages, config) {CODE
LOWsrc/client/components/shortcuts/shortcut-handler.js67export function handleTerminalSelectionReplace (event, ctx) {CODE
LOWsrc/client/store/sync.js37function updateSyncServerStatusFromGist (store, gist, type) {CODE
Over-Commented Block14 hits · 14 pts
SeverityFileLineSnippetContext
LOWtest/e2e/018.file-transfer-conflict.spec.js201 // Count and return the number of selected itemsCOMMENT
LOW.github/workflows/linux-loong64-legacy.yml1# Build electerm for loong64 (LoongArch64) Linux - Legacy (old world)COMMENT
LOWsrc/app/server/download-upgrade.js61 proxy,COMMENT
LOWsrc/app/lib/on-close.js41 // _id: 'exitStatus'COMMENT
LOWsrc/app/widgets/widget-local-file-server.js61 },COMMENT
LOWsrc/app/widgets/load-widget.js41 return resCOMMENT
LOWsrc/client/components/tabs/tab.jsx81 clearPasswordPrompt = () => {COMMENT
LOWsrc/client/components/web/web-session.jsx81 // webview.addEventListener('did-start-loading', (e) => {COMMENT
LOWsrc/client/components/terminal/terminal.jsx1781 // getPwd = async () => {COMMENT
LOWsrc/client/store/sync.js121 // }COMMENT
LOWsrc/client/store/sync.js601 if (pass) {COMMENT
LOWsrc/client/store/mcp-handler.js321 message: `Bookmark group "${group.title}" created`COMMENT
LOWsrc/client/store/mcp-handler.js341 // store.addQuickCommand(qm)COMMENT
LOWsrc/client/store/mcp-handler.js361 // message: `Executed quick command "${qm.name}"`COMMENT
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWsrc/client/components/common/placeholder.jsx3 <div id='placeholder' className='placeholder-wrap' />CODE
LOWsrc/client/store/sync.js120 // content: 'placeholder'COMMENT
Overly Generic Function Names1 hit · 1 pts
SeverityFileLineSnippetContext
LOWsrc/client/common/db.js148export async function getData (name) {CODE