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

Daky0000/Saas

https://github.com/Daky0000/Saas · scanned 2026-06-17 01:26 UTC (1 month, 2 weeks ago)

395 raw signals (0 security + 395 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -27.2 (diff) · 391 actionable findings from 1 signal source. 4 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
49.5
/100
Security checks
50
0 findings
System graph
50
100.0% cov · 391 findings
Critical
1
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 139 Medium 87 Low 99 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 391 Crowd 0 Layer: Software 1 Frontend 72 Hardware 2 Security 14 Cicd 2 Quality 112 Api 188

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 6 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/`.
6 matching findings on this repo
  • info Commented-code block (7 lines) in packages/api/src/db-migrations.ts:845
  • info Commented-code block (5 lines) in packages/api/src/server/distributionRoutes.ts…
  • info Commented-code block (15 lines) in scripts/archive/extract-db-migrations.mjs:38
  • info Commented-code block (6 lines) in scripts/archive/wire-social-connect-routes.mj…
  • info Commented-code block (6 lines) in .claude/skills/remotion-to-hyperframes/assets…
  • info Commented-code block (6 lines) in .claude/skills/remotion-to-hyperframes/assets…
View all commented-out code findings →
Config drift 10 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.
10 matching findings on this repo
  • medium Runtime service client appears to use placeholder configuration
  • medium `fetch()` without try/.catch or AbortSignal — packages/web/src/components/admin…
  • info Commented-code block (6 lines) in .claude/skills/remotion-to-hyperframes/assets…
  • high Dangling fetch: GET https://${serverPrefix}.api.mailchimp.com/3.0/ (packages/ap…
  • high Dangling fetch: GET https://api.openai.com/v1/models (packages/api/src/server/p…
  • high Dangling fetch: GET https://api.webflow.com/v2/sites (packages/api/src/server/p…
  • high Dangling fetch: GET https://api.stripe.com/v1/account (packages/api/src/server/…
  • high Dangling fetch: POST https://api.linear.app/graphql (packages/api/src/server/pl…
  • high Dangling fetch: GET https://connect.squareup.com/v2/locations (packages/api/src…
  • high Dangling fetch: GET https://api.apify.com/v2/users/me (packages/api/src/server/…
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/5a67746a-a96f-4dc1-9660-e1093deeee0c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5a67746a-a96f-4dc1-9660-e1093deeee0c/

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.