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.

triggerdotdev/trigger.dev

https://github.com/triggerdotdev/trigger.dev · scanned 2026-06-16 00:42 UTC (2 months, 1 week ago)

744 raw signals (0 security + 744 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 727 actionable findings from 1 signal source. 17 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 · 727 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 45 Medium 75 Low 256 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 727 Crowd 0 Layer: Frontend 193 Network 7 Hardware 1 Security 37 Cicd 1 Quality 448 Api 40

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

medium Agent authority lacks a verifier contract: .claude/rules/legacy-v3-code.md .claude/rules/legacy-v3-code.md
low Old/deprecated-named symbol `referralSourceForLegacy` in apps/webapp/app/routes…

View all legacy markers findings →

Commented-out code 253 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 apps/coordinator/src/index.ts:694
info Commented-code block (7 lines) in apps/supervisor/src/env.ts:160
info Commented-code block (5 lines) in apps/supervisor/src/index.ts:513
info Commented-code block (11 lines) in apps/supervisor/src/workloadServer/index.ts:…
info Commented-code block (7 lines) in apps/supervisor/src/workloadManager/compute.t…
info Commented-code block (5 lines) in apps/webapp/sentry.server.ts:4
info Commented-code block (5 lines) in apps/webapp/vitest.e2e.full.config.ts:4
info Commented-code block (6 lines) in apps/webapp/test/mollifierSyntheticRunHeader.…
info Commented-code block (8 lines) in apps/webapp/test/auth-cross-cutting.e2e.full.…
info Commented-code block (5 lines) in apps/webapp/test/metadataRouteOperationsLoggi…
info Commented-code block (5 lines) in apps/webapp/test/auth-dashboard.e2e.full.test…
info Commented-code block (7 lines) in apps/webapp/test/api-auth.e2e.test.ts:126

View all commented-out code findings →

Config drift 15 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 — packages/cli-v3/src/config.ts:226
high Agent instruction/config may expose a secret: packages/trigger-sdk/skills/autho… packages/trigger-sdk/skills/authoring-tasks/SKILL…:236
high Agent instruction/config may expose a secret: packages/trigger-sdk/skills/realt… packages/trigger-sdk/skills/realtime-and-frontend…:62
high Agent instruction/config may expose a secret: packages/cli-v3/skills/authoring-… packages/cli-v3/skills/authoring-tasks/SKILL.md:52
high Agent instruction/config may expose a secret: packages/cli-v3/skills/getting-st… packages/cli-v3/skills/getting-started/SKILL.md:136
high Agent instruction/config may expose a secret: packages/cli-v3/skills/realtime-a… packages/cli-v3/skills/realtime-and-frontend/SKIL…:31
high Agent instruction/config may expose a secret: .claude/review-guides/chat-agent-… .claude/review-guides/chat-agent-sessions-row-agn…:67
high Agent instruction/config may expose a secret: .claude/skills/trigger-dev-tasks/… .claude/skills/trigger-dev-tasks/advanced-tasks.md:94
high Agent instruction/config may expose a secret: .claude/skills/trigger-dev-tasks/… .claude/skills/trigger-dev-tasks/scheduled-tasks.…:53
high Agent instruction/config may expose a secret: .claude/skills/trigger-dev-tasks/… .claude/skills/trigger-dev-tasks/basic-tasks.md:78
high Agent instruction/config may expose a secret: .claude/skills/trigger-dev-tasks/… .claude/skills/trigger-dev-tasks/SKILL.md:139
high Agent instruction/config may expose a secret: .cursor/rules/writing-tasks.mdc .cursor/rules/writing-tasks.mdc:259

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/3af173b2-ae90-4963-8347-35278c30447e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3af173b2-ae90-4963-8347-35278c30447e/

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.