neurons-me/all.this

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.

1 of your 27 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.24s · analysis 7.78s · 0.6 MB · GitHub API rate-limit (preflight)

https://github.com/neurons-me/all.this · scanned 2026-06-05 17:10 UTC (4 days, 23 hours ago) · 10 languages

75 raw signals (27 security + 48 graph) 8th percentile · Typescript · small (2-20K LoC) System graph score 97 (lower by 50)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 23 hours ago · v2 · 51 actionable findings from 2 signal sources. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 24 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	55.0	0.25	13.75
`testing_score`	0.0	0.20	0.00
`documentation_score`	40.0	0.15	6.00
`practices_score`	42.0	0.15	6.30
`code_quality`	67.6	0.10	6.76
Overall		1.00	47.8

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 11 Medium 12 Low 22 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 27 System graph 24 Crowd 0 Layer: Software 37 Quality 9 Api 1 Frontend 2 Security 1 Cicd 1

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.

Legacy markers 1 finding

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.

1 matching finding on this repo

low File has no detected symbols: src/npm/src/gui-legacy.ts

View all legacy markers findings →

Config drift 1 finding

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.

1 matching finding on this repo

medium No CI/CD configuration found

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/f43550d6-be9b-4cca-930d-1e237a032f03/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f43550d6-be9b-4cca-930d-1e237a032f03/

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.