Sage/carbon

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.

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

Scan timing: clone 4.64s · analysis 49.15s · 13.1 MB · GitHub API rate-limit (preflight)

https://github.com/Sage/carbon · scanned 2026-06-05 12:51 UTC (5 days, 10 hours ago) · 10 languages

360 raw signals (126 security + 234 graph) 51st percentile · Typescript · large (100-500K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 103 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	68.9	0.25	17.23
`testing_score`	71.0	0.20	14.20
`documentation_score`	83.7	0.15	12.55
`practices_score`	84.0	0.15	12.60
`code_quality`	59.5	0.10	5.95
Overall		1.00	75.3

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 2 Medium 14 Low 86 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 53 System graph 103 Crowd 0 Layer: Quality 43 Security 8 Software 72 Cicd 4 Api 1 Frontend 28

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 4 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/`.

4 matching findings on this repo

info Commented-code block (6 lines) in src/__internal__/focus-trap/focus-trap-utils.…
info Commented-code block (5 lines) in src/components/text-editor/__internal__/__ui_…
info Commented-code block (6 lines) in src/components/select/__internal__/select-lis…
info Commented-code block (5 lines) in src/components/portal/portal.pw.tsx:18

View all commented-out code findings →

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

6 matching findings on this repo

medium npm package `@commitlint/config-conventional` is 4 major version(s) behind (17.… package.json
high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… src/components/text-editor/__internal__/__utils__…:34
low File has no detected symbols: babel.config.js
low File has no detected symbols: jest.config.ts
low File has no detected symbols: playwright-ct.config.ts
low Old/deprecated-named symbol `settings_old` in src/components/icon/icon-config.t…

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/1d2b0c80-c5e1-48d3-bc2a-65a7c3970515/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1d2b0c80-c5e1-48d3-bc2a-65a7c3970515/

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.