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 52 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.33s · analysis 14.43s · 2.3 MB · GitHub API rate-limit (preflight)

jquery/jquery

https://github.com/jquery/jquery · scanned 2026-06-05 09:46 UTC (5 days, 17 hours ago) · 10 languages

237 raw signals (49 security + 188 graph) 83rd percentile · Javascript · medium (20-100K LoC) System graph score 96 (lower by 17)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 65.2 0.25 16.30
testing_score 90.0 0.20 18.00
documentation_score 85.0 0.15 12.75
practices_score 83.0 0.15 12.45
code_quality 67.7 0.10 6.77
Overall 1.00 79.0
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 19 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 (9 lines) in eslint.config.js:51
  • info Commented-code block (6 lines) in test/unit/core.js:1126
  • info Commented-code block (6 lines) in test/unit/event.js:3296
  • info Commented-code block (8 lines) in test/unit/manipulation.js:2395
  • info Commented-code block (6 lines) in test/unit/offset.js:572
  • info Commented-code block (5 lines) in test/unit/selector.js:298
  • info Commented-code block (5 lines) in src/event.js:353
  • info Commented-code block (6 lines) in src/selector-native.js:94
  • info Commented-code block (7 lines) in src/data.js:9
  • info Commented-code block (5 lines) in src/ajax.js:459
  • info Commented-code block (5 lines) in src/offset.js:146
  • info Commented-code block (6 lines) in src/selector.js:165
View all commented-out code findings →
Config drift 5 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.
5 matching findings on this repo
  • low File has no detected symbols: eslint.config.js
  • low File has no detected symbols: test/bundler_smoke_tests/rollup-pure-esm.config.js
  • low File has no detected symbols: test/bundler_smoke_tests/rollup-commonjs.config.js
  • info TODO/FIXME marker in shipping code — eslint.config.js:42
  • info Commented-code block (9 lines) in eslint.config.js:51
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/bbea5ca8-5cd7-46ca-8551-2cc271adf6b8/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bbea5ca8-5cd7-46ca-8551-2cc271adf6b8/

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.