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.
Sign up free Scan another repo
39 of your 86 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

tailwindlabs/tailwindcss

https://github.com/tailwindlabs/tailwindcss · scanned 2026-06-05 06:50 UTC (6 days, 1 hour ago) · 10 languages

362 raw signals (74 security + 288 graph) 11/13 scanners ran 75th percentile · Typescript · medium (20-100K LoC) System graph score 84 (lower by 6)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 6 days, 1 hour ago · v2 · 171 actionable findings from 2 signal sources. 47 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
81.7
/100
Security checks
79
27 findings
System graph
84
100.0% cov · 144 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
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 95.0 0.20 19.00
documentation_score 64.0 0.15 9.60
practices_score 57.0 0.15 8.55
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 35 Medium 9 Low 77 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 27 System graph 144 Crowd 0 Layer: Security 40 Quality 58 Software 53 Cicd 4 Api 1 Frontend 15

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 2 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.
2 matching findings on this repo
  • low File has no detected symbols: packages/@tailwindcss-upgrade/src/codemods/templa…
  • low File has no detected symbols: packages/@tailwindcss-upgrade/src/codemods/templa…
View all legacy markers findings →
Commented-out code 22 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 (5 lines) in integrations/utils.ts:425
  • info Commented-code block (5 lines) in packages/@tailwindcss-node/src/env.ts:21
  • info Commented-code block (7 lines) in packages/@tailwindcss-upgrade/src/codemods/co…
  • info Commented-code block (5 lines) in packages/@tailwindcss-upgrade/src/codemods/cs…
  • info Commented-code block (5 lines) in packages/@tailwindcss-upgrade/src/codemods/cs…
  • info Commented-code block (5 lines) in packages/@tailwindcss-upgrade/src/codemods/cs…
  • info Commented-code block (5 lines) in packages/@tailwindcss-upgrade/src/codemods/te…
  • info Commented-code block (6 lines) in packages/@tailwindcss-upgrade/src/codemods/te…
  • info Commented-code block (5 lines) in packages/@tailwindcss-upgrade/src/utils/write…
  • info Commented-code block (5 lines) in packages/tailwindcss/playwright.config.ts:59
  • info Commented-code block (5 lines) in packages/tailwindcss/src/compile.ts:220
  • info Commented-code block (5 lines) in packages/tailwindcss/src/css-functions.ts:128
View all commented-out code findings →
Config drift 18 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: vitest.config.ts
  • low File has no detected symbols: integrations/vitest.config.ts
  • low File has no detected symbols: integrations/vite/config.test.ts
  • low File has no detected symbols: integrations/upgrade/js-config.test.ts
  • low File has no detected symbols: integrations/postcss/config.test.ts
  • low File has no detected symbols: packages/@tailwindcss-node/tsup.config.ts
  • low File has no detected symbols: packages/@tailwindcss-postcss/tsup.config.ts
  • low File has no detected symbols: packages/@tailwindcss-webpack/tsup.config.ts
  • low File has no detected symbols: packages/@tailwindcss-upgrade/tsup.config.ts
  • high Insecure pattern 'exec_used' in integrations/cli/config.test.ts:36 integrations/cli/config.test.ts:36
  • high Insecure pattern 'exec_used' in integrations/vite/config.test.ts:54 integrations/vite/config.test.ts:54
  • high Insecure pattern 'exec_used' in integrations/upgrade/js-config.test.ts:167 integrations/upgrade/js-config.test.ts:167
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/87b2d1e1-fc68-452c-9f93-8e943f10b5e2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/87b2d1e1-fc68-452c-9f93-8e943f10b5e2/

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.