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

ZIRAKU-SW/ai-media-prototype

https://github.com/ZIRAKU-SW/ai-media-prototype · scanned 2026-06-16 01:13 UTC (2 months, 1 week ago)

43 raw signals (0 security + 43 graph)

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

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 43 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
70.0
/100
Security checks
70
0 findings
System graph
70
100.0% cov · 43 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 0 Medium 25 Low 10 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 43 Crowd 0 Layer: Api 1 Frontend 8 Network 1 Security 10 Cicd 1 Quality 22
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 70.0/100 with 100.0% coverage. It contains 664 nodes across 4 cross-layer flows, written primarily in mixed languages. Engine surfaced 43 findings — concentrated in quality (22), security (10), frontend (8). Risk profile is high: 2 critical, 0 high, 25 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 37 of 43 actionable findings. 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 Secrets conf 1.00 Runtime dotenv file present in repo: .env
`.env` looks like a runtime dotenv file. It contains secret-looking assignments for VERCEL_TOKEN, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, SUPABASE_DB_PASSWORD, CURSOR_API_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.
.env ConfigEnv fileRuntime env
critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env.local
`.env.local` looks like a runtime dotenv file. It contains secret-looking assignments for NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, CURSOR_API_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.
.env.local ConfigEnv fileRuntime env
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — components/pages/ArticlePage.tsx:208
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 — components/pages/ThemeArticlePage.tsx:119
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 — packages/dev-console/src/client/DevConsoleClient.tsx:447
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 — packages/dev-console/src/client/DevConsoleMessageImages.tsx:14
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 — scripts/articles/upsert-articles.mjs:289
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 — scripts/x/article-media.ts:22
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 — scripts/x/post-articles.ts:27
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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/launch.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .cursor/rules/bug-registration.mdc
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.cursor/rules/bug-registration.mdc VerificationCursor rule
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, tests, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
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 security conf 1.00 Insecure pattern 'dangerous_innerhtml' in components/pages/ArticlePage.tsx:208
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
components/pages/ArticlePage.tsx:208 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in components/pages/ThemeArticlePage.tsx:119
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
components/pages/ThemeArticlePage.tsx:119 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in prototypes/pattern-a-wired/index.html:281
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
prototypes/pattern-a-wired/index.html:281 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in prototypes/pattern-b-notion/index.html:332
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
prototypes/pattern-b-notion/index.html:332 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in prototypes/pattern-c-zapier/index.html:328
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
prototypes/pattern-c-zapier/index.html:328 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in app/api/dev/health/route.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
app/api/dev/health/route.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/dev-console/src/server/chat.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/dev-console/src/server/chat.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/dev-console/src/server/deploy.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/dev-console/src/server/deploy.ts:1 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — ai_media_agent/dev_agent.py:65
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 32 placeholder/mock markers across 20 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 network Security conf 1.00 Privileged port 150 in use
Port 150 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/oceanosfleet/open-vm-firewall-for-oceanos.sh Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 111 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 17 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CURSOR_SDK_MODEL`, `DEV_CONSOLE_BACKEND_URL`, `DEV_CONSOLE_BUILD_SCRIPT`, `DEV_CONSOLE_PYTHON`, `NEXT_PUBLIC_BASE_PATH`, `NEXT_PUBLIC_SUPABASE_ANON_KEY`, `NEXT_PUBLIC_SUPABASE_URL`, `X_ACCESS_TOKEN` + 9 more. Add them (with a placeholder/comment) …
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 54 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 License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/dev-console/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/dev-console/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `prompt__copy` in components/ziraku/ZirakuMembersContent.tsx:71
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `sensor_dev_console_sessions_v1` in packages/dev-console/src/config.ts:33
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
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 — scripts/x/browser-post.ts:63
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 — scripts/x/post-articles.ts:244
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 — scripts/x/run-slot.ts:30
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/ab23353f-550e-4eb9-97d2-e40dd94bb4bf/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ab23353f-550e-4eb9-97d2-e40dd94bb4bf/

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.