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

chenyme/grok2api

https://github.com/chenyme/grok2api · scanned 2026-07-23 08:33 UTC (5 days, 9 hours ago)

74 raw signals (0 security + 74 graph)

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

Complete repo analysis

Last scanned 5 days, 9 hours ago · v4 · last Δ +4.0 (diff) · 57 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
Combined
69.1
/100
Security checks
69
0 findings
System graph
69
90.0% cov · 57 findings
Critical
2
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 2 High 1 Medium 16 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 57 Crowd 0 Layer: Frontend 19 Security 11 Hardware 4 Cicd 3 Quality 19 Dependencies 1
Scan summary Repository scanned at 69.1/100 with 90.0% coverage. It contains 1271 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 74 findings — concentrated in cicd (20), frontend (19), quality (19). Risk profile is high: 2 critical, 1 high, 27 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 39 of 57 actionable findings. 74 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 Trivy conf 1.00 CVE-2026-33815: github.com/jackc/pgx/v5 v5.6.0 — backend/go.mod
github.com/jackc/pgx/v5: github.com/jackc/pgx: Memory-safety vulnerability Memory-safety vulnerability in github.com/jackc/pgx/v5. Package: github.com/jackc/pgx/v5 Installed: v5.6.0 Fixed in: 5.9.0 Severity: CRITICAL Fix: Upgrade github.com/jackc/pgx/v5 to 5.9.0
VulnCve 2026 33815
critical System graph security Trivy conf 1.00 CVE-2026-33816: github.com/jackc/pgx/v5 v5.6.0 — backend/go.mod
github.com/jackc/pgx/v5: github.com/jackc/pgx: Memory-safety vulnerability Memory-safety vulnerability in github.com/jackc/pgx/v5. Package: github.com/jackc/pgx/v5 Installed: v5.6.0 Fixed in: 5.9.0 Severity: CRITICAL Fix: Upgrade github.com/jackc/pgx/v5 to 5.9.0
VulnCve 2026 33816
high System graph security Trivy conf 1.00 DS-0002: Image user should not be 'root' — Dockerfile
Image user should not be 'root' Specify at least 1 USER command in Dockerfile with non-root user as argument Rule: DS-0002 Severity: HIGH Target: Dockerfile
Misconfig
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/ui/chart.tsx:79
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/features/creative-console/creative-console-page.tsx:811
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/features/docs/api-docs-page.tsx:257
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/shared/api/client.ts:140
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security Trivy conf 1.00 CVE-2026-40898: github.com/quic-go/quic-go v0.59.0 — backend/go.mod
github.com/quic-go/quic-go: quic-go: Denial of Service via excessive memory allocation in HTTP/3 trailers quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.59.1, an attacker can cause excessive memory allocation in quic-go's HTTP/3 client and server implementations by sen…
VulnCve 2026 40898
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 12 occurrences GitHub Action is tag-pinned rather than SHA-pinned
github/codeql-action/init@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 12 locations
.github/workflows/ghcr-image.yml:49, 93, 96, 130, 141, 150, 157, 182, +2 more (10 hits)
.github/workflows/codeql.yml:41, 47 (2 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/ghcr-image.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 0.65 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/ui/chart.tsx:79
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/ui/chart.tsx:79 Dangerous innerhtml
medium System graph security security conf 0.65 Insecure pattern 'dangerous_innerhtml' in frontend/src/features/creative-console/creative-console-page.tsx:811
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/features/creative-console/creative-console-page.tsx:811 Dangerous innerhtml
medium System graph security security conf 0.65 Insecure pattern 'domparser_html_parse' in frontend/src/features/creative-console/creative-console-page.tsx:1043
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
frontend/src/features/creative-console/creative-console-page.tsx:1043 Domparser html parse
medium System graph security Semgrep conf 1.00 math random used — backend/internal/pkg/batch/executor.go:6
Do not use `math/rand`. Use `crypto/rand` instead. Rule: go.lang.security.audit.crypto.math_random.math-random-used Severity: WARNING OWASP: A02:2021 - Cryptographic Failures, A04:2025 - Cryptographic Failures CWE: CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) Catego…
SecurityGo
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 44 placeholder/mock markers across 17 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph security Semgrep conf 1.00 string formatted query — backend/internal/infra/persistence/relational/schema.go:228
String-formatted SQL query detected. This could lead to SQL injection if the string is not sanitized properly. Audit this call to ensure the SQL is not manipulable by external data. Rule: go.lang.security.audit.database.string-formatted-query.string-formatted-query Severity: WARNING OWASP: A01:201…
SecurityGo
low System graph security Trivy conf 1.00 CVE-2026-41889: github.com/jackc/pgx/v5 v5.6.0 — backend/go.mod
github.com/jackc/pgx: golang: pgx: SQL injection via specific SQL query conditions pgx is a PostgreSQL driver and toolkit for Go. Prior to version 5.9.2, SQL injection can occur when the non-default simple protocol is used, a dollar quoted string literal is used in the SQL query, that string liter…
VulnCve 2026 41889
low System graph dependencies dependencies conf 1.00 Dependency recharts is a major version behind
`recharts` is pinned at `2.15.4` in `frontend/package.json` while the latest release on the npm registry is `3.10.0` — 1 major version(s) behind. Old majors stop receiving security backports and accumulate known CVEs. Review the upstream changelog / migration guide and upgrade `recharts` to `3.10.0…
frontend/package.json FreshnessOutdated
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: alpine:${ALPINE_VERSION}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:45 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: golang:${GO_VERSION}-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:24 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:${NODE_VERSION}-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:4 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 7 locations
.github/workflows/ghcr-image.yml:27, 30, 54, 90, 127 (5 hits)
.github/workflows/codeql.yml:38
.github/workflows/stale.yml:19
CI/CD securitySupply chainGithub actions
low System graph quality Complexity conf 1.00 Very large file: backend/internal/application/account/service.go (2955 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/internal/application/gateway/service.go (1320 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/internal/application/gateway/service_test.go (2007 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/internal/infra/egress/manager.go (1701 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/internal/infra/egress/manager_test.go (1772 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/internal/infra/persistence/relational/account_repository.go (2039 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/internal/infra/provider/web/chat.go (2178 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/internal/infra/provider/web/image.go (1781 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/internal/infra/provider/web/protocol_test.go (1216 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/internal/transport/http/account/handler.go (1252 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/internal/transport/http/inference/handler.go (1661 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/features/accounts/accounts-page.tsx (1387 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/features/creative-console/creative-console-page.tsx (1123 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/shared/i18n/index.ts (1621 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/106a0e33-cf1c-47c3-a16c-59604f81e1e3/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/106a0e33-cf1c-47c3-a16c-59604f81e1e3/

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.