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.

Taguchi-1989/GitOps

https://github.com/Taguchi-1989/GitOps · scanned 2026-06-16 00:28 UTC (2 months, 2 weeks ago)

67 raw signals (38 security + 29 graph)

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. 96 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 · 29 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 4 Medium 15 Low 10 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 29 Crowd 0 Layer: Quality 20 Security 5 Api 1 Frontend 8 Hardware 2 Cicd 1

Exclude dismissed / FP Exclude test files

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 68.6/100 with 100.0% coverage. It contains 1010 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 29 findings — concentrated in quality (13), frontend (8), security (4). Risk profile is high: 0 critical, 1 high, 12 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 31 of 37 actionable findings. 133 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 Security checks quality Practices conf 0.82 15 occurrences Foundry mined mock as real or placeholder: Taguchi-1989/GitOps

Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…

15 occurrences

repo-level (15 hits)

critical Security checks security auth conf 0.78 Foundry mined security auth guardrail gaps: Taguchi-1989/GitOps

Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…

high Security checks quality Practices conf 0.84 17 occurrences Foundry mined bad chains: Taguchi-1989/GitOps

Comment chain pattern product: bad_chains Repo: Taguchi-1989/GitOps Thread: Taguchi-1989/GitOps#8 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_has…

17 occurrences

repo-level (17 hits)

high Security checks quality Quality conf 0.76 4 occurrences Foundry mined schema ui api mismatch: Taguchi-1989/GitOps

Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_high_confidence_link Rep…

4 occurrences

repo-level (4 hits)

high Security checks quality Testing conf 0.78 13 occurrences Foundry mined test ci gap after feedback: Taguchi-1989/GitOps

Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_high_confi…

13 occurrences

repo-level (13 hits)

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/agents/backend.md

Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.

.claude/agents/backend.md:227 SecretsClaude instruction

medium Security checks quality Practices conf 0.62 8 occurrences Foundry mined assumption checks: Taguchi-1989/GitOps

Comment chain pattern product: assumption_checks Repo: Taguchi-1989/GitOps Thread: Taguchi-1989/GitOps#6 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_…

8 occurrences

repo-level (8 hits)

medium Security checks quality maintenance conf 0.70 28 occurrences Foundry mined blueprint gap alignment: Taguchi-1989/GitOps

Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …

28 occurrences

repo-level (28 hits)

medium Security checks quality Practices conf 0.70 18 occurrences Foundry mined unresolved feedback: Taguchi-1989/GitOps

Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: supp…

18 occurrences

repo-level (18 hits)

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/components/flow/MermaidViewer.tsx:273

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 — src/components/issue/ProposalCard.tsx:107

Fq dangerous html

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/app/issues/new/NewIssueForm.tsx:111

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 — src/components/flow/grid/FlowGridEditor.tsx:251

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 — src/components/issue/IssueDetail.tsx:163

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 instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing license. 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 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 src/components/flow/MermaidViewer.tsx:273

Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.

src/components/flow/MermaidViewer.tsx:273 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/issue/ProposalCard.tsx:107

Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.

src/components/issue/ProposalCard.tsx:107 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/next-build.js:1

Found a known-risky pattern (node_child_process). Review and replace if possible.

scripts/next-build.js:1 Node child process

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 40 placeholder/mock markers across 14 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 quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration

A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.

Runtime configService clientGenerated repo pattern

low System graph quality Integrity conf 1.00 15 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `ASSUMPTIONS_DIR`, `AUTH_DISABLED`, `DICT_DIR`, `FLOWS_DIR`, `GATES_DIR`, `GIT_MAIN_BRANCH`, `LLM_BASE_URL`, `LLM_JSON_MODE` + 7 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

Deployment

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 7 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:18-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 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 Integrity conf 1.00 Old/deprecated-named symbol `flow_v2` in src/lib/api-utils.test.ts:388

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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

low System graph frontend Frontend quality conf 1.00 React Flow <MiniMap> without dark background — src/components/flow/editor/FlowCanvas.tsx:165

A bare <MiniMap> renders with the vendor's white default in dark themes. Wrap the canvas in a class that overrides `.react-flow__minimap` background, or pass an explicit `style`/`maskColor`/`bgColor`. Why: P1 in CHECKLIST.md — vendor defaults bleed light through. Rule id: fq.minimap.no-bg

Fq minimap no bg

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 — prisma/seed.ts:32

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/c5f8f1fc-234e-41b0-85c5-9ff029cbde2b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c5f8f1fc-234e-41b0-85c5-9ff029cbde2b/

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.