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

qx04222/mailpulse

https://github.com/qx04222/mailpulse · scanned 2026-06-15 23:44 UTC (2 months, 4 weeks ago)

130 raw signals (0 security + 130 graph)

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

Complete repo analysis

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

JSON
Combined
62.5
/100
Security checks
63
0 findings
System graph
63
88.9% cov · 119 findings
Critical
2
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 2 High 1 Medium 18 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 119 Crowd 0 Layer: Software 5 Api 1 Frontend 16 Security 4 Cicd 3 Quality 90
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 62.5/100 with 88.9% coverage. It contains 5129 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 130 findings — concentrated in quality (93), frontend (16), cicd (11). Risk profile is high: 2 critical, 1 high, 23 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 40 of 119 actionable findings. 130 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 Possible secret in admin/e2e/helpers.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
admin/e2e/helpers.ts:3
critical System graph security Secrets conf 1.00 Possible secret in admin/playwright.config.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
admin/playwright.config.ts:40
high System graph quality Integrity conf 1.00 Blocking `httpx.post(...)` inside `async def _broadcast_file` — engine/src/bot/lark_callback.py:895
Sync I/O inside an async function blocks the event loop. While `httpx.post(...)` 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…
engine/src/bot/lark_callback.py:895 Sync io in asyncPerformance
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — admin/src/app/layout.tsx:40
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 — admin/src/app/dashboard/companies/page.tsx:307
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 — admin/src/app/dashboard/layout.tsx:194
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 — admin/src/app/dashboard/notifications/page.tsx:331
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 — admin/src/app/dashboard/sla/page.tsx:328
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 — admin/src/app/dashboard/templates/page.tsx:280
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 — admin/src/lib/fetcher.ts:3
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 — admin/src/lib/lark.ts:10
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — admin/src/test/live-probes.integration.test.ts:56
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 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 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
anthropics/claude-code-action@v1 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 3 locations
.github/workflows/claude-fix-ci.yml:108
.github/workflows/claude-fix-finding.yml:64
.github/workflows/claude-fix-runtime.yml:59
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 4 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.
4 files, 4 locations
.github/workflows/auto-merge-fix-pr.yml
.github/workflows/claude-fix-ci.yml
.github/workflows/claude-fix-finding.yml
.github/workflows/claude-fix-runtime.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in admin/src/app/layout.tsx:40
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
admin/src/app/layout.tsx:40 Dangerous innerhtml
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — engine/scripts/refresh_gmail_token.py:61
`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 — engine/scripts/run_migrations.py:188
`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 49 placeholder/mock markers across 20 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Integrity conf 1.00 13 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_ALLOWED_ORIGINS`, `ADMIN_PASSWORD`, `ADMIN_SESSION_SECRET`, `CI`, `DATABASE_URL`, `E2E_PORT`, `ENABLE_TEST_ENDPOINTS`, `NEXT_PUBLIC_SUPABASE_ANON_KEY` + 5 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't brea…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 46 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
4 files, 4 locations
.github/workflows/ci-admin.yml:107
.github/workflows/claude-fix-ci.yml:101
.github/workflows/claude-fix-finding.yml:57
.github/workflows/claude-fix-runtime.yml:52
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: engine/scripts/run_migrations.py:load, engine/scripts/run_migrations.py:load 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're separate.
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `m_old` in engine/tests/test_e2e_full_digest.py:714
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 `ou_old` in engine/tests/test_cov_lark_calendar_acl.py:217
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 `out_old` in engine/tests/test_cov_main.py:373
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 `p2_im_message_receive_v1` in engine/src/bot/lark_message.py:3
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 `register_p2_im_message_receive_v1` in engine/src/bot/lark_callback.py:408
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 `schedule_old` in engine/tests/test_cov_entrypoint.py:400
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 `sid_old` in engine/tests/test_merge_vault_db_deep.py:273
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: date_range
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
engine/src/processors/two_pass.py:521
low System graph software Dead code conf 1.00 Possibly dead Python function: find_contact_id_by_identity
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
engine/src/storage/contact_identity.py:121
low System graph software Dead code conf 1.00 Possibly dead Python function: footer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
engine/src/destinations/pdf_report.py:97
low System graph software Dead code conf 1.00 Possibly dead Python function: register_source
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
engine/src/sources/base.py:24
low System graph software Dead code conf 1.00 Possibly dead Python function: run_bot
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
engine/src/bot/server.py:216
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 quality Complexity conf 1.00 Very large file: engine/src/main.py (1565 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: engine/tests/test_cov_lark_callback.py (1302 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: engine/tests/test_cov_main.py (1395 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/24b5def5-2e72-4582-92af-d705be8fffce/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/24b5def5-2e72-4582-92af-d705be8fffce/

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.