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

Scan timing: clone 6.19s · analysis 12.12s · 95.0 MB · GitHub API rate-limit (preflight)

PostHog/posthog-js

https://github.com/PostHog/posthog-js · scanned 2026-06-05 18:32 UTC (4 days, 19 hours ago) · 10 languages

1216 raw signals (120 security + 1096 graph) 11/13 scanners ran 84th percentile · Typescript · large (100-500K LoC) System graph score 52 (higher by 32)

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

Complete repo analysis

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

JSON
Combined
66.9
/100
Security checks
82
57 findings
System graph
52
100.0% cov · 539 findings
Critical
119
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 91.0 0.15 13.65
practices_score 73.0 0.15 10.95
code_quality 70.0 0.10 7.00
Overall 1.00 84.6
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 119 High 36 Medium 43 Low 255 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 57 System graph 539 Crowd 0 Layer: Security 131 Cicd 8 Quality 176 Software 55 Frontend 178 Hardware 3 Api 45

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 4 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.
4 matching findings on this repo
  • low Old/deprecated-named symbol `OptionalExpoFileSystemLegacy` in packages/react-na…
  • low Old/deprecated-named symbol `OptionalExpoFileSystemLegacy` in packages/react-na…
  • low Old/deprecated-named symbol `OptionalExpoFileSystemLegacy` in packages/react-na…
  • low Old/deprecated-named symbol `OptionalExpoFileSystemLegacy` in packages/react-na…
View all legacy markers findings →
Commented-out code 71 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 packages/node/src/extensions/sentry-integrati…
  • info Commented-code block (5 lines) in packages/node/src/extensions/feature-flags/fe…
  • info Commented-code block (7 lines) in packages/nextjs-config/src/config.ts:23
  • info Commented-code block (9 lines) in packages/types/src/session-recording.ts:76
  • info Commented-code block (5 lines) in packages/react-native/test/posthog.spec.ts:21…
  • info Commented-code block (6 lines) in packages/react-native/test/posthog-xcode-pars…
  • info Commented-code block (5 lines) in packages/react-native/test/expoconfig.spec.ts…
  • info Commented-code block (6 lines) in packages/react-native/test/storage.spec.ts:214
  • info Commented-code block (6 lines) in packages/react-native/src/native-deps.tsx:176
  • info Commented-code block (7 lines) in packages/react-native/src/storage.ts:11
  • info Commented-code block (5 lines) in packages/react-native/src/posthog-rn.ts:265
  • info Commented-code block (5 lines) in packages/react-native/src/tooling/expoconfig.…
View all commented-out code findings →
Config drift 19 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: playground/remix/vite.config.ts
  • low File has no detected symbols: playground/vite/vite.config.ts
  • low File has no detected symbols: playground/webpack/webpack.config.ts
  • low File has no detected symbols: playground/react-nextjs/next.config.js
  • low File has no detected symbols: packages/node/rslib.config.ts
  • low File has no detected symbols: packages/types/rslib.config.ts
  • low File has no detected symbols: packages/next/tests/config.test.ts
  • low Stray `console.log` in TS/JS — playground/flags/remote-config-example.js:17
  • info TODO/FIXME marker in shipping code — packages/rrweb/vite.config.default.ts:123
  • low Stray `console.log` in TS/JS — packages/rrweb/vite.config.default.ts:39
  • low Stray `console.log` in TS/JS — packages/rrweb/rrweb/vite.config.js:17
  • low Stray `console.log` in TS/JS — packages/rrweb/rrweb-snapshot/vite.config.js:66
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/1874ab3f-846a-4195-84e6-26fee77143c6/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1874ab3f-846a-4195-84e6-26fee77143c6/

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.