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.

terrene-foundation/envoy

https://github.com/terrene-foundation/envoy · scanned 2026-06-16 00:32 UTC (2 months, 2 weeks ago)

811 raw signals (61 security + 750 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 741 actionable findings from 2 signal sources. 198 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 · 732 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 141 Medium 341 Low 82 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 732 Crowd 0 Layer: Quality 502 Security 191 Software 11 Api 1 Frontend 32 Network 4

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 2 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.

2 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Commented-out code 169 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 (5 lines) in tests/integration/test_envelope_library_offli…
info Commented-code block (5 lines) in tests/integration/channels/test_redteam_r1_cl…
info Commented-code block (6 lines) in tests/integration/channels/test_discord_adapt…
info Commented-code block (7 lines) in tests/tier1/test_envoy_ledger_export_bundle.p…
info Commented-code block (5 lines) in tests/tier1/test_envoy_model_router.py:203
info Commented-code block (5 lines) in tests/tier1/test_shamir_distribution_checklis…
info Commented-code block (5 lines) in tests/tier1/test_envelope_compiler_pipeline.p…
info Commented-code block (5 lines) in tests/tier1/test_posture_gate_5_step_fail_clo…
info Commented-code block (5 lines) in tests/tier1/test_shamir_ritual_coordinator_or…
info Commented-code block (14 lines) in tests/tier1/test_kailash_rs_bindings_shape_p…
info Commented-code block (5 lines) in tests/tier1/test_trust_vault_lifecycle.py:270
info Commented-code block (6 lines) in tests/conformance/n4_n6_vectors.py:60

View all commented-out code findings →

Config drift 132 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.

12 matching findings on this repo

high Agent instruction/config may expose a secret: GEMINI.md GEMINI.md:582
high Agent instruction/config may expose a secret: AGENTS.md AGENTS.md:568
high Agent instruction/config may expose a secret: .claude/sync-manifest.yaml .claude/sync-manifest.yaml:466
high Agent instruction/config may expose a secret: .claude/rules/security.md .claude/rules/security.md:13
high Agent instruction/config may expose a secret: .claude/rules/llm-auth-strategy-h… .claude/rules/llm-auth-strategy-hygiene.md:25
high Agent instruction/config may expose a secret: .claude/rules/testing.md .claude/rules/testing.md:112
high Agent instruction/config may expose a secret: .claude/agents/codex-architect.md .claude/agents/codex-architect.md:43
high Agent instruction/config may expose a secret: .claude/agents/frameworks/align-s… .claude/agents/frameworks/align-specialist.md:147
high Agent instruction/config may expose a secret: .claude/skills/01-core-sdk/custom… .claude/skills/01-core-sdk/custom-node-guide.md:298
high Agent instruction/config may expose a secret: .claude/skills/01-core-sdk/enterp… .claude/skills/01-core-sdk/enterprise-infrastruct…:15
high Agent instruction/config may expose a secret: .claude/skills/01-core-sdk/python… .claude/skills/01-core-sdk/pythoncode-best-practi…:72
high Agent instruction/config may expose a secret: .claude/skills/01-core-sdk/produc… .claude/skills/01-core-sdk/production-readiness-p…:50

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/86ffcffd-1af8-41b1-bd74-0b509c763bf1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/86ffcffd-1af8-41b1-bd74-0b509c763bf1/

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.