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

Smart-AI-Memory/attune-ai

https://github.com/Smart-AI-Memory/attune-ai · scanned 2026-06-16 00:17 UTC (2 months, 2 weeks ago)

456 raw signals (0 security + 456 graph)

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

Complete repo analysis

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

JSON
Combined
44.9
/100
Security checks
45
0 findings
System graph
45
100.0% cov · 430 findings
Critical
5
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 5 High 83 Medium 84 Low 151 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 430 Crowd 0 Layer: Software 29 Frontend 28 Network 3 Hardware 2 Security 101 Cicd 2 Quality 198 Api 67
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 44.9/100 with 100.0% coverage. It contains 41870 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 456 findings — concentrated in quality (215), security (102), api (67). Risk profile is high: 6 critical, 83 high, 91 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 314 of 430 actionable findings. 456 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 security conf 1.00 Insecure pattern 'private_key_in_repo' in src/attune/memory/security/secrets_detector.py:186
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
src/attune/memory/security/secrets_detector.py:186 Private key in repo
critical System graph security security conf 1.00 Insecure pattern 'private_key_in_repo' in website/public/framework-docs/how-to/security-architecture/index.html:4387
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
website/public/framework-docs/how-to/security-architecture/index.html:4387 Private key in repo
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in src/attune/memory/security/secrets_detector.py
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
lines 40, 581
src/attune/memory/security/secrets_detector.py:40, 581 (2 hits)
critical System graph security Secrets conf 1.00 Possible secret in src/attune/memory/security/secrets_types.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/attune/memory/security/secrets_types.py:29
critical System graph security Secrets conf 1.00 Possible secret in website/public/framework-docs/how-to/security-architecture/index.html
Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.
website/public/framework-docs/how-to/security-architecture/index.html:4399
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/lessons.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/lessons.md:30 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/plans/feature-agent-sdk-0163-uplift-2026-04-19.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/plans/feature-agent-sdk-0163-uplift-2026-04-19.md:206 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/plans/feature-rag-code-grounding-2026-04-17.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/plans/feature-rag-code-grounding-2026-04-17.md:294 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/rules/attune/advanced-optimization-plan.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/rules/attune/advanced-optimization-plan.md:633 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/rules/attune/coding-standards-index.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/rules/attune/coding-standards-index.md:649 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: plugin/skills/memory-and-context/SKILL.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
plugin/skills/memory-and-context/SKILL.md:104 SecretsSkill file
high System graph quality Integrity conf 1.00 Blocking `httpx.get(...)` inside `async def call_api` — src/attune/resilience/retry.py:68
Sync I/O inside an async function blocks the event loop. While `httpx.get(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_threa…
src/attune/resilience/retry.py:68 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `time.sleep(...)` inside `async def run_stage` — examples/approval_gates_demo.py:258
Sync I/O inside an async function blocks the event loop. While `time.sleep(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_thre…
examples/approval_gates_demo.py:258 Sync io in asyncPerformance
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/costs?limit=10&days=7 (website/components/CostSavingsCard.tsx:65)
`website/components/CostSavingsCard.tsx:65` calls `GET /api/costs?limit=10&days=7` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/costs` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /help/search-index.json (attune-ai-dev/help/search.js:7)
`attune-ai-dev/help/search.js:7` calls `GET /help/search-index.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/help/search-index.json` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://${serverPrefix}.api.mailchimp.com/3.0/lists/${listId}/members/${emailHash} (website/lib/email/mailchimp.ts:98)
`website/lib/email/mailchimp.ts:98` calls `GET https://${serverPrefix}.api.mailchimp.com/3.0/lists/${listId}/members/${emailHash}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.api.mailchimp.com/3.0/list…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/${repo} (website/components/GitHubStarsBadge.tsx:18)
`website/components/GitHubStarsBadge.tsx:18` calls `GET https://api.github.com/repos/${repo}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/<p>` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/repos/${repo} (website/components/GitHubStats.tsx:26)
`website/components/GitHubStats.tsx:26` calls `GET https://api.github.com/repos/${repo}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/repos/<p>` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://${serverPrefix}.api.mailchimp.com/3.0/lists/${listId}/members/${emailHash} (website/lib/email/mailchimp.ts:140)
`website/lib/email/mailchimp.ts:140` calls `PATCH https://${serverPrefix}.api.mailchimp.com/3.0/lists/${listId}/members/${emailHash}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.api.mailchimp.com/3.0/l…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/contact (website/app/contact/page.tsx:95)
`website/app/contact/page.tsx:95` calls `POST /api/contact` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/contact` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/debug-wizard/analyze (website/components/debug-wizard/DebugWizard.tsx:533)
`website/components/debug-wizard/DebugWizard.tsx:533` calls `POST /api/debug-wizard/analyze` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/debug-wizard/analyze` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/newsletter (website/components/LeadMagnet.tsx:16)
`website/components/LeadMagnet.tsx:16` calls `POST /api/newsletter` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/newsletter` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/newsletter (website/components/NewsletterSignup.tsx:20)
`website/components/NewsletterSignup.tsx:20` calls `POST /api/newsletter` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/newsletter` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/wizards/invoke (website/components/WizardPlayground.tsx:65)
`website/components/WizardPlayground.tsx:65` calls `POST /api/wizards/invoke` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/wizards/invoke` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/wizards/sbar/enhance (website/components/SBARWizard.tsx:240)
`website/components/SBARWizard.tsx:240` calls `POST /api/wizards/sbar/enhance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/wizards/sbar/enhance` 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/wizards/sbar/generate (website/components/SBARWizard.tsx:353)
`website/components/SBARWizard.tsx:353` calls `POST /api/wizards/sbar/generate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/wizards/sbar/generate` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/wizards/sbar/medications (website/components/SBARWizard.tsx:306)
`website/components/SBARWizard.tsx:306` calls `POST /api/wizards/sbar/medications` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/wizards/sbar/medications` 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/wizards/sbar/priority (website/components/SBARWizard.tsx:278)
`website/components/SBARWizard.tsx:278` calls `POST /api/wizards/sbar/priority` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/wizards/sbar/priority` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/wizards/sbar/start (website/components/SBARWizard.tsx:179)
`website/components/SBARWizard.tsx:179` calls `POST /api/wizards/sbar/start` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/wizards/sbar/start` 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 https://${serverPrefix}.api.mailchimp.com/3.0/lists/${listId}/members (website/lib/email/mailchimp.ts:29)
`website/lib/email/mailchimp.ts:29` calls `POST https://${serverPrefix}.api.mailchimp.com/3.0/lists/${listId}/members` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.api.mailchimp.com/3.0/lists/<p>/member…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete_account` without auth dependency — backend/api/users.py:89
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/users.py:89 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_session` without auth dependency — backend/api/analysis.py:325
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/analysis.py:325 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `remove_team_member` without auth dependency — backend/api/subscriptions.py:132
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/subscriptions.py:132 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_team_member` without auth dependency — backend/api/subscriptions.py:110
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/subscriptions.py:110 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `analyze_file` without auth dependency — backend/api/analysis.py:193
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/analysis.py:193 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `analyze_project` without auth dependency — backend/api/analysis.py:162
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/analysis.py:162 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_session` without auth dependency — backend/api/analysis.py:110
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/analysis.py:110 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `deactivate_license` without auth dependency — backend/api/subscriptions.py:178
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/subscriptions.py:178 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `purchase_subscription` without auth dependency — backend/api/subscriptions.py:55
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/subscriptions.py:55 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh_token` without auth dependency — backend/api/auth.py:140
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/auth.py:140 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `validate_license` without auth dependency — backend/api/auth.py:184
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/auth.py:184 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_profile` without auth dependency — backend/api/users.py:44
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/users.py:44 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'eval_used' in .claude/CLAUDE.md:88
Found a known-risky pattern (eval_used). Review and replace if possible.
.claude/CLAUDE.md:88 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in attune-ai-dev/help/bug-predict/comparison.html:332
Found a known-risky pattern (eval_used). Review and replace if possible.
attune-ai-dev/help/bug-predict/comparison.html:332 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in attune-ai-dev/help/bug-predict/concept.html:283
Found a known-risky pattern (eval_used). Review and replace if possible.
attune-ai-dev/help/bug-predict/concept.html:283 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in attune-ai-dev/help/bug-predict/faq.html:285
Found a known-risky pattern (eval_used). Review and replace if possible.
attune-ai-dev/help/bug-predict/faq.html:285 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in attune-ai-dev/help/bug-predict/quickstart.html:275
Found a known-risky pattern (eval_used). Review and replace if possible.
attune-ai-dev/help/bug-predict/quickstart.html:275 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in attune-ai-dev/help/search-index.json:1
Found a known-risky pattern (eval_used). Review and replace if possible.
attune-ai-dev/help/search-index.json:1 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in attune-ai-dev/help/security-audit/concept.html:7
Found a known-risky pattern (eval_used). Review and replace if possible.
attune-ai-dev/help/security-audit/concept.html:7 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in attune-ai-dev/help/security-audit/faq.html:7
Found a known-risky pattern (eval_used). Review and replace if possible.
attune-ai-dev/help/security-audit/faq.html:7 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in docs/rag/ab-report-2026-04-19-sentinel-hybrid.json:19
Found a known-risky pattern (eval_used). Review and replace if possible.
docs/rag/ab-report-2026-04-19-sentinel-hybrid.json:19 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in docs/rag/ab-report-2026-04-19-sentinel-xml-attr.json:19
Found a known-risky pattern (eval_used). Review and replace if possible.
docs/rag/ab-report-2026-04-19-sentinel-xml-attr.json:19 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in docs/rag/ab-report-2026-04-19.json:18
Found a known-risky pattern (eval_used). Review and replace if possible.
docs/rag/ab-report-2026-04-19.json:18 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in plugin/hooks/security_guard.py:54
Found a known-risky pattern (eval_used). Review and replace if possible.
plugin/hooks/security_guard.py:54 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in plugin/README.md:60
Found a known-risky pattern (eval_used). Review and replace if possible.
plugin/README.md:60 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in plugin/skills/bug-predict/SKILL.md:60
Found a known-risky pattern (eval_used). Review and replace if possible.
plugin/skills/bug-predict/SKILL.md:60 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in plugin/skills/security-audit/SKILL.md:65
Found a known-risky pattern (eval_used). Review and replace if possible.
plugin/skills/security-audit/SKILL.md:65 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in src/attune/hooks/scripts/security_guard.py:46
Found a known-risky pattern (eval_used). Review and replace if possible.
src/attune/hooks/scripts/security_guard.py:46 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in src/attune/workflows/bug_predict_patterns.py:243
Found a known-risky pattern (eval_used). Review and replace if possible.
src/attune/workflows/bug_predict_patterns.py:243 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in src/attune/workflows/deep_review.py:68
Found a known-risky pattern (eval_used). Review and replace if possible.
src/attune/workflows/deep_review.py:68 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in src/attune/workflows/discovery_sweep/sources/pattern_scan.py:200
Found a known-risky pattern (eval_used). Review and replace if possible.
src/attune/workflows/discovery_sweep/sources/pattern_scan.py:200 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in website/public/framework-docs/CODING_STANDARDS/index.html:1819
Found a known-risky pattern (eval_used). Review and replace if possible.
website/public/framework-docs/CODING_STANDARDS/index.html:1819 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in website/public/framework-docs/reference/FAQ/index.html:6595
Found a known-risky pattern (eval_used). Review and replace if possible.
website/public/framework-docs/reference/FAQ/index.html:6595 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in .claude/CLAUDE.md:88
Found a known-risky pattern (exec_used). Review and replace if possible.
.claude/CLAUDE.md:88 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in attune-ai-dev/help/bug-predict/faq.html:285
Found a known-risky pattern (exec_used). Review and replace if possible.
attune-ai-dev/help/bug-predict/faq.html:285 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in attune-ai-dev/help/bug-predict/quickstart.html:276
Found a known-risky pattern (exec_used). Review and replace if possible.
attune-ai-dev/help/bug-predict/quickstart.html:276 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in attune-ai-dev/help/search-index.json:1
Found a known-risky pattern (exec_used). Review and replace if possible.
attune-ai-dev/help/search-index.json:1 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in attune-ai-dev/help/security-audit/concept.html:283
Found a known-risky pattern (exec_used). Review and replace if possible.
attune-ai-dev/help/security-audit/concept.html:283 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in attune-ai-dev/help/security-audit/faq.html:7
Found a known-risky pattern (exec_used). Review and replace if possible.
attune-ai-dev/help/security-audit/faq.html:7 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in docs/rag/ab-report-2026-04-19-sentinel-hybrid.json:99
Found a known-risky pattern (exec_used). Review and replace if possible.
docs/rag/ab-report-2026-04-19-sentinel-hybrid.json:99 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in docs/rag/ab-report-2026-04-19-sentinel-xml-attr.json:99
Found a known-risky pattern (exec_used). Review and replace if possible.
docs/rag/ab-report-2026-04-19-sentinel-xml-attr.json:99 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in docs/rag/ab-report-2026-04-19.json:93
Found a known-risky pattern (exec_used). Review and replace if possible.
docs/rag/ab-report-2026-04-19.json:93 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in plugin/hooks/security_guard.py:58
Found a known-risky pattern (exec_used). Review and replace if possible.
plugin/hooks/security_guard.py:58 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in plugin/README.md:60
Found a known-risky pattern (exec_used). Review and replace if possible.
plugin/README.md:60 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in plugin/skills/bug-predict/SKILL.md:60
Found a known-risky pattern (exec_used). Review and replace if possible.
plugin/skills/bug-predict/SKILL.md:60 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in plugin/skills/security-audit/SKILL.md:65
Found a known-risky pattern (exec_used). Review and replace if possible.
plugin/skills/security-audit/SKILL.md:65 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/attune/hooks/scripts/security_guard.py:50
Found a known-risky pattern (exec_used). Review and replace if possible.
src/attune/hooks/scripts/security_guard.py:50 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/attune/workflows/bug_predict_patterns.py:243
Found a known-risky pattern (exec_used). Review and replace if possible.
src/attune/workflows/bug_predict_patterns.py:243 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/attune/workflows/deep_review.py:68
Found a known-risky pattern (exec_used). Review and replace if possible.
src/attune/workflows/deep_review.py:68 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/attune/workflows/discovery_sweep/sources/pattern_scan.py:206
Found a known-risky pattern (exec_used). Review and replace if possible.
src/attune/workflows/discovery_sweep/sources/pattern_scan.py:206 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in website/public/framework-docs/CODING_STANDARDS/index.html:1819
Found a known-risky pattern (exec_used). Review and replace if possible.
website/public/framework-docs/CODING_STANDARDS/index.html:1819 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in website/public/framework-docs/reference/FAQ/index.html:6730
Found a known-risky pattern (exec_used). Review and replace if possible.
website/public/framework-docs/reference/FAQ/index.html:6730 Exec used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in website/public/framework-docs/assets/javascripts/lunr/wordcut.js:5977
Found a known-risky pattern (new_function_used). Review and replace if possible.
website/public/framework-docs/assets/javascripts/lunr/wordcut.js:5977 New function used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — website/app/blog/[slug]/page.tsx:79
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — website/app/blog/page.tsx:37
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — website/app/changelog/page.tsx:46
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — website/app/docs/page.tsx:95
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — website/app/faq/page.tsx:210
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — website/app/how-it-works/page.tsx:35
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — website/app/layout.tsx:47
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — website/app/page.tsx:48
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — website/app/pricing/page.tsx:53
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — website/components/Breadcrumbs.tsx:27
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — website/components/PlausibleAnalytics.tsx:16
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — attune-ai-dev/help/search.js:7
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/attune/ops/static/js/client_token.js:5
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/attune/ops/static/js/run_view.js:324
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/attune/ops/static/js/runner.js:532
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 — website/components/debug-wizard/DebugWizard.tsx:533
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 — website/components/SBARWizard.tsx:240
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 — website/components/telemetry/hooks/useTelemetryData.ts:126
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/mcp.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/mcp.json VerificationMcp config
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/plans/code-review-comparison.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/plans/code-review-comparison.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/rules/attune/documentation-patterns.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/rules/attune/documentation-patterns.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/rules/attune/vscode-extension-limitations.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/rules/attune/vscode-extension-limitations.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/settings.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/agent/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/agent/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/bulk/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/bulk/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/dev/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/dev/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/pipeline/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/pipeline/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/plan/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/plan/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/simplify/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/simplify/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/utilities/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/utilities/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/workflows/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/workflows/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .mcp.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.mcp.json VerificationMcp config
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugin/.mcp.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
plugin/.mcp.json VerificationMcp config
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugin/skills/bug-predict/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
plugin/skills/bug-predict/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugin/skills/doc-gen/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
plugin/skills/doc-gen/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugin/skills/refactor-plan/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
plugin/skills/refactor-plan/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugin/skills/security-audit/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
plugin/skills/security-audit/SKILL.md VerificationSkill file
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 8 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.
8 files, 8 locations
.github/workflows/build-help-site.yml
.github/workflows/dependabot-auto-merge.yml
.github/workflows/docs.yml
.github/workflows/help-freshness.yml
.github/workflows/publish-pypi.yml
.github/workflows/release.yml
.github/workflows/scorecard.yml
.github/workflows/tier-pattern-analysis.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in website/app/blog/[slug]/page.tsx:79
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
website/app/blog/[slug]/page.tsx:79 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in website/app/blog/page.tsx:37
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
website/app/blog/page.tsx:37 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in website/app/changelog/page.tsx:46
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
website/app/changelog/page.tsx:46 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in website/app/docs/page.tsx:95
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
website/app/docs/page.tsx:95 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in website/app/faq/page.tsx:210
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
website/app/faq/page.tsx:210 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in website/app/how-it-works/page.tsx:35
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
website/app/how-it-works/page.tsx:35 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in website/app/layout.tsx:47
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
website/app/layout.tsx:47 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in website/app/page.tsx:48
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
website/app/page.tsx:48 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in website/app/pricing/page.tsx:53
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
website/app/pricing/page.tsx:53 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in website/components/Breadcrumbs.tsx:27
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
website/components/Breadcrumbs.tsx:27 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in website/components/PlausibleAnalytics.tsx:16
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
website/components/PlausibleAnalytics.tsx:16 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in attune-ai-dev/help/search.js:11
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
attune-ai-dev/help/search.js:11 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in deployments/wizards-backend/static/index.html:279
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
deployments/wizards-backend/static/index.html:279 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/attune/ops/static/js/bulletin.js:96
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/attune/ops/static/js/bulletin.js:96 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/attune/ops/static/js/completion_candidates.js:228
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/attune/ops/static/js/completion_candidates.js:228 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/attune/ops/static/js/run_view.js:944
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/attune/ops/static/js/run_view.js:944 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/attune/ops/static/js/workflows_kebab.js:61
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/attune/ops/static/js/workflows_kebab.js:61 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in website/public/framework-docs/assets/javascripts/bundle.e71a0d61.min.js:14
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
website/public/framework-docs/assets/javascripts/bundle.e71a0d61.min.js:14 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in website/public/framework-docs/assets/javascripts/bundle.e71a0d61.min.js:14
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
website/public/framework-docs/assets/javascripts/bundle.e71a0d61.min.js:14 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in plugin/hooks/security_guard.py:66
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
plugin/hooks/security_guard.py:66 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in scripts/phase_2_setup.py:357
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
scripts/phase_2_setup.py:357 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in src/attune/hooks/scripts/security_guard.py:58
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
src/attune/hooks/scripts/security_guard.py:58 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in src/attune/workflows/discovery_sweep/sources/pattern_scan.py:212
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
src/attune/workflows/discovery_sweep/sources/pattern_scan.py:212 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in attune-ai-dev/help/security-audit/concept.html:303
Found a known-risky pattern (weak_hash). Review and replace if possible.
attune-ai-dev/help/security-audit/concept.html:303 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in attune-ai-dev/help/security-audit/faq.html:308
Found a known-risky pattern (weak_hash). Review and replace if possible.
attune-ai-dev/help/security-audit/faq.html:308 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in docs/rag/ab-report-2026-04-19-sentinel-hybrid.json:179
Found a known-risky pattern (weak_hash). Review and replace if possible.
docs/rag/ab-report-2026-04-19-sentinel-hybrid.json:179 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in docs/rag/ab-report-2026-04-19-sentinel-xml-attr.json:179
Found a known-risky pattern (weak_hash). Review and replace if possible.
docs/rag/ab-report-2026-04-19-sentinel-xml-attr.json:179 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in docs/rag/ab-report-2026-04-19.json:168
Found a known-risky pattern (weak_hash). Review and replace if possible.
docs/rag/ab-report-2026-04-19.json:168 Weak hash
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/batch10_workflow.py:64
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/launch_autonomous_test_gen.py:29
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/phase_2_setup.py:357
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/qa_post_release.py:64
`subprocess.check_output(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/run_tests.py:50
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/attune/project_index/index.py:304
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/attune/prompts/examples.py:26
`subprocess.check_output(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/attune/workflows/agent_sdk_adapter.py:770
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 275 placeholder/mock markers across 109 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 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.
attune.config.yml Ports
medium System graph network Security conf 1.00 Privileged port 29 in use
Port 29 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
attune.config.yml Ports
medium System graph network Security conf 1.00 Privileged port 7 in use
Port 7 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/integration-auth.yml Ports
low System graph quality Maintenance conf 1.00 160 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Integrity conf 1.00 98 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALLOWED_ORIGINS`, `AMS_BASE_URL`, `AMS_NAMESPACE`, `ANTHROPIC_ADMIN_API_KEY`, `ANTHROPIC_COST_CACHE_TTL_SECONDS`, `APPDATA`, `ATTUNE_AGENT_MODEL_DEFAULT`, `ATTUNE_AI_CHARS_PER_TOKEN` + 90 more. Add them (with a placeholder/comment) to .env.example…
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 6001 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: mcr.microsoft.com/devcontainers/python:1-3.11-bullseye
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
.devcontainer/Dockerfile:3 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 2 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.
lines 17, 20
website/.github/workflows/deploy.yml:17, 20 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 15 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: plugin/hooks/_sdk_gate.py:is_sdk_subprocess, src/attune/hooks/scripts/_sdk_gate.py:is_sdk_subprocess This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they'r…
15 occurrences
repo-level (15 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: scripts/simple_todo_impl.py:find_test_files, scripts/run_test_todo_implementation.py:find_test_files_with_todos, scripts/run_todo_implementation_workflow.py:find_test_files_with_todos This is *the* AI-coder failure mode (4× more duplication in vibe-c…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: examples/coordinated_workflow_demo.py:run_stage, examples/coordinated_workflow_demo.py:run_stage, examples/coordinated_workflow_demo.py:run_stage, examples/coordinated_workflow_demo.py:run_stage This is *the* AI-coder failure mode (4× more duplicatio…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_also_unused` in tests/golden_files/simplify/over_engineered/input.py:96
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 `agent1_copy` in tests/agents_md/test_loader.py:152
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 `analysis_v1` in examples/redis_exploration.py:104
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 `analysis_v1` in src/attune/memory/short_term/working.py:124
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 `analysis_v1` in src/attune/redis_memory_storage.py:158
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 `analyzer_v1` in tests/unit/memory/test_short_term.py:183
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 `attune_config_legacy` in src/attune/config/__init__.py:30
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 `bug_legacy` in tests/unit/test_analyze_tier_patterns.py:413
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 `days_old` in src/attune/patterns/contextual.py:227
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 `env_backup` in tests/memory/test_redis_config.py:188
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 `env_backup` in tests/unit/agents/release/test_release_models.py:364
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 `env_backup` in tests/unit/meta_workflows/test_llm_execution.py:457
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 `is_deprecated` in src/attune/workflows/migration.py:355
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 `no_backup` in scripts/migrate_workflow_history.py:188
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 `test_dialog_choice_2_use_legacy` in tests/unit/test_coverage_batch7.py:1212
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 `test_get_conversation_history_returns_copy` in tests/agent_factory/test_base.py:345
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 `test_get_conversation_history_returns_copy` in tests/agent_factory/test_native_adapter.py:232
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 `test_get_platform_info_returns_copy` in tests/core/test_platform_utils.py:402
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 `test_get_state_returns_copy` in tests/unit/help/test_session.py:69
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 `test_load_cached_advisories_warns_when_cache_old` in tests/unit/workflows/test_dependency_check_audit.py:62
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 `test_old` in tests/unit/workflows/test_test_maintenance.py:285
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 `test_output_schema_returns_copy` in tests/unit/curator/test_prompt_schema.py:71
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_pattern_v2` in tests/unit/memory/test_control_panel.py:62
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 `test_remembered_choice_legacy` in tests/unit/test_workflow_migration.py:163
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 `test_stale_when_last_modified_is_old` in tests/unit/ops/test_spec_lifecycle.py:209
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 `TestExecuteWithFallbackLegacy` in tests/unit/models/test_resilient_executor_coverage.py: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 `TestLoadWorkflowHistoryDeprecated` in tests/unit/test_coverage_batch17.py:79
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 `TestWorkflowResponseLegacy` in tests/unit/mcp/handlers/test_workflow_response.py:103
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 `TestWorkingMemoryReadIsNotDeprecated` in attune_redis/tests/test_memory.py:147
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 `via_legacy` in tests/unit/workflows/test_orchestrated_health_check.py:786
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 `wizard_v2` in tests/unit/test_generator/test_cli.py:803
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 software Dead code conf 1.00 Possibly dead Python function: benchmark_comparison
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/profile_utils.py:138
low System graph software Dead code conf 1.00 Possibly dead Python function: build_all
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/build_docs.py:177
low System graph software Dead code conf 1.00 Possibly dead Python function: check_agent_templates
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:109
low System graph software Dead code conf 1.00 Possibly dead Python function: check_anticipation_window
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agents/compliance_anticipation_agent.py:456
low System graph software Dead code conf 1.00 Possibly dead Python function: check_attune_ai_version
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:47
low System graph software Dead code conf 1.00 Possibly dead Python function: check_attune_cli_help
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:146
low System graph software Dead code conf 1.00 Possibly dead Python function: check_attune_help_cli
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:157
low System graph software Dead code conf 1.00 Possibly dead Python function: check_attune_help_in_attune_ai
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:218
low System graph software Dead code conf 1.00 Possibly dead Python function: check_attune_help_version
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:55
low System graph software Dead code conf 1.00 Possibly dead Python function: check_core_imports
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:79
low System graph software Dead code conf 1.00 Possibly dead Python function: check_help_engine_init
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:120
low System graph software Dead code conf 1.00 Possibly dead Python function: check_help_engine_renderers
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:126
low System graph software Dead code conf 1.00 Possibly dead Python function: check_help_engine_session
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:134
low System graph software Dead code conf 1.00 Possibly dead Python function: check_mcp_imports
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:99
low System graph software Dead code conf 1.00 Possibly dead Python function: check_mcp_server_imports
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:197
low System graph software Dead code conf 1.00 Possibly dead Python function: check_path_validation_blocks_null_bytes
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:184
low System graph software Dead code conf 1.00 Possibly dead Python function: check_path_validation_blocks_traversal
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:174
low System graph software Dead code conf 1.00 Possibly dead Python function: check_pip_shows_correct_versions
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:63
low System graph software Dead code conf 1.00 Possibly dead Python function: check_wizard_registry
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:91
low System graph software Dead code conf 1.00 Possibly dead Python function: check_workflow_registry
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/qa_post_release.py:83
low System graph software Dead code conf 1.00 Possibly dead Python function: decorator
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/profile_utils.py:33
low System graph software Dead code conf 1.00 Possibly dead Python function: instrumented
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/phase0/measure.py:60
low System graph software Dead code conf 1.00 Possibly dead Python function: predict_next_audit
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agents/compliance_anticipation_agent.py:349
low System graph software Dead code conf 1.00 Possibly dead Python function: print_benchmark_results
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/profile_utils.py:189
low System graph software Dead code conf 1.00 Possibly dead Python function: profile_memory
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/profile_utils.py:88
low System graph software Dead code conf 1.00 Possibly dead Python function: replace_todo
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/simple_todo_impl.py:46
low System graph software Dead code conf 1.00 Possibly dead Python function: should_anticipate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agents/compliance_anticipation_agent.py:538
low System graph software Dead code conf 1.00 Possibly dead Python function: visit_ClassDef
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/ast_api_extractor.py:49
low System graph software Dead code conf 1.00 Possibly dead Python function: visit_FunctionDef
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/ast_api_extractor.py:123
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 — website/app/api/contact/route.ts:28
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 — website/app/api/newsletter/route.ts:29
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 — website/app/api/og/route.tsx: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 — website/app/api/webhooks/vercel/route.ts:86
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 — website/lib/db.ts:140
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 — website/lib/email/mailchimp.ts:24
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 — website/lib/email/sendgrid.ts:53
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 — website/lib/logger.ts:86
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 — website/lib/redis.ts:103
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 — website/public/framework-docs/assets/javascripts/lunr/wordcut.js:6636
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 quality Integrity conf 1.00 Stub function `check_core_imports` (body is just `pass`/`return`) — scripts/qa_post_release.py:79
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /account
`backend/api/users.py` declares `DELETE /account` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /session/{session_id}
`backend/api/analysis.py` declares `DELETE /session/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /team/members/{user_id}
`backend/api/subscriptions.py` declares `DELETE /team/members/{user_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`deployments/wizards-backend/app.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/health
`backend/main.py` declares `GET /api/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/info
`backend/main.py` declares `GET /api/info` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/wizards/{wizard_id}
`backend/api/wizards.py` declares `GET /api/wizards/{wizard_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /completion-candidates
`src/attune/ops/routes/specs.py` declares `GET /completion-candidates` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /demo
`deployments/wizards-backend/routers/inspect.py` declares `GET /demo` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /formats
`deployments/wizards-backend/routers/inspect.py` declares `GET /formats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /help
`src/attune/ops/routes/dashboard.py` declares `GET /help` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /help/admin
`src/attune/ops/routes/dashboard.py` declares `GET /help/admin` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /help/search
`src/attune/ops/routes/dashboard.py` declares `GET /help/search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /help/{feature}
`src/attune/ops/routes/dashboard.py` declares `GET /help/{feature}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /help/{feature}/{kind}
`src/attune/ops/routes/dashboard.py` declares `GET /help/{feature}/{kind}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /history
`backend/api/analysis.py` declares `GET /history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /licenses
`backend/api/subscriptions.py` declares `GET /licenses` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /live
`deployments/wizards-backend/routers/health.py` declares `GET /live` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /me
`backend/api/auth.py` declares `GET /me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /profile
`backend/api/users.py` declares `GET /profile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /ready
`deployments/wizards-backend/routers/health.py` declares `GET /ready` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /runs/{run_id}/view
`src/attune/ops/routes/dashboard.py` declares `GET /runs/{run_id}/view` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /session/{session_id}
`backend/api/analysis.py` declares `GET /session/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /sessions
`src/attune/ops/routes/dashboard.py` declares `GET /sessions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /specs
`src/attune/ops/routes/dashboard.py` declares `GET /specs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /team
`backend/api/subscriptions.py` declares `GET /team` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /usage
`backend/api/users.py` declares `GET /usage` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /workflows
`src/attune/ops/routes/dashboard.py` declares `GET /workflows` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{slug}
`src/attune/ops/routes/specs.py` declares `GET /{slug}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{{wizard_id}}/report
`patterns/structural.py` declares `GET /{{wizard_id}}/report` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /file
`backend/api/analysis.py` declares `POST /file` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /licenses/{license_id}/deactivate
`backend/api/subscriptions.py` declares `POST /licenses/{license_id}/deactivate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /login
`backend/api/auth.py` declares `POST /login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /project
`backend/api/analysis.py` declares `POST /project` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /purchase
`backend/api/subscriptions.py` declares `POST /purchase` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /quick
`deployments/wizards-backend/routers/inspect.py` declares `POST /quick` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /refresh
`backend/api/auth.py` declares `POST /refresh` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /register
`backend/api/auth.py` declares `POST /register` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /run
`deployments/wizards-backend/routers/inspect.py` declares `POST /run` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /session
`backend/api/analysis.py` declares `POST /session` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /start
`patterns/empathy.py` declares `POST /start` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /team/members
`backend/api/subscriptions.py` declares `POST /team/members` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /validate-license
`backend/api/auth.py` declares `POST /validate-license` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{slug}/completion-candidates/dismiss
`src/attune/ops/routes/specs.py` declares `POST /{slug}/completion-candidates/dismiss` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{{wizard_id}}/enhance
`patterns/behavior.py` declares `POST /{{wizard_id}}/enhance` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{{wizard_id}}/preview
`patterns/empathy.py` declares `POST /{{wizard_id}}/preview` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{{wizard_id}}/save
`patterns/validation.py` declares `POST /{{wizard_id}}/save` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{{wizard_id}}/step
`patterns/structural.py` declares `POST /{{wizard_id}}/step` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /profile
`backend/api/users.py` declares `PUT /profile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /{slug}/{phase}/status
`src/attune/ops/routes/specs.py` declares `PUT /{slug}/{phase}/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: agents/book_production/learning.py (1373 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: agents/compliance_anticipation_agent.py (1423 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/attune/workflows/agent_sdk_adapter.py (1615 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/cli_commands/test_telemetry_commands.py (1706 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/orchestration/test_execution_strategies.py (1815 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/socratic/test_mcp_server.py (1461 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.

Showing first 300 of 314. 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/9b374769-5422-4788-8d44-189b8a865960/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9b374769-5422-4788-8d44-189b8a865960/

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.