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.

Automattic/jetpack

https://github.com/Automattic/jetpack · scanned 2026-06-17 01:23 UTC (1 month, 2 weeks ago)

730 raw signals (0 security + 730 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -27.0 (diff) · 635 actionable findings from 1 signal source. 95 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 635 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 7 Medium 199 Low 220 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 635 Crowd 0 Layer: Frontend 154 Network 1 Hardware 3 Security 117 Cicd 4 Quality 350 Api 6

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

5 matching findings on this repo

medium Insecure pattern 'direct_innerhtml_assignment' in projects/packages/paypal-paym… projects/packages/paypal-payments/src/legacy/payp…:97
low Old/deprecated-named symbol `useShowMinifyLegacy` in projects/plugins/boost/app…
low Old/deprecated-named symbol `useShowMinifyLegacy` in projects/plugins/boost/app…
low Old/deprecated-named symbol `useShowMinifyLegacy` in projects/plugins/boost/app…
low Old/deprecated-named symbol `isLegacy` in projects/plugins/jetpack/_inc/client/…

View all legacy markers findings →

Commented-out code 131 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 (12 lines) in tools/jetpack-live-branches/jetpack-live-bra…
info Commented-code block (5 lines) in tools/cli/commands/draft.js:119
info Commented-code block (6 lines) in tools/cli/commands/playground.js:73
info Commented-code block (7 lines) in tools/cli/commands/generate.js:237
info Commented-code block (7 lines) in tools/cli/commands/docker.js:824
info Commented-code block (5 lines) in tools/js-tools/await-packagist-updates.mjs:174
info Commented-code block (7 lines) in projects/plugins/inspect/rollup.config.js:20
info Commented-code block (5 lines) in projects/plugins/protect/src/js/components/pr…
info Commented-code block (6 lines) in projects/plugins/search/tests/e2e/specs/searc…
info Commented-code block (5 lines) in projects/plugins/jetpack/extensions/plugins/a…
info Commented-code block (7 lines) in projects/plugins/jetpack/extensions/plugins/a…
info Commented-code block (7 lines) in projects/plugins/jetpack/extensions/extended-…

View all commented-out code findings →

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

info TODO/FIXME marker in shipping code — tools/e2e-commons/playwright.config.defaul…
info TODO/FIXME marker in shipping code — projects/plugins/search/tests/e2e/specs/se…
high Insecure pattern 'new_function_used' in projects/js-packages/webpack-config/src… projects/js-packages/webpack-config/src/webpack/t…:56
medium Insecure pattern 'cors_wildcard' in projects/js-packages/webpack-config/src/web… projects/js-packages/webpack-config/src/webpack/d…:26
low Node manifest has dependencies but no lockfile: projects/js-packages/eslint-con… projects/js-packages/eslint-config-target-es/pack…
low Node manifest has dependencies but no lockfile: projects/js-packages/webpack-co… projects/js-packages/webpack-config/package.json
low Node manifest has dependencies but no lockfile: projects/js-packages/config/pac… projects/js-packages/config/package.json
medium Runtime service client appears to use placeholder configuration
info Commented-code block (7 lines) in projects/plugins/inspect/rollup.config.js:20
info Commented-code block (6 lines) in projects/plugins/search/tests/e2e/specs/searc…
info Commented-code block (7 lines) in projects/plugins/jetpack/tools/postcss.config…
info Commented-code block (5 lines) in projects/packages/videopress/postcss.config.j…

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/29954aa8-0f24-40a0-9ad1-9fd42dd4b303/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/29954aa8-0f24-40a0-9ad1-9fd42dd4b303/

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.