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.

anvanster/compressor

https://github.com/anvanster/compressor · scanned 2026-06-17 01:34 UTC (1 month, 2 weeks ago)

50 raw signals (0 security + 50 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -12.7 (diff) · 50 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 50 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 5 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 50 Crowd 0 Layer: Frontend 10 Security 4 Cicd 2 Quality 34

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 64.0/100 with 66.7% coverage. It contains 1107 nodes across 11 cross-layer flows, written primarily in mixed languages. Engine surfaced 50 findings — concentrated in quality (34), frontend (10), security (4). Risk profile is high: 0 critical, 1 high, 5 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/cli/commands/benchmark.ts:152

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

src/cli/commands/benchmark.ts:152 Exec used

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/bench/cell.ts:1

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

src/bench/cell.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/commands/benchmark.ts:1

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

src/cli/commands/benchmark.ts:1 Node child process

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

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

src/paths.ts:1 Node child process

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

medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration

A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.

Runtime configService clientGenerated repo pattern

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

Found 398 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 `oursOld` in test/adapters/claude-code.test.ts:335

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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/cli/commands/benchmark.ts:459