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

Scan timing: clone 1.45s · analysis 8.0s · 0.6 MB · GitHub API rate-limit (preflight)

google-labs-code/design.md

https://github.com/google-labs-code/design.md.git · scanned 2026-06-25 21:07 UTC (2 months, 2 weeks ago) · 10 languages

41 raw signals (22 security + 19 graph) 65th percentile · Typescript · small (2-20K LoC) System graph score 96 (lower by 14)

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

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 37 actionable findings from 2 signal sources. 4 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
90.2
/100
Security checks
84
18 findings
System graph
96
66.7% cov · 19 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 95.1 0.25 23.77
testing_score 85.0 0.20 17.00
documentation_score 81.0 0.15 12.15
practices_score 65.0 0.15 9.75
code_quality 80.0 0.10 8.00
Overall 1.00 81.9
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 3 Medium 7 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 18 System graph 19 Crowd 0 Layer: Quality 15 Software 6 Security 7 Cicd 2 Frontend 7
Scan summary Repository scanned at 96.4/100 with 66.7% coverage. It contains 271 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 19 findings — concentrated in frontend (7), quality (7), security (5). Risk profile is high: 1 critical, 1 high, 3 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 19 of 37 actionable findings. 41 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Semgrep conf 1.00 detect child process — packages/cli/scripts/check-package.ts:65
Detected calls to child_process from a function argument `cmd`. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized or sandboxed. Rule: javascript.lang.security.detect-child-proc…
SecurityJavascript
medium Security checks quality Quality conf 0.74 2 occurrences Critical user action appears to be handled by a no-op or placeholder
Human reports repeatedly found generated dashboards where buttons existed but only alerted, logged, threw not-implemented errors, or promised coming-soon behavior. This makes the UI look complete while the user journey cannot complete a real action.
lines 40, 264
packages/cli/scripts/check-package.ts:40, 264 (2 hits)
medium Security checks software dependencies conf 0.88 postcss: GHSA-qx2v-qp2m-jg93
PostCSS has XSS via Unescaped </style> in its CSS Stringify Output
bun.lock
medium Security checks software dependencies conf 0.88 turbo: GHSA-hcf7-66rw-9f5r
Trubo: Login callback CSRF/session fixation
bun.lock
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/cli/scripts/check-package.ts:27
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/cli/scripts/check-package.ts:27 Node child process
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
high Security checks software dependencies conf 0.90 npm package `citty` is minor version(s) behind (^0.1.6 -> 0.2.2)
`citty` is pinned/resolved at ^0.1.6 but the latest stable release on the npm registry is 0.2.2 (minor version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
packages/cli/package.json
high Security checks software dependencies conf 0.90 npm package `yaml` is minor version(s) behind (^2.7.1 -> 2.9.0)
`yaml` is pinned/resolved at ^2.7.1 but the latest stable release on the npm registry is 2.9.0 (minor version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
packages/cli/package.json
low Security checks software dependencies conf 0.88 turbo: GHSA-3qcw-2rhx-2726
Turbo: Unexpected local code execution during Yarn Berry detection
bun.lock
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 18 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/cli/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/cli/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/cli/scripts/check-package.ts:40
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/cli/src/commands/diff.ts:72
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/cli/src/commands/export.ts:65
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/cli/src/commands/lint.ts:45
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/cli/src/commands/spec.ts:62
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/cli/src/linter/dtcg/conformance.test.ts:116
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/cli/src/linter/spec-gen/generate.ts:69
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
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/54fe7f94-d210-4e23-bb5b-fe185f71720a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/54fe7f94-d210-4e23-bb5b-fe185f71720a/

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.