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.

quantixtechnology/Quantix-Core-1.0

https://github.com/quantixtechnology/Quantix-Core-1.0 · scanned 2026-06-15 23:44 UTC (2 months, 4 weeks ago)

609 raw signals (0 security + 609 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 581 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 6 Medium 106 Low 150 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 581 Crowd 0 Layer: Software 27 Api 1 Frontend 168 Security 38 Quality 347

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 2 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

2 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Legacy markers 3 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

3 matching findings on this repo

low Old/deprecated-named symbol `form_fill_legacy` in skills/ppt/scripts/pdf.py:1240
low Old/deprecated-named symbol `form_fill_legacy` in skills/pdf/scripts/pdf.py:1330
low Old/deprecated-named symbol `isLegacy` in src/app/api/debug/store-global-audit/…

View all legacy markers findings →

Commented-out code 221 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (5 lines) in ecosystem.config.js:11
info Commented-code block (6 lines) in next.config.js:12
info Commented-code block (6 lines) in scripts/repair-delivery-users.mjs:4
info Commented-code block (5 lines) in scripts/diagnose-delivery-login.mjs:4
info Commented-code block (5 lines) in skills/skill-creator/scripts/improve_descript…
info Commented-code block (5 lines) in skills/ppt/scripts/html2pptx.js:826
info Commented-code block (6 lines) in skills/ppt/scripts/thumbnail.py:32
info Commented-code block (6 lines) in skills/pdf/scripts/html2pdf-next.js:282
info Commented-code block (6 lines) in skills/pdf/scripts/cover_validate.js:105
info Commented-code block (6 lines) in skills/pdf/scripts/design_engine.py:343
info Commented-code block (5 lines) in public/sw.js:3
info Commented-code block (14 lines) in mini-services/realtime-service/index.ts:5

View all commented-out code findings →

Config drift 15 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

12 matching findings on this repo

info `truncate` class without `title=` for hover reveal — src/components/workflow/wo…
medium Runtime service client appears to use placeholder configuration
medium CI is configured but no tests are detected
high Agent instruction/config may expose a secret: skills/ASR/SKILL.md skills/ASR/SKILL.md:231
high Agent instruction/config may expose a secret: skills/web-reader/SKILL.md skills/web-reader/SKILL.md:876
high Agent instruction/config may expose a secret: skills/web-search/SKILL.md skills/web-search/SKILL.md:614
high Agent instruction/config may expose a secret: skills/image-generation/SKILL.md skills/image-generation/SKILL.md:263
info Commented-code block (5 lines) in ecosystem.config.js:11
info Commented-code block (6 lines) in next.config.js:12
medium `fetch()` without try/.catch or AbortSignal — src/components/business/payment/g…
info Commented-code block (6 lines) in src/app/api/admin/payment-config/route.ts:1
info Commented-code block (5 lines) in src/app/api/core/platform/config/route.ts:1

View all config drift findings →

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/c8c24c93-9b14-4fc7-99e0-83dc9b7d994f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c8c24c93-9b14-4fc7-99e0-83dc9b7d994f/

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.