bluesky-social/social-app

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.

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

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 35.88s for a 71.1 MB repo slow.
Repobility's analysis ran in 18.91s after the clone landed.

https://github.com/bluesky-social/social-app · scanned 2026-06-05 23:28 UTC (4 days, 5 hours ago) · 10 languages

826 raw signals (136 security + 690 graph) 11/13 scanners ran 48th percentile · Typescript · large (100-500K LoC) System graph score 46 (higher by 28)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 5 hours ago · v2 · 292 actionable findings from 2 signal sources. 189 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 · 238 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	25.0	0.20	5.00
`documentation_score`	61.0	0.15	9.15
`practices_score`	97.0	0.15	14.55
`code_quality`	80.0	0.10	8.00
Overall		1.00	74.5

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 4 High 18 Medium 38 Low 100 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 54 System graph 238 Crowd 0 Layer: Quality 92 Cicd 23 Software 57 Security 7 Frontend 98 Hardware 5 Api 10

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 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `enableFullScreenImage_legacy` in app.config.js:328

View all legacy markers findings →

Commented-out code 31 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 (11 lines) in dev-env/test-pds.ts:86
info Commented-code block (5 lines) in src/Navigation.tsx:807
info Commented-code block (7 lines) in src/state/queries/nuxs/index.ts:47
info Commented-code block (7 lines) in src/analytics/PassiveAnalytics.tsx:28
info Commented-code block (5 lines) in src/screens/Deactivated.tsx:60
info Commented-code block (5 lines) in src/screens/Login/LoginForm.tsx:247
info Commented-code block (9 lines) in src/screens/Settings/AppIconSettings/useAppIc…
info Commented-code block (5 lines) in src/screens/Search/modules/ExploreTrendingVid…
info Commented-code block (6 lines) in src/screens/Messages/components/MessageInput.…
info Commented-code block (5 lines) in src/screens/Messages/components/MessageInput.…
info Commented-code block (5 lines) in src/screens/Messages/components/groupSystemMe…
info Commented-code block (6 lines) in src/platform/crypto.ts:1

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

low File has no detected symbols: metro.config.js
low File has no detected symbols: babel.config.js
low File has no detected symbols: lingui.config.ts
low File has no detected symbols: prettier.config.ts
low File has no detected symbols: app.config.js
low Old/deprecated-named symbol `enableFullScreenImage_legacy` in app.config.js:328

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/249cc9eb-5ca4-4bb8-88aa-f2e4f2e3fed6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/249cc9eb-5ca4-4bb8-88aa-f2e4f2e3fed6/

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.