bluesky-social/atproto-website

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.

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

Scan timing: clone 20.47s · analysis 23.85s · 23.0 MB · GitHub preflight 436ms

https://github.com/bluesky-social/atproto-website · scanned 2026-06-05 19:34 UTC (4 days, 16 hours ago) · 10 languages

145 raw signals (103 security + 42 graph) 7th percentile · Typescript · small (2-20K LoC) System graph score 90 (lower by 43)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 16 hours ago · v2 · 94 actionable findings from 2 signal sources. 30 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 · 21 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	40.5	0.25	10.12
`testing_score`	0.0	0.20	0.00
`documentation_score`	59.7	0.15	8.96
`practices_score`	57.0	0.15	8.55
`code_quality`	70.3	0.10	7.03
Overall		1.00	47.4

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 11 Medium 23 Low 27 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 73 System graph 21 Crowd 0 Layer: Quality 27 Security 12 Software 48 Api 1 Frontend 5 Cicd 1

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 (5 lines) in public/bsky-conversation.js:446
info Commented-code block (5 lines) in src/components/YouTubeEmbed.tsx:5
info Commented-code block (6 lines) in src/components/home/GlobeAnimation.tsx:309
info Commented-code block (5 lines) in src/app/off-protocol/rss.xml/route.ts:3

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

medium No CI/CD configuration found
low File has no detected symbols: prettier.config.js
low File has no detected symbols: tailwind.config.ts
low File has no detected symbols: i18nConfig.js
low File has no detected symbols: postcss.config.js

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/4ee38bee-6dbc-47f5-86fb-815cdc5e9dac/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4ee38bee-6dbc-47f5-86fb-815cdc5e9dac/

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.