wso2/apim-apps

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.

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

Scan timing: clone 5.61s · analysis 16.21s · 25.2 MB · GitHub API rate-limit (preflight)

https://github.com/wso2/apim-apps · scanned 2026-06-05 15:09 UTC (5 days, 2 hours ago) · 10 languages

864 raw signals (96 security + 768 graph) 11/13 scanners ran 52nd percentile · Javascript · large (100-500K LoC) System graph score 71 (higher by 8)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 2 hours ago · v2 · 380 actionable findings from 2 signal sources. 99 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 · 351 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	84.0	0.20	16.80
`documentation_score`	69.0	0.15	10.35
`practices_score`	67.0	0.15	10.05
`code_quality`	70.0	0.10	7.00
Overall		1.00	78.2

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 38 Low 200 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 29 System graph 351 Crowd 0 Layer: Quality 108 Security 7 Software 53 Cicd 2 Frontend 199 Api 11

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 15 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.

12 matching findings on this repo

low Stray `console.log` in TS/JS — portals/devportal/src/main/webapp/source/src/app…
low Old/deprecated-named symbol `LayoutLegacy` in portals/devportal/src/main/webapp…
low Old/deprecated-named symbol `RecommendationsLegacy` in portals/devportal/src/ma…
low Old/deprecated-named symbol `SubscriptionPolicySelectLegacy` in portals/devport…
low Old/deprecated-named symbol `RecommendedApiThumbLegacy` in portals/devportal/sr…
low Old/deprecated-named symbol `StarRatingBarLegacy` in portals/devportal/src/main…
low Old/deprecated-named symbol `CommonListingLegacy` in portals/devportal/src/main…
low Old/deprecated-named symbol `ApiTableViewLegacy` in portals/devportal/src/main/…
low Old/deprecated-named symbol `ApiThumbClassicLegacy` in portals/devportal/src/ma…
low Old/deprecated-named symbol `ImageGeneratorLegacy` in portals/devportal/src/mai…
low Old/deprecated-named symbol `DetailsLegacy` in portals/devportal/src/main/webap…
low Old/deprecated-named symbol `SdkLegacy` in portals/devportal/src/main/webapp/so…

View all legacy markers findings →

Commented-out code 13 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 TODO/FIXME marker in shipping code — portals/devportal/src/main/webapp/source/s…
info TODO/FIXME marker in shipping code — portals/publisher/src/main/webapp/source/s…
info Commented-code block (8 lines) in tests/cypress/e2e/devportal/001-applications/…
info Commented-code block (5 lines) in tests/cypress/e2e/publisher/016-service-catal…
info Commented-code block (6 lines) in tests/cypress/e2e/publisher/019-read-only-use…
info Commented-code block (7 lines) in tests/cypress/e2e/publisher/011-lifecycle/01-…
info Commented-code block (6 lines) in portals/devportal/src/main/webapp/source/src/…
low Old/deprecated-named symbol `CommentEditLegacy` in portals/devportal/src/main/w…
info Commented-code block (5 lines) in portals/devportal/src/main/webapp/source/src/…
info Commented-code block (6 lines) in portals/publisher/src/main/webapp/source/Test…
info Commented-code block (12 lines) in portals/publisher/src/main/webapp/source/src…
info Commented-code block (6 lines) in portals/publisher/src/main/webapp/source/src/…

View all commented-out code findings →

Config drift 26 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

low File has no detected symbols: tests/babel.config.js
low File has no detected symbols: tests/cypress/e2e/admin/10-advanced-configuration…
low File has no detected symbols: tests/cypress/e2e/publisher/003-run-time-configs/…
low File has no detected symbols: tests/cypress/e2e/publisher/003-run-time-configs/…
low File has no detected symbols: tests/cypress/e2e/publisher/003-run-time-configs/…
low File has no detected symbols: tests/cypress/e2e/publisher/003-run-time-configs/…
low File has no detected symbols: tests/cypress/e2e/publisher/003-run-time-configs/…
low File has no detected symbols: tests/cypress/e2e/publisher/003-run-time-configs/…
low File has no detected symbols: tests/cypress/e2e/publisher/003-run-time-configs/…
low Stray `console.log` in TS/JS — tests/cypress.config.js:59
info TODO/FIXME marker in shipping code — portals/admin/src/main/webapp/webpack.conf…
info TODO/FIXME marker in shipping code — portals/devportal/src/main/webapp/source/s…

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/9d03fbc2-272b-4044-be4f-8d6b70ce1b87/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9d03fbc2-272b-4044-be4f-8d6b70ce1b87/

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.