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.

ucsandman/Magnetic

https://github.com/ucsandman/Magnetic · scanned 2026-06-16 00:44 UTC (2 months, 1 week ago)

49 raw signals (0 security + 49 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 49 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 49 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 28 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 49 Crowd 0 Layer: Frontend 16 Security 17 Cicd 2 Quality 14

Exclude dismissed / FP Exclude test files

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 85.1/100 with 77.8% coverage. It contains 832 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 49 findings — concentrated in security (17), frontend (16), quality (14). Risk profile is low: 0 critical, 0 high, 28 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 45 of 49 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/fetch-binaries.mjs:71

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 — src/main/media-server.test.ts:44

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 — src/main/media-server.ts:16

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 — src/main/protocol.ts:52

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 — src/renderer/browser/Waveform.tsx:13

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 — src/renderer/playback/decoder/sample-decoder.ts:11

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 — src/renderer/playback/offline.ts:49

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 — src/renderer/playback/pcm-source.ts:150

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 — src/renderer/silence/SilencePanel.tsx:41

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 'cors_wildcard' in src/main/protocol.ts:53

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

src/main/protocol.ts:53 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/dump-shortcuts.mjs:3

Found a known-risky pattern (node_child_process). Review and replace if possible.

scripts/dump-shortcuts.mjs:3 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/fetch-binaries.mjs:12

Found a known-risky pattern (node_child_process). Review and replace if possible.

scripts/fetch-binaries.mjs:12 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/make-fixtures.mjs:13

Found a known-risky pattern (node_child_process). Review and replace if possible.

scripts/make-fixtures.mjs:13 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/export/encoder.ts:1

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/export/encoder.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/export/smart-render.ts:1

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/export/smart-render.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/ipc.ts:2

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/ipc.ts:2 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/jobs/filmstrip.ts:1

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/jobs/filmstrip.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/jobs/media-derivatives.ts:1

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/jobs/media-derivatives.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/jobs/transcribe.ts:1

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/jobs/transcribe.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/jobs/waveform.ts:1

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/jobs/waveform.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/project-io/import.ts:2

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/project-io/import.ts:2 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/project-io/probe.ts:1

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/project-io/probe.ts:1 Node child process

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 cicd CI/CD security conf 1.00 No CI/CD pipelines detected

No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.

CI/CD securityCoverage

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 27 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 quality Integrity conf 1.00 Old/deprecated-named symbol `gapIdByOld` in src/shared/timeline/ops.ts:311

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.

package.json CI/CD securitySupply chainNpm

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 — e2e/captions.spec.ts:117