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

zensgit/metasheet2

https://github.com/zensgit/metasheet2 · scanned 2026-06-16 01:13 UTC (2 months, 1 week ago)

912 raw signals (0 security + 912 graph)

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

Complete repo analysis

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

JSON
Combined
34.8
/100
Security checks
35
0 findings
System graph
35
100.0% cov · 721 findings
Critical
6
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 6 High 84 Medium 162 Low 294 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 721 Crowd 0 Layer: Frontend 86 Network 31 Hardware 1 Security 133 Cicd 3 Quality 341 Api 126
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 34.8/100 with 100.0% coverage. It contains 22452 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 912 findings — concentrated in quality (341), cicd (189), security (138). Risk profile is high: 11 critical, 84 high, 195 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 472 of 721 actionable findings. 912 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 Secrets conf 1.00 3 occurrences Possible secret in .github/workflows/sqlserver-smoke.yml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 42, 43, 50
.github/workflows/sqlserver-smoke.yml:42, 43, 50 (3 hits)
critical System graph security Secrets conf 1.00 4 occurrences Possible secret in apps/web/src/router/types.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 43, 44, 420, 421
apps/web/src/router/types.ts:43, 44, 420, 421 (4 hits)
critical System graph security Secrets conf 1.00 Possible secret in apps/web/src/views/LoginView.vue
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
apps/web/src/views/LoginView.vue:154
critical System graph security Secrets conf 1.00 Possible secret in scripts/ops/multitable-onprem-preflight.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/ops/multitable-onprem-preflight.sh:552
critical System graph security Secrets conf 1.00 Possible secret in scripts/verify-multitable-live-smoke.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/verify-multitable-live-smoke.mjs:1014
critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: packages/core-backend/.env
`packages/core-backend/.env` looks like a runtime dotenv file. It contains secret-looking assignments for JWT_SECRET. Move real values to a secret manager and keep only `.env.example` style templates in source control.
packages/core-backend/.env ConfigEnv fileRuntime env
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/multitable/attachments/${attachmentId} (apps/web/src/multitable/api/client.ts:1393)
`apps/web/src/multitable/api/client.ts:1393` calls `DELETE /api/multitable/attachments/${attachmentId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/attachments/<p>` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/multitable/dingtalk-groups/${encodeURIComponent(id)}${qs(sheetId ? { sheetId } : {})} (apps/web/src/multitable/api/client.ts:1725)
`apps/web/src/multitable/api/client.ts:1725` calls `DELETE /api/multitable/dingtalk-groups/${encodeURIComponent(id)}${qs(sheetId ? { sheetId } : {})}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/dingta…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/multitable/fields/${fieldId} (apps/web/src/multitable/api/client.ts:1130)
`apps/web/src/multitable/api/client.ts:1130` calls `DELETE /api/multitable/fields/${fieldId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/fields/<p>` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/multitable/records/${recordId}${qs({ expectedVersion })} (apps/web/src/multitable/api/client.ts:1320)
`apps/web/src/multitable/api/client.ts:1320` calls `DELETE /api/multitable/records/${recordId}${qs({ expectedVersion })}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/records/<p>/<p>)}` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/multitable/sheets/${encodeURIComponent(sheetId)}/records/${encodeURIComponent(recordId)}/permissions/${encodeURIComponent(permissionId)} (apps/web/src/multitable/api/client.ts:1423)
`apps/web/src/multitable/api/client.ts:1423` calls `DELETE /api/multitable/sheets/${encodeURIComponent(sheetId)}/records/${encodeURIComponent(recordId)}/permissions/${encodeURIComponent(permissionId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Nor…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/multitable/tokens/${encodeURIComponent(tokenId)} (apps/web/src/multitable/api/client.ts:1648)
`apps/web/src/multitable/api/client.ts:1648` calls `DELETE /api/multitable/tokens/${encodeURIComponent(tokenId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/tokens/<p>` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/multitable/views/${viewId} (apps/web/src/multitable/api/client.ts:1159)
`apps/web/src/multitable/api/client.ts:1159` calls `DELETE /api/multitable/views/${viewId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/views/<p>` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/comments/inbox${qs(params ?? {})} (apps/web/src/multitable/api/client.ts:1582)
`apps/web/src/multitable/api/client.ts:1582` calls `GET /api/comments/inbox${qs(params ?? {})}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/comments/inbox${qs(params ` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/comments/mention-candidates${qs(params)} (apps/web/src/multitable/api/client.ts:1523)
`apps/web/src/multitable/api/client.ts:1523` calls `GET /api/comments/mention-candidates${qs(params)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/comments/mention-candidates/<p>` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/comments/mention-summary${qs(params)} (apps/web/src/multitable/api/client.ts:1567)
`apps/web/src/multitable/api/client.ts:1567` calls `GET /api/comments/mention-summary${qs(params)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/comments/mention-summary/<p>` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/ai/usage-summary (apps/web/src/multitable/api/client.ts:1250)
`apps/web/src/multitable/api/client.ts:1250` calls `GET /api/multitable/ai/usage-summary` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/ai/usage-summary` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/automation-executions${qs({ ...filters })} (apps/web/src/multitable/api/client.ts:1777)
`apps/web/src/multitable/api/client.ts:1777` calls `GET /api/multitable/automation-executions${qs({ ...filters })}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/automation-executions/<p>)}` If this poin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/bases (apps/web/src/multitable/api/client.ts:907)
`apps/web/src/multitable/api/client.ts:907` calls `GET /api/multitable/bases` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/bases` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/context${qs(params)} (apps/web/src/multitable/api/client.ts:947)
`apps/web/src/multitable/api/client.ts:947` calls `GET /api/multitable/context${qs(params)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/context/<p>` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/dingtalk-groups${qs(sheetId ? { sheetId } : {})} (apps/web/src/multitable/api/client.ts:1701)
`apps/web/src/multitable/api/client.ts:1701` calls `GET /api/multitable/dingtalk-groups${qs(sheetId ? { sheetId } : {})}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/dingtalk-groups${qs(sheetid ` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/dingtalk-groups/${encodeURIComponent(id)}/deliveries${qs(sheetId ? { sheetId } : {})} (apps/web/src/multitable/api/client.ts:1741)
`apps/web/src/multitable/api/client.ts:1741` calls `GET /api/multitable/dingtalk-groups/${encodeURIComponent(id)}/deliveries${qs(sheetId ? { sheetId } : {})}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitabl…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/fields${qs({ sheetId })} (apps/web/src/multitable/api/client.ts:1098)
`apps/web/src/multitable/api/client.ts:1098` calls `GET /api/multitable/fields${qs({ sheetId })}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/fields/<p>)}` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/fields/${fieldId}/link-options${qs(params ?? {})} (apps/web/src/multitable/api/client.ts:1365)
`apps/web/src/multitable/api/client.ts:1365` calls `GET /api/multitable/fields/${fieldId}/link-options${qs(params ?? {})}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/fields/<p>/link-options${qs(params…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/record-subscription-notifications${qs(params ?? {})} (apps/web/src/multitable/api/client.ts:1304)
`apps/web/src/multitable/api/client.ts:1304` calls `GET /api/multitable/record-subscription-notifications${qs(params ?? {})}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/record-subscription-notificatio…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/records-summary${qs(params as Record<string, string | number | boolean | undefined>)} (apps/web/src/multitable/api/client.ts:1373)
`apps/web/src/multitable/api/client.ts:1373` calls `GET /api/multitable/records-summary${qs(params as Record<string, string | number | boolean | undefined>)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitabl…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/records/${recordId}${qs(params ?? {})} (apps/web/src/multitable/api/client.ts:1265)
`apps/web/src/multitable/api/client.ts:1265` calls `GET /api/multitable/records/${recordId}${qs(params ?? {})}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/records/<p>${qs(params ` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/sheets (apps/web/src/multitable/api/client.ts:953)
`apps/web/src/multitable/api/client.ts:953` calls `GET /api/multitable/sheets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/charts (apps/web/src/multitable/api/client.ts:1823)
`apps/web/src/multitable/api/client.ts:1823` calls `GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/charts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets/<p>/charts` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/dashboards (apps/web/src/multitable/api/client.ts:1875)
`apps/web/src/multitable/api/client.ts:1875` calls `GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/dashboards` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets/<p>/dashboards` If this poin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/field-permissions (apps/web/src/multitable/api/client.ts:1013)
`apps/web/src/multitable/api/client.ts:1013` calls `GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/field-permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets/<p>/field-permissions…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/form-share-candidates${qs(params ?? {})} (apps/web/src/multitable/api/client.ts:1626)
`apps/web/src/multitable/api/client.ts:1626` calls `GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/form-share-candidates${qs(params ?? {})}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheet…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/permission-candidates${qs(params ?? {})} (apps/web/src/multitable/api/client.ts:976)
`apps/web/src/multitable/api/client.ts:976` calls `GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/permission-candidates${qs(params ?? {})}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/permissions (apps/web/src/multitable/api/client.ts:967)
`apps/web/src/multitable/api/client.ts:967` calls `GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets/<p>/permissions` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/records/${encodeURIComponent(recordId)}/permissions (apps/web/src/multitable/api/client.ts:1399)
`apps/web/src/multitable/api/client.ts:1399` calls `GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/records/${encodeURIComponent(recordId)}/permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/view-aggregate${qs(rest as Record<string, string | undefined>)} (apps/web/src/multitable/api/client.ts:1182)
`apps/web/src/multitable/api/client.ts:1182` calls `GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/view-aggregate${qs(rest as Record<string, string | undefined>)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/views/${encodeURIComponent(viewId)}/form-share (apps/web/src/multitable/api/client.ts:1600)
`apps/web/src/multitable/api/client.ts:1600` calls `GET /api/multitable/sheets/${encodeURIComponent(sheetId)}/views/${encodeURIComponent(viewId)}/form-share` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/templates (apps/web/src/multitable/api/client.ts:921)
`apps/web/src/multitable/api/client.ts:921` calls `GET /api/multitable/templates` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/templates` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/tokens (apps/web/src/multitable/api/client.ts:1633)
`apps/web/src/multitable/api/client.ts:1633` calls `GET /api/multitable/tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/tokens` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/view${qs(params as Record<string, string | number | boolean | undefined>)} (apps/web/src/multitable/api/client.ts:1173)
`apps/web/src/multitable/api/client.ts:1173` calls `GET /api/multitable/view${qs(params as Record<string, string | number | boolean | undefined>)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/view/<p>`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/multitable/views${qs({ sheetId })} (apps/web/src/multitable/api/client.ts:1136)
`apps/web/src/multitable/api/client.ts:1136` calls `GET /api/multitable/views${qs({ sheetId })}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/views/<p>)}` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://${addr.address}:${addr.port}/api/plugins (packages/core-backend/tests/unit/server-lifecycle.test.ts:31)
`packages/core-backend/tests/unit/server-lifecycle.test.ts:31` calls `GET http://${addr.address}:${addr.port}/api/plugins` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/http:/<p>:/<p>/api/plugins` If this …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8900/api/admin/users (packages/core-backend/src/routes/metrics-demo.ts:172)
`packages/core-backend/src/routes/metrics-demo.ts:172` calls `GET http://localhost:8900/api/admin/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8900/api/admin/users` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8900/api/admin/users (packages/core-backend/src/routes/metrics-demo.ts:184)
`packages/core-backend/src/routes/metrics-demo.ts:184` calls `GET http://localhost:8900/api/admin/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8900/api/admin/users` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8900/api/hr/employees (packages/core-backend/src/routes/metrics-demo.ts:191)
`packages/core-backend/src/routes/metrics-demo.ts:191` calls `GET http://localhost:8900/api/hr/employees` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8900/api/hr/employees` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8900/api/plugins (packages/core-backend/test-kanban-integration.js:6)
`packages/core-backend/test-kanban-integration.js:6` calls `GET http://localhost:8900/api/plugins` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8900/api/plugins` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8900/api/user/profile (packages/core-backend/src/routes/metrics-demo.ts:177)
`packages/core-backend/src/routes/metrics-demo.ts:177` calls `GET http://localhost:8900/api/user/profile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8900/api/user/profile` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8900/metrics/prom (plugins/hello-world/src/index.js:87)
`plugins/hello-world/src/index.js:87` calls `GET http://localhost:8900/metrics/prom` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8900/metrics/prom` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/multitable/dingtalk-groups/${encodeURIComponent(id)}${qs(sheetId ? { sheetId } : {})} (apps/web/src/multitable/api/client.ts:1716)
`apps/web/src/multitable/api/client.ts:1716` calls `PATCH /api/multitable/dingtalk-groups/${encodeURIComponent(id)}${qs(sheetId ? { sheetId } : {})}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/dingtal…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/multitable/fields/${fieldId} (apps/web/src/multitable/api/client.ts:1121)
`apps/web/src/multitable/api/client.ts:1121` calls `PATCH /api/multitable/fields/${fieldId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/fields/<p>` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/multitable/sheets/${encodeURIComponent(sheetId)}/automations/${encodeURIComponent(ruleId)} (apps/web/src/multitable/api/client.ts:1456)
`apps/web/src/multitable/api/client.ts:1456` calls `PATCH /api/multitable/sheets/${encodeURIComponent(sheetId)}/automations/${encodeURIComponent(ruleId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sh…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/multitable/sheets/${encodeURIComponent(sheetId)}/charts/${encodeURIComponent(chartId)} (apps/web/src/multitable/api/client.ts:1838)
`apps/web/src/multitable/api/client.ts:1838` calls `PATCH /api/multitable/sheets/${encodeURIComponent(sheetId)}/charts/${encodeURIComponent(chartId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/multitable/sheets/${encodeURIComponent(sheetId)}/views/${encodeURIComponent(viewId)}/form-share (apps/web/src/multitable/api/client.ts:1606)
`apps/web/src/multitable/api/client.ts:1606` calls `PATCH /api/multitable/sheets/${encodeURIComponent(sheetId)}/views/${encodeURIComponent(viewId)}/form-share` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitab…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/multitable/views/${viewId} (apps/web/src/multitable/api/client.ts:1150)
`apps/web/src/multitable/api/client.ts:1150` calls `PATCH /api/multitable/views/${viewId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/views/<p>` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/attachments (apps/web/src/multitable/api/client.ts:1384)
`apps/web/src/multitable/api/client.ts:1384` calls `POST /api/multitable/attachments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/attachments` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/automation/resume (apps/web/src/multitable/api/client.ts:1797)
`apps/web/src/multitable/api/client.ts:1797` calls `POST /api/multitable/automation/resume` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/automation/resume` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/bases (apps/web/src/multitable/api/client.ts:912)
`apps/web/src/multitable/api/client.ts:912` calls `POST /api/multitable/bases` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/bases` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/dingtalk-groups/${encodeURIComponent(id)}/test-send${qs(sheetId ? { sheetId } : {})} (apps/web/src/multitable/api/client.ts:1732)
`apps/web/src/multitable/api/client.ts:1732` calls `POST /api/multitable/dingtalk-groups/${encodeURIComponent(id)}/test-send${qs(sheetId ? { sheetId } : {})}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitabl…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/fields (apps/web/src/multitable/api/client.ts:1103)
`apps/web/src/multitable/api/client.ts:1103` calls `POST /api/multitable/fields` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/fields` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/patch (apps/web/src/multitable/api/client.ts:1339)
`apps/web/src/multitable/api/client.ts:1339` calls `POST /api/multitable/patch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/patch` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/person-fields/prepare (apps/web/src/multitable/api/client.ts:1112)
`apps/web/src/multitable/api/client.ts:1112` calls `POST /api/multitable/person-fields/prepare` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/person-fields/prepare` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/records (apps/web/src/multitable/api/client.ts:1310)
`apps/web/src/multitable/api/client.ts:1310` calls `POST /api/multitable/records` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/records` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/records/${recordId}/lock (apps/web/src/multitable/api/client.ts:1330)
`apps/web/src/multitable/api/client.ts:1330` calls `POST /api/multitable/records/${recordId}/lock` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/records/<p>/lock` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/sheets (apps/web/src/multitable/api/client.ts:958)
`apps/web/src/multitable/api/client.ts:958` calls `POST /api/multitable/sheets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/ai/shortcut/preview (apps/web/src/multitable/api/client.ts:1210)
`apps/web/src/multitable/api/client.ts:1210` calls `POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/ai/shortcut/preview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets/<p>/ai/shortcut/pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/ai/shortcut/run (apps/web/src/multitable/api/client.ts:1226)
`apps/web/src/multitable/api/client.ts:1226` calls `POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/ai/shortcut/run` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets/<p>/ai/shortcut/run` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/ai/suggest-formula (apps/web/src/multitable/api/client.ts:1239)
`apps/web/src/multitable/api/client.ts:1239` calls `POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/ai/suggest-formula` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets/<p>/ai/suggest-form…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/automations/${encodeURIComponent(ruleId)}/test (apps/web/src/multitable/api/client.ts:1748)
`apps/web/src/multitable/api/client.ts:1748` calls `POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/automations/${encodeURIComponent(ruleId)}/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitabl…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/charts (apps/web/src/multitable/api/client.ts:1829)
`apps/web/src/multitable/api/client.ts:1829` calls `POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/charts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets/<p>/charts` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/dashboards (apps/web/src/multitable/api/client.ts:1881)
`apps/web/src/multitable/api/client.ts:1881` calls `POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/dashboards` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets/<p>/dashboards` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/formula/dry-run (apps/web/src/multitable/api/client.ts:1193)
`apps/web/src/multitable/api/client.ts:1193` calls `POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/formula/dry-run` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/sheets/<p>/formula/dry-run` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/views/${encodeURIComponent(viewId)}/form-share/regenerate (apps/web/src/multitable/api/client.ts:1616)
`apps/web/src/multitable/api/client.ts:1616` calls `POST /api/multitable/sheets/${encodeURIComponent(sheetId)}/views/${encodeURIComponent(viewId)}/form-share/regenerate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/templates/${encodeURIComponent(templateId)}/dry-run (apps/web/src/multitable/api/client.ts:937)
`apps/web/src/multitable/api/client.ts:937` calls `POST /api/multitable/templates/${encodeURIComponent(templateId)}/dry-run` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/templates/<p>/dry-run` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/templates/${encodeURIComponent(templateId)}/install (apps/web/src/multitable/api/client.ts:926)
`apps/web/src/multitable/api/client.ts:926` calls `POST /api/multitable/templates/${encodeURIComponent(templateId)}/install` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/templates/<p>/install` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/tokens (apps/web/src/multitable/api/client.ts:1639)
`apps/web/src/multitable/api/client.ts:1639` calls `POST /api/multitable/tokens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/tokens` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/tokens/${encodeURIComponent(tokenId)}/rotate (apps/web/src/multitable/api/client.ts:1655)
`apps/web/src/multitable/api/client.ts:1655` calls `POST /api/multitable/tokens/${encodeURIComponent(tokenId)}/rotate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/tokens/<p>/rotate` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/multitable/views (apps/web/src/multitable/api/client.ts:1141)
`apps/web/src/multitable/api/client.ts:1141` calls `POST /api/multitable/views` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multitable/views` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/multitable/sheets/${encodeURIComponent(sheetId)}/field-permissions/${encodeURIComponent(fieldId)}/${encodeURIComponent(subjectType)}/${encodeURIComponent(subjectId)} (apps/web/src/multitable/api/client.ts:1043)
`apps/web/src/multitable/api/client.ts:1043` calls `PUT /api/multitable/sheets/${encodeURIComponent(sheetId)}/field-permissions/${encodeURIComponent(fieldId)}/${encodeURIComponent(subjectType)}/${encodeURIComponent(subjectId)}` but no backend route matches that path. This is a runtime 404 waiting t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/multitable/sheets/${encodeURIComponent(sheetId)}/permissions/${encodeURIComponent(subjectType)}/${encodeURIComponent(subjectId)} (apps/web/src/multitable/api/client.ts:987)
`apps/web/src/multitable/api/client.ts:987` calls `PUT /api/multitable/sheets/${encodeURIComponent(sheetId)}/permissions/${encodeURIComponent(subjectType)}/${encodeURIComponent(subjectId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/multitable/sheets/${encodeURIComponent(sheetId)}/records/${encodeURIComponent(recordId)}/permissions (apps/web/src/multitable/api/client.ts:1411)
`apps/web/src/multitable/api/client.ts:1411` calls `PUT /api/multitable/sheets/${encodeURIComponent(sheetId)}/records/${encodeURIComponent(recordId)}/permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/multi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/multitable/sheets/${encodeURIComponent(sheetId)}/records/${encodeURIComponent(recordId)}/subscriptions/me (apps/web/src/multitable/api/client.ts:1286)
`apps/web/src/multitable/api/client.ts:1286` calls `PUT /api/multitable/sheets/${encodeURIComponent(sheetId)}/records/${encodeURIComponent(recordId)}/subscriptions/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/multitable/views/${encodeURIComponent(viewId)}/permissions/${encodeURIComponent(subjectType)}/${encodeURIComponent(subjectId)} (apps/web/src/multitable/api/client.ts:1085)
`apps/web/src/multitable/api/client.ts:1085` calls `PUT /api/multitable/views/${encodeURIComponent(viewId)}/permissions/${encodeURIComponent(subjectType)}/${encodeURIComponent(subjectId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path …
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'eval_used' in packages/core-backend/src/gateway/redis-circuit-breaker-store.ts:372
Found a known-risky pattern (eval_used). Review and replace if possible.
packages/core-backend/src/gateway/redis-circuit-breaker-store.ts:372 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in packages/core-backend/src/integration/rate-limiting/redis-token-bucket-store.ts:160
Found a known-risky pattern (eval_used). Review and replace if possible.
packages/core-backend/src/integration/rate-limiting/redis-token-bucket-store.ts:160 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in packages/core-backend/src/multitable/redis-leader-lock.ts:38
Found a known-risky pattern (eval_used). Review and replace if possible.
packages/core-backend/src/multitable/redis-leader-lock.ts:38 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in apps/web/src/multitable/components/cells/MetaRichLongTextEditor.vue:12
Found a known-risky pattern (exec_used). Review and replace if possible.
apps/web/src/multitable/components/cells/MetaRichLongTextEditor.vue:12 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/core-backend/src/gateway/RateLimiter.ts:18
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/core-backend/src/gateway/RateLimiter.ts:18 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/core-backend/src/multitable/automation-service.ts:611
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/core-backend/src/multitable/automation-service.ts:611 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/core-backend/src/services/CacheService.ts:41
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/core-backend/src/services/CacheService.ts:41 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in scripts/ops/attendance-check-storage.sh:278
Found a known-risky pattern (exec_used). Review and replace if possible.
scripts/ops/attendance-check-storage.sh:278 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/web/src/multitable/api/client.ts:907
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 — apps/web/src/services/ViewManager.ts:287
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/core-backend/scripts/ops/yjs-node-client.mjs:36
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/core-backend/src/routes/automation.ts:296
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/core-backend/test-kanban-integration.js:6
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/attendance-ui-verify.mjs:10
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/seed-demo-data.ts:24
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, 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 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 cicd CI/CD security conf 1.00 30 occurrences GitHub Action is tag-pinned rather than SHA-pinned
pnpm/action-setup@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
12 files, 17 locations
.github/workflows/plugin-tests.yml:63, 89, 147, 322, 359 (5 hits)
.github/workflows/migration-replay.yml:31, 48 (2 hits)
.github/workflows/attendance-gate-contract-matrix.yml:34
.github/workflows/attendance-locale-zh-smoke-prod.yml:96
.github/workflows/attendance-onprem-package-build.yml:35
.github/workflows/attendance-strict-gates-prod.yml:293
.github/workflows/attendance-web-guard.yml:46
.github/workflows/docker-build.yml:30
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 5 occurrences 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.
5 files, 5 locations
.github/workflows/attendance-onprem-package-build.yml
.github/workflows/docker-build.yml
.github/workflows/multitable-onprem-package-build.yml
.github/workflows/phase5-nightly-validation-regression.yml
.github/workflows/phase5-threshold-update.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in packages/core-backend/src/gateway/APIGateway.ts:195
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
packages/core-backend/src/gateway/APIGateway.ts:195 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in packages/core-backend/src/server.js:91
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
packages/core-backend/src/server.js:91 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in packages/core-backend/src/services/CollabService.ts:245
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
packages/core-backend/src/services/CollabService.ts:245 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in packages/core-backend/src/services/MetricsStreamService.ts:107
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
packages/core-backend/src/services/MetricsStreamService.ts:107 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in apps/web/src/multitable/components/cells/MetaRichLongTextEditor.vue:239
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
apps/web/src/multitable/components/cells/MetaRichLongTextEditor.vue:239 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in apps/web/src/composables/useAuth.ts:179
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
apps/web/src/composables/useAuth.ts:179 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/attendance-ui-verify.mjs:20
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/attendance-ui-verify.mjs:20 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/profile-multitable-grid.mjs:281
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/profile-multitable-grid.mjs:281 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/verify-attendance-full-flow.mjs:181
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/verify-attendance-full-flow.mjs:181 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/verify-attendance-import-ui.mjs:73
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/verify-attendance-import-ui.mjs:73 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/verify-attendance-locale-zh-smoke.mjs:568
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/verify-attendance-locale-zh-smoke.mjs:568 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/verify-attendance-production-flow.mjs:204
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/verify-attendance-production-flow.mjs:204 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/verify-attendance-ui-regression.mjs:65
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/verify-attendance-ui-regression.mjs:65 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/verify-attendance-ui.mjs:375
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/verify-attendance-ui.mjs:375 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/verify-multitable-live-smoke.mjs:4263
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/verify-multitable-live-smoke.mjs:4263 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/verify-plm-ui-regression.sh:593
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/verify-plm-ui-regression.sh:593 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/verify-univer-ui-smoke.mjs:185
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/verify-univer-ui-smoke.mjs:185 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/core-backend/src/sandbox/ScriptSandbox.ts:332
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/core-backend/src/sandbox/ScriptSandbox.ts:332 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/openapi/dist-sdk/scripts/build.mjs:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/openapi/dist-sdk/scripts/build.mjs:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/advance-yjs-rollout-stack.mjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/advance-yjs-rollout-stack.mjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/attendance-daily-gate-report.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/attendance-daily-gate-report.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/capture-yjs-rollout-report.mjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/capture-yjs-rollout-report.mjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/check-pr-mainline-readiness.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/check-pr-mainline-readiness.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/check-pr-stack-readiness.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/check-pr-stack-readiness.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/check-yjs-retention-health.mjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/check-yjs-retention-health.mjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/dingtalk-alertmanager-closeout.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/dingtalk-alertmanager-closeout.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/dingtalk-p4-evidence-record.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/dingtalk-p4-evidence-record.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/dingtalk-p4-final-closeout.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/dingtalk-p4-final-closeout.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/dingtalk-p4-final-handoff.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/dingtalk-p4-final-handoff.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/dingtalk-p4-regression-gate.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/dingtalk-p4-regression-gate.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/dingtalk-p4-release-readiness.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/dingtalk-p4-release-readiness.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/dingtalk-p4-smoke-session.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/dingtalk-p4-smoke-session.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/dingtalk-work-notification-agent-id-apply.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/dingtalk-work-notification-agent-id-apply.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/dingtalk-work-notification-release-gate.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/dingtalk-work-notification-release-gate.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/github-actions-runtime-readiness.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/github-actions-runtime-readiness.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/integration-erp-plm-deploy-readiness.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/integration-erp-plm-deploy-readiness.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/integration-k3wise-onprem-preflight.mjs:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/integration-k3wise-onprem-preflight.mjs:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/multitable-dangling-link-sweep.mjs:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/multitable-dangling-link-sweep.mjs:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/multitable-phase3-release-gate.mjs:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/multitable-phase3-release-gate.mjs:28 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/run-yjs-rollout-gate.mjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/run-yjs-rollout-gate.mjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/set-dingtalk-alertmanager-webhook-secret.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/set-dingtalk-alertmanager-webhook-secret.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ops/staging-migration-alignment-report.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ops/staging-migration-alignment-report.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/verify-univer-ui-smoke.mjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/verify-univer-ui-smoke.mjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in apps/web/src/multitable/components/cells/MetaCellRenderer.vue:38
Found a known-risky pattern (vue_v_html). Review and replace if possible.
apps/web/src/multitable/components/cells/MetaCellRenderer.vue:38 Vue v html
medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in apps/web/src/multitable/components/cells/MetaRichLongTextRender.vue:14
Found a known-risky pattern (vue_v_html). Review and replace if possible.
apps/web/src/multitable/components/cells/MetaRichLongTextRender.vue:14 Vue v html
medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in apps/web/src/multitable/components/MetaRecordDrawer.vue:262
Found a known-risky pattern (vue_v_html). Review and replace if possible.
apps/web/src/multitable/components/MetaRecordDrawer.vue:262 Vue v html
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 443 placeholder/mock markers across 90 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 10 in use
Port 10 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/verify-plm-bom-tools.sh Ports
medium System graph network Security conf 1.00 Privileged port 11 in use
Port 11 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/phase5-demo-conclusion.sh Ports
medium System graph network Security conf 1.00 Privileged port 12 in use
Port 12 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/verify-plm-bom-tools.sh Ports
medium System graph network Security conf 1.00 Privileged port 15 in use
Port 15 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/verify-plm-bom-tools.sh Ports
medium System graph network Security conf 1.00 Privileged port 16 in use
Port 16 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 17 in use
Port 17 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 18 in use
Port 18 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/auto-checkpoints-scheduler.sh Ports
medium System graph network Security conf 1.00 Privileged port 19 in use
Port 19 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 20 in use
Port 20 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 21 in use
Port 21 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/auto-checkpoints-scheduler.sh Ports
medium System graph network Security conf 1.00 Privileged port 23 in use
Port 23 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/verify-plm-bom-tools.sh Ports
medium System graph network Security conf 1.00 Privileged port 24 in use
Port 24 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/verify-plm-bom-tools.sh Ports
medium System graph network Security conf 1.00 Privileged port 28 in use
Port 28 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/48h-checkpoint.sh Ports
medium System graph network Security conf 1.00 Privileged port 3 in use
Port 3 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/phase4-preflight-check.sh Ports
medium System graph network Security conf 1.00 Privileged port 30 in use
Port 30 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
ops/prometheus/phase5-alerts.yml Ports
medium System graph network Security conf 1.00 Privileged port 35 in use
Port 35 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/phase4-preflight-check.sh Ports
medium System graph network Security conf 1.00 Privileged port 38 in use
Port 38 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 4 in use
Port 4 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/phase5-threshold-update.yml Ports
medium System graph network Security conf 1.00 Privileged port 42 in use
Port 42 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 43 in use
Port 43 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 48 in use
Port 48 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 50 in use
Port 50 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/auto-checkpoints-scheduler.sh Ports
medium System graph network Security conf 1.00 Privileged port 51 in use
Port 51 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 54 in use
Port 54 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 55 in use
Port 55 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 57 in use
Port 57 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 58 in use
Port 58 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
output/playwright/attendance-rule-templates-snapshot.yml Ports
medium System graph network Security conf 1.00 Privileged port 6 in use
Port 6 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/attendance-import-perf-highscale.yml Ports
medium System graph network Security conf 1.00 Privileged port 9 in use
Port 9 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/phase5-demo-conclusion.sh Ports
medium System graph network Security conf 1.00 Privileged port 95 in use
Port 95 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
ops/prometheus/phase5-alerts.yml Ports
low System graph quality Integrity conf 1.00 497 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_READY_TIMEOUT`, `ADMIN_TOKEN`, `ADMIN_USER_ID`, `ALLOW_C5_SMOKE_CUSTOM_ORG_CLEANUP`, `ALLOW_C5_SMOKE_EXISTING_DUE_DELIVERIES`, `ALLOW_DB_RESET`, `ALLOW_EMPTY_RECORDS`, `ALLOW_EXISTING_A2_SYSTEM_SCOPE` + 489 more. Add them (with a placeholder…
config drift
low System graph quality Maintenance conf 1.00 65 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
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 1044 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 cicd CI/CD security conf 1.00 154 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.
12 files, 70 locations
.github/workflows/plugin-tests.yml:28, 31, 43, 55, 58, 81, 84, 107, +7 more (15 hits)
.github/workflows/attendance-import-perf-longrun.yml:140, 262, 265, 438, 463, 466, 471, 536, +1 more (9 hits)
.github/workflows/attendance-strict-gates-prod.yml:122, 249, 290, 298, 502, 524, 577 (7 hits)
.github/workflows/attendance-locale-zh-smoke-prod.yml:77, 102, 238, 284, 310, 359 (6 hits)
.github/workflows/attendance-daily-gate-dashboard.yml:75, 78, 91, 242, 395 (5 hits)
.github/workflows/attendance-import-perf-baseline.yml:143, 190, 193, 348, 369 (5 hits)
.github/workflows/attendance-import-perf-highscale.yml:129, 177, 180, 387, 409 (5 hits)
.github/workflows/observability-strict.yml:52, 57, 74, 87, 587 (5 hits)
CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/src/multitable/components/cells/MetaCellEditor.vue:197
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/src/multitable/components/MetaBasePicker.vue:55
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/src/multitable/components/MetaFormView.vue:234
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/src/multitable/components/MetaViewTabBar.vue:11
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/src/views/AfterSalesView.vue:2099
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/src/views/CalendarView.vue:249
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/src/views/FormView.vue:326
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/web/src/views/GalleryView.vue:56
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — packages/core-backend/src/components/workflow-designer/PropertyPanel.vue:5
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
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: apps/web/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.
apps/web/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/core-backend/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/core-backend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/mssql-readonly-utils/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/mssql-readonly-utils/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/openapi/dist-sdk/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/openapi/dist-sdk/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: plugins/plugin-attendance/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.
plugins/plugin-attendance/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: plugins/plugin-audit-logger/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.
plugins/plugin-audit-logger/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: plugins/plugin-integration-core/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.
plugins/plugin-integration-core/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: plugins/plugin-intelligent-restore/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.
plugins/plugin-intelligent-restore/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: plugins/plugin-telemetry-otel/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.
plugins/plugin-telemetry-otel/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: plugins/plugin-view-gantt/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.
plugins/plugin-view-gantt/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: tools/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.
tools/cli/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `asyncsend_v2` in packages/core-backend/src/integrations/dingtalk/client.ts:628
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 `asyncsend_v2` in packages/core-backend/tests/unit/dingtalk-work-notification.test.ts:102
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 `att_old` in apps/web/tests/multitable-attachment-editor.spec.ts:177
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 `att_old` in apps/web/tests/multitable-form-view.spec.ts:312
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 `att_old` in apps/web/tests/multitable-record-drawer.spec.ts:534
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 `attendance_overtime_segmentation_v1` in packages/core-backend/tests/integration/attendance-plugin.test.ts:5069
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 `attendance_overtime_segmentation_v1` in scripts/ops/staging-attendance-overtime-segmentation-o6-smoke.mjs:187
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 `audit_copy` in plugins/plugin-integration-core/__tests__/metasheet-multitable-target-adapter.test.cjs:161
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 `base_legacy` in apps/web/tests/multitable-grid.spec.ts:215
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 `base_legacy` in packages/core-backend/src/db/migrations/zzzz20260318110000_add_multitable_bases_and_permissions.ts:4
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 `base_legacy` in packages/core-backend/src/multitable/provisioning.ts:107
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 `base_legacy` in packages/core-backend/src/routes/univer-meta.ts:354
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 `base_legacy` in packages/core-backend/tests/integration/after-sales-registry-backfill.test.ts:134
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 `base_legacy` in packages/core-backend/tests/integration/multitable-context.api.test.ts:530
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 `base_legacy` in packages/core-backend/tests/integration/multitable-cross-base-seed-view-toctou.test.ts:9
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 `base_legacy` in packages/core-backend/tests/integration/multitable-cross-base-sheet-create-toctou.test.ts:221
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 `base_legacy` in packages/core-backend/tests/unit/after-sales-installer.test.ts:465
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 `base_legacy` in packages/core-backend/tests/unit/after-sales-plugin-routes.test.ts:286
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 `base_legacy` in packages/core-backend/tests/unit/attendance-report-field-catalog.test.ts:855
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 `base_legacy` in packages/core-backend/tests/unit/multitable-plugin-scope.test.ts:83
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 `base_legacy` in packages/core-backend/tests/unit/multitable-provisioning.test.ts:201
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 `base_legacy` in packages/core-backend/tests/unit/multitable-record-create-context.test.ts:7
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 `base_legacy` in packages/core-backend/tests/unit/multitable-records.test.ts:54
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 `base_legacy` in scripts/profile-multitable-grid.mjs:314
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 `base_legacy` in scripts/verify-multitable-live-smoke.mjs:4172
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 `dbLegacy` in plugins/plugin-integration-core/__tests__/db.test.cjs:247
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 `dt_legacy` in packages/core-backend/tests/unit/automation-v1.test.ts:763
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 `dt_legacy` in packages/core-backend/tests/unit/dingtalk-group-destination-service.test.ts:129
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 `fld_legacy` in packages/core-backend/tests/unit/multitable-formula-engine.test.ts:343
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 `fld_status_old` in packages/core-backend/tests/integration/multitable-view-config.api.test.ts:219
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 `k3_target_copy` in apps/web/tests/IntegrationWorkbenchView.spec.ts:921
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 `lead_legacy` in packages/core-backend/tests/unit/after-sales-workflow-adapter.test.ts:672
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 `listPendingApprovalsLegacy` in packages/openapi/dist-sdk/index.d.ts:431
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 `metasheet_v2` in packages/core-backend/test-persistence.js:10
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 `metasheet_v2` in test-persistence.js:94
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 `mt_col_widths_s1_v1` in apps/web/tests/multitable-phase3.spec.ts:38
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 `plm_stock_preparation_decision_v1` in plugins/plugin-integration-core/lib/stock-preparation-option-sync.cjs:39
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 `plm_stock_preparation_decision_v1` in plugins/plugin-integration-core/lib/stock-preparation-templates.cjs:469
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 `plmAuthLegacy` in apps/web/src/views/plm/usePlmAuthStatus.ts:55
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 `plmAuthLegacy` in apps/web/src/views/plm/usePlmProductPanel.ts:25
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 `plmAuthLegacy` in apps/web/tests/usePlmAuthStatus.spec.ts:36
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 `plmAuthLegacy` in apps/web/tests/usePlmProductPanel.spec.ts:56
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 `rbac_permission_cache_legacy` in scripts/ops/phase5-cache-hit-rate-contract.test.mjs:66
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 `req_old` in apps/web/tests/multitable-embed-host.spec.ts:499
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 `rule_legacy` in packages/core-backend/tests/unit/automation-scheduler-leader.test.ts:125
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 `sec_old` in packages/core-backend/tests/integration/multitable-record-restore.test.ts:240
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 `statusLegacy` in apps/web/tests/AutomationExecutionsView.spec.ts:17
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 `statusLegacy` in apps/web/tests/conditionBranchRunsView.spec.ts:17
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 `statusLegacy` in apps/web/tests/parallelBranchRunsView.spec.ts:17
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 `statusLegacy` in packages/core-backend/src/routes/automation.ts:86
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 `statusLegacy` in packages/core-backend/tests/unit/automation-runs-api.test.ts:80
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 `subscribePatternLegacy` in packages/core-backend/src/integration/messaging/message-bus.ts:306
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 `tenant_legacy` in packages/core-backend/tests/unit/jwt-middleware.test.ts:123
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 `unregisterOld` in packages/core-backend/tests/unit/attendance-scheduler.test.ts:120
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 `wf_copy` in packages/core-backend/tests/unit/workflow-designer-compile-preview-route.test.ts:222
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 `workflow_job_v1` in apps/web/src/multitable/types.ts:896
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 `workflow_job_v1` in apps/web/src/views/workflowDesignerPersistence.ts:738
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 `workflow_job_v1` in apps/web/tests/conditionBranchEditor.spec.ts:38
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 `workflow_job_v1` in apps/web/tests/multitable-automation-rule-editor.spec.ts:561
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 `workflow_job_v1` in apps/web/tests/multitable-client.spec.ts:233
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 `workflow_job_v1` in apps/web/tests/parallelBranchEditor.spec.ts:47
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 `workflow_job_v1` in apps/web/tests/workflowDesignerCompilePreview.spec.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 Integrity conf 1.00 Old/deprecated-named symbol `workflow_job_v1` in packages/core-backend/src/db/migrations/zzzz20260530120000_create_automation_jobs_and_execution_mode.ts:5
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 `workflow_job_v1` in packages/core-backend/src/db/migrations/zzzz20260603130000_create_automation_suspensions.ts:5
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 `workflow_job_v1` in packages/core-backend/src/db/types.ts:1340
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 `workflow_job_v1` in packages/core-backend/src/multitable/automation-actions.ts:155
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 `workflow_job_v1` in packages/core-backend/src/multitable/automation-executor.ts:581
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 `workflow_job_v1` in packages/core-backend/src/multitable/automation-job-service.ts:5
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 `workflow_job_v1` in packages/core-backend/src/multitable/automation-service.ts:77
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 `workflow_job_v1` in packages/core-backend/src/workflow/bpmnCompilePreview.ts:47
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 `workflow_job_v1` in packages/core-backend/tests/integration/multitable-automation-branch-local-wait.test.ts:119
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 `workflow_job_v1` in packages/core-backend/tests/integration/multitable-automation-jobs.test.ts:93
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 `workflow_job_v1` in packages/core-backend/tests/integration/multitable-automation-start-approval.test.ts:175
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 `workflow_job_v1` in packages/core-backend/tests/integration/multitable-automation-suspend-resume.test.ts:47
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 `workflow_job_v1` in packages/core-backend/tests/integration/multitable-cross-base-automation-write-rule.test.ts:100
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 `workflow_job_v1` in packages/core-backend/tests/unit/multitable-automation-service.test.ts:426
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 frontend Frontend quality conf 1.00 React Flow <Controls> without dark theming — packages/core-backend/src/components/workflow-designer/WorkflowDesigner.vue:74
`<Controls>` ships with white buttons. Override `.react-flow__controls` and `.react-flow__controls-button` in your stylesheet or pass a styled wrapper. Why: P1 in CHECKLIST.md — vendor defaults bleed light through. Rule id: fq.controls.no-bg
Fq controls no bg
low System graph frontend Frontend quality conf 1.00 React Flow <MiniMap> without dark background — packages/core-backend/src/components/workflow-designer/WorkflowDesigner.vue:69
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 — apps/web/src/views/CalendarView.vue:850
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 — apps/web/src/views/KanbanView.vue:196
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/core-backend/benchmark/pattern-matching.ts:326
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/core-backend/core/cache/CacheRegistry.d.ts:42
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/core-backend/core/cache/CacheRegistry.js:44
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/core-backend/core/cache/CacheRegistry.ts:46
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/core-backend/scripts/benchmark-messaging.ts:5
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/core-backend/scripts/config-reload.ts:12
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/core-backend/scripts/encrypt-dingtalk-integration-secrets.ts:83
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/core-backend/scripts/gen-dev-token.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/core-backend/scripts/init-default-views.ts:33
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/core-backend/scripts/kv-inspect.ts:55
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/core-backend/scripts/phase5-snapshot-migrate-and-restore.ts:39
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/core-backend/scripts/pre-merge-check.ts:43
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/core-backend/scripts/run-snapshot-migration.ts:17
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/core-backend/scripts/seed-rbac.ts:57
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

Showing first 300 of 472. Refine filters or use the findings page for deep search.

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/a57b657a-4689-429a-bec4-5c0b2159ab08/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a57b657a-4689-429a-bec4-5c0b2159ab08/

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.