Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo

TerriFlux/opensankey

https://github.com/TerriFlux/opensankey · scanned 2026-06-16 00:32 UTC (2 months, 2 weeks ago)

227 raw signals (0 security + 227 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 221 actionable findings from 1 signal source. 6 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
60.0
/100
Security checks
60
0 findings
System graph
60
88.9% cov · 221 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 3 Medium 16 Low 112 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 221 Crowd 0 Layer: Software 19 Frontend 26 Hardware 3 Security 8 Cicd 2 Quality 139 Api 24
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 60.0/100 with 88.9% coverage. It contains 1516 nodes across 23 cross-layer flows, written primarily in mixed languages. Engine surfaced 227 findings — concentrated in quality (145), frontend (26), api (24). Risk profile is high: 0 critical, 3 high, 16 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 131 of 221 actionable findings. 227 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: POST /example/upload (opensankey/client/src/Persistence/UniversalJSONCompression.tsx:217)
`opensankey/client/src/Persistence/UniversalJSONCompression.tsx:217` calls `POST /example/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/example/upload` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /opensankey/menus/excel_template (opensankey/client/src/components/topmenus/ExcelTemplateModal.tsx:146)
`opensankey/client/src/components/topmenus/ExcelTemplateModal.tsx:146` calls `POST /opensankey/menus/excel_template` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/opensankey/menus/excel_template` If this points at …
Dangling fetchFetch
high System graph hardware Supply chain conf 1.00 Dockerfile pipes a remote installer into a shell
Executing downloaded code during image build gives the remote endpoint build-time code execution. Prefer pinned packages or verify downloaded installers by checksum/signature.
Dockerfile:7 containersRemote installer
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — opensankey/client/src/components/dialogs/PersistenceProcessDialog.tsx:561
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — opensankey/client/src/components/dialogs/PersistenceProcessDialogTerminal.tsx:328
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — opensankey/client/src/components/topmenus/SankeyTemplates.tsx:108
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — opensankey/client/src/registerServiceWorker.js:86
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — opensankey/client/src/types/ApplicationData.tsx:882
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in opensankey/client/src/Elements/Legend.tsx:313
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
opensankey/client/src/Elements/Legend.tsx:313 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in opensankey/client/src/Elements/TooltipsCSS.tsx:43
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
opensankey/client/src/Elements/TooltipsCSS.tsx:43 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in opensankey/client/src/Persistence/SankeyPersistence.tsx:447
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
opensankey/client/src/Persistence/SankeyPersistence.tsx:447 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in scripts/git_branch_cleaner.py:19
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
scripts/git_branch_cleaner.py:19 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in scripts/git_branch_selector.py:18
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
scripts/git_branch_selector.py:18 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in scripts/gitlab_stale_branches.py:18
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
scripts/gitlab_stale_branches.py:18 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — opensankey/server/views_export.py:148
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 28 placeholder/mock markers across 11 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
2 test file(s) for 144 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Maintenance conf 1.00 34 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 288 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: ubuntu:jammy
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:2 containersPinned dependencies
low System graph security security conf 1.00 Insecure pattern 'debug_true' in opensankey/app.py:29
Found a known-risky pattern (debug_true). Review and replace if possible.
opensankey/app.py:29 Debug true
low System graph quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/gitlab_stale_branches.py:delete_branches_interactive, scripts/gitlab_stale_branches.py:delete_branch This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document wh…
7 occurrences
repo-level (7 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: scripts/gitlab_stale_branches.py:run_command, scripts/git_branch_cleaner.py:run_command, scripts/git_branch_selector.py:run_command This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Con…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: setup.py:run, setup.py:run, setup.py:run, setup.py:run This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
duplicatesduplication
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/1.0.7/editor/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
examples/1.0.7/editor/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/1.0.7/viewer/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
examples/1.0.7/viewer/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/1.1.4/editor/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
examples/1.1.4/editor/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/1.1.4/viewer/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
examples/1.1.4/viewer/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/current/editor/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
examples/current/editor/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/current/viewer/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
examples/current/viewer/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: opensankey/client/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
opensankey/client/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_icon_copy` in opensankey/client/src/css/IconLibrairie.tsx:1651
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cast_copy` in opensankey/client/src/Elements/Legend.tsx:74
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `child_to_copy` in opensankey/client/src/Elements/LinkValues.tsx:103
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `container_to_copy` in opensankey/client/src/Elements/TextZone.tsx:26
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `convert_data_legacy` in opensankey/client/src/Persistence/Legacy.tsx:342
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `convert_data_legacy` in opensankey/client/src/Persistence/SankeyPersistence.tsx:50
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `drawing_area_to_copy` in opensankey/client/src/types/DrawingArea.tsx:402
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `element_to_copy` in opensankey/client/src/Elements/Element.tsx:182
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `errorOnDeprecated` in opensankey/client/jest.config.ts:51
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `node_to_copy` in opensankey/client/src/Elements/Node.tsx:169
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `node_to_copy` in opensankey/client/src/Elements/NodeDimension.tsx:606
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `node_to_copy` in opensankey/client/src/Elements/NodeTagsManager.tsx:58
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `sankey_to_copy` in opensankey/client/src/types/Sankey.tsx:235
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `tag_to_copy` in opensankey/client/src/types/Tag.tsx:128
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `tagg_to_copy` in opensankey/client/src/types/TagGroup.tsx:78
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
examples/1.1.4/viewer/package.json CI/CD securitySupply chainNpm
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
examples/current/viewer/package.json CI/CD securitySupply chainNpm
low System graph software Dead code conf 1.00 Possibly dead Python function: page_not_found
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/__init__.py:18
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_bg
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:88
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_flow
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:144
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_label_name
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:233
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_label_position
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:285
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_label_value
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:258
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_labels
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:200
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_layout
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:171
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_margin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:61
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_meta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:364
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_node
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:111
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_size
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:38
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_themeoffset
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:337
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_setting_line_value
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:312
low System graph software Dead code conf 1.00 Possibly dead Python function: sort_nodeIO
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic_utils.py:499
low System graph software Dead code conf 1.00 Possibly dead Python function: test_parse_sankeymatic_flow
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic.py:602
low System graph software Dead code conf 1.00 Possibly dead Python function: test_parse_sankeymatic_flows
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic.py:610
low System graph software Dead code conf 1.00 Possibly dead Python function: test_parse_sankeymatic_node_color
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic.py:576
low System graph software Dead code conf 1.00 Possibly dead Python function: test_parse_sankeymatic_setting
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
opensankey/server/sankeymatic.py:696
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/Algorithms/NodePositioning.tsx:110
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/App.tsx:122
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/components/configmenus/SankeyMenuConfigurationLayout.tsx:930
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/components/configmenus/SankeyMenuConfigurationLinksData.tsx:320
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/components/dialogs/PersistenceProcessDialog.tsx:849
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/components/topmenus/MenuTop.tsx:107
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/components/welcome/ModalWelcome.tsx:229
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/Elements/Node.tsx:788
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/Elements/NodeDimension.tsx:892
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/Elements/NodeTagsManager.tsx:106
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/Elements/TooltipsConfig.tsx:377
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/index.tsx:90
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/Persistence/Legacy.tsx:673
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/Persistence/SankeyPersistence.tsx:166
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/Persistence/UniversalJSONCompression.tsx:82
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/registerServiceWorker.js:42
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — opensankey/client/src/types/ApplicationData.tsx:716
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: ANY /
`opensankey/doc/views.py` declares `ANY /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /<adress>
`opensankey/doc/views.py` declares `ANY /<adress>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /_images/<path>
`opensankey/doc/views.py` declares `ANY /_images/<path>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /convert/launch
`opensankey/server/views.py` declares `ANY /convert/launch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /convert/peek_options
`opensankey/server/views.py` declares `ANY /convert/peek_options` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /example/download
`opensankey/server/views.py` declares `ANY /example/download` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /menus/examples
`opensankey/server/views.py` declares `ANY /menus/examples` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /menus/excel_template
`opensankey/server/views.py` declares `ANY /menus/excel_template` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /menus/templates
`opensankey/server/views.py` declares `ANY /menus/templates` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /menus/tutorials
`opensankey/server/views.py` declares `ANY /menus/tutorials` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /open_sankeymatic
`opensankey/server/views.py` declares `ANY /open_sankeymatic` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /save/pdf
`opensankey/server/views_export.py` declares `ANY /save/pdf` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /save/pdf/post_clean
`opensankey/server/views_export.py` declares `ANY /save/pdf/post_clean` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /save/png
`opensankey/server/views_export.py` declares `ANY /save/png` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /save/png/post_clean
`opensankey/server/views_export.py` declares `ANY /save/png/post_clean` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /save/svg
`opensankey/server/views_export.py` declares `ANY /save/svg` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /save/svg/post_clean
`opensankey/server/views_export.py` declares `ANY /save/svg/post_clean` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /upload/check_process
`opensankey/server/views.py` declares `ANY /upload/check_process` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /upload/clean
`opensankey/server/views.py` declares `ANY /upload/clean` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /upload/retrieve_json
`opensankey/server/views.py` declares `ANY /upload/retrieve_json` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /upload/retrieve_result
`opensankey/server/views.py` declares `ANY /upload/retrieve_result` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /url/load_json
`opensankey/server/views.py` declares `ANY /url/load_json` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/Algorithms/NodePositioning.tsx (3565 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/components/configmenus/MenuCommon.tsx (1769 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/components/configmenus/MenuElementsAppearance.tsx (3498 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/components/dialogs/PersistenceProcessDialog.tsx (1580 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/components/dialogs/PersistenceProcessDialogConfigs.tsx (2289 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/components/topmenus/MenuTop.tsx (1478 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/css/IconLibrairie.tsx (1870 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/css/Theme.tsx (3274 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/Elements/DrawLabel.tsx (2820 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/Elements/Element.tsx (1359 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/Elements/ElementsAttributesConfig.tsx (3366 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/Elements/Link.tsx (2422 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/Elements/Node.tsx (2257 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/Persistence/Legacy.tsx (2795 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/Persistence/SankeyPersistence.tsx (2447 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/traductions/traduction_app_elements.tsx (2747 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/traductions/traduction_nodes.tsx (1230 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/types/ApplicationData.tsx (1924 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/types/DrawingArea.tsx (3386 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/client/src/types/MenuConfig.tsx (1535 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: opensankey/server/views.py (1486 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/2cf2752a-9fcc-488d-93bc-b43973850147/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2cf2752a-9fcc-488d-93bc-b43973850147/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.