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.

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

100.0% cov · 430 findings

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

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

Legacy markers 7 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

7 matching findings on this repo

low Old/deprecated-named symbol `bug_legacy` in tests/unit/test_analyze_tier_patter…
low Old/deprecated-named symbol `test_dialog_choice_2_use_legacy` in tests/unit/tes…
low Old/deprecated-named symbol `test_remembered_choice_legacy` in tests/unit/test_…
low Old/deprecated-named symbol `TestExecuteWithFallbackLegacy` in tests/unit/model…
low Old/deprecated-named symbol `TestWorkflowResponseLegacy` in tests/unit/mcp/hand…
low Old/deprecated-named symbol `via_legacy` in tests/unit/workflows/test_orchestra…
low Old/deprecated-named symbol `attune_config_legacy` in src/attune/config/__init_…

View all legacy markers findings →

Commented-out code 99 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (13 lines) in tests/conftest.py:46
info Commented-code block (8 lines) in tests/security/test_secrets_detector_edge_pat…
info Commented-code block (5 lines) in tests/integration/test_critical_workflows_smo…
info Commented-code block (8 lines) in tests/models/test_sonnet_opus_fallback.py:22
info Commented-code block (5 lines) in tests/unit/orchestration/test_tools_test_gene…
info Commented-code block (5 lines) in tests/unit/orchestration/test_tools_performan…
info Commented-code block (8 lines) in tests/unit/orchestration/test_composition_pat…
info Commented-code block (6 lines) in tests/unit/ops/test_sweep_results_server_wiri…
info Commented-code block (6 lines) in tests/unit/ops/test_telemetry_summary.py:21
info Commented-code block (5 lines) in tests/unit/ops/test_home.py:196
info Commented-code block (11 lines) in tests/unit/ops/test_run_meta_runner_integrat…
info Commented-code block (7 lines) in tests/unit/ops/test_persistence_and_history.p…

View all commented-out code findings →

Config drift 11 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

11 matching findings on this repo

high Agent instruction/config may expose a secret: plugin/skills/memory-and-context/… plugin/skills/memory-and-context/SKILL.md:104
high Agent instruction/config may expose a secret: .claude/lessons.md .claude/lessons.md:30
high Agent instruction/config may expose a secret: .claude/rules/attune/advanced-opt… .claude/rules/attune/advanced-optimization-plan.md:633
high Agent instruction/config may expose a secret: .claude/rules/attune/coding-stand… .claude/rules/attune/coding-standards-index.md:649
high Agent instruction/config may expose a secret: .claude/plans/feature-rag-code-gr… .claude/plans/feature-rag-code-grounding-2026-04-…:294
high Agent instruction/config may expose a secret: .claude/plans/feature-agent-sdk-0… .claude/plans/feature-agent-sdk-0163-uplift-2026-…:206
high Agent instruction/config may expose a secret: .claude/plans/archive/2026-04-09-… .claude/plans/archive/2026-04-09-plan-b-phase1-te…:13
low Old/deprecated-named symbol `env_backup` in tests/memory/test_redis_config.py:1…
low Old/deprecated-named symbol `attune_config_legacy` in src/attune/config/__init_…
info Commented-code block (5 lines) in src/attune/ops/config.py:33
info Commented-code block (7 lines) in src/attune/workflows/config.py:537

View all config drift findings →

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.