Azim-Ahmed/Node-flow-diagram

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.

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

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

https://github.com/Azim-Ahmed/Node-flow-diagram · scanned 2026-06-05 16:56 UTC (5 days ago) · 10 languages

155 raw signals (119 security + 36 graph) 23rd percentile · Javascript · small (2-20K LoC) System graph score 89 (lower by 40)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days ago · v2 · 136 actionable findings from 2 signal sources. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 18 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	45.5	0.25	11.38
`testing_score`	17.0	0.20	3.40
`documentation_score`	38.7	0.15	5.81
`practices_score`	42.0	0.15	6.30
`code_quality`	79.4	0.10	7.94
Overall		1.00	49.8

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 36 Medium 52 Low 35 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 118 System graph 18 Crowd 0 Layer: Quality 15 Security 2 Software 112 Api 1 Frontend 5 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.

Commented-out code 2 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/`.

2 matching findings on this repo

info Commented-code block (5 lines) in src/redux/actions/auth.actions.js:111
info Commented-code block (6 lines) in src/assets/FlowData/index.js:10

View all commented-out code findings →

Config drift 3 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.

3 matching findings on this repo

medium No CI/CD configuration found
low File has no detected symbols: tailwind.config.js
low File has no detected symbols: postcss.config.js

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/a66c87f6-8eb8-43de-aca2-f6fdfc8daf66/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a66c87f6-8eb8-43de-aca2-f6fdfc8daf66/

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.