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

selinyi123/clipvault-personal

https://github.com/selinyi123/clipvault-personal · scanned 2026-06-16 00:06 UTC (2 months, 2 weeks ago)

27 raw signals (0 security + 27 graph)

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

Complete repo analysis

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

JSON
Combined
82.4
/100
Security checks
82
0 findings
System graph
82
88.9% cov · 26 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 0 Medium 4 Low 18 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 26 Crowd 0 Layer: Software 10 Frontend 1 Security 3 Cicd 1 Quality 11
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 82.4/100 with 88.9% coverage. It contains 573 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 27 findings — concentrated in quality (11), software (10), security (4). Risk profile is high: 3 critical, 0 high, 4 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 24 of 26 actionable findings. 27 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 2 occurrences Possible secret in contracts/vectors/secret_guard.json
Detected pattern matching github_token. Rotate the credential and move to a secret manager.
lines 67, 99
contracts/vectors/secret_guard.json:67, 99 (2 hits)
critical System graph security Secrets conf 1.00 Possible secret in tools/gen_vectors.py
Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.
tools/gen_vectors.py:137
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — desktop/clipvault/api/webui/app.js:6
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality 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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in desktop/clipvault/api/webui/app.js:76
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
desktop/clipvault/api/webui/app.js:76 Direct innerhtml assignment
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 10 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 quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `github_backup` in desktop/clipvault/main.py:18
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 `github_backup` in desktop/tests/test_backup.py:12
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 `last_backup` in desktop/clipvault/api/handlers.py:245
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_g11_1_rules_per_type_end_with_copy` in desktop/tests/test_actions.py:35
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: backup_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
desktop/clipvault/main.py:110
low System graph software Dead code conf 1.00 Possibly dead Python function: do_DELETE
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
desktop/clipvault/api/server.py:151
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
desktop/clipvault/api/server.py:87
low System graph software Dead code conf 1.00 Possibly dead Python function: do_PATCH
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
desktop/clipvault/api/server.py:161
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
desktop/clipvault/api/server.py:121
low System graph software Dead code conf 1.00 Possibly dead Python function: has_remote
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
desktop/clipvault/backup/git_repo.py:74
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
desktop/clipvault/api/server.py:84
low System graph software Dead code conf 1.00 Possibly dead Python function: record_attempt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
desktop/clipvault/store/backup_queue_repo.py:58
low System graph software Dead code conf 1.00 Possibly dead Python function: serve
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
desktop/clipvault/api/server.py:181
low System graph software Dead code conf 1.00 Possibly dead Python function: sweep_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
desktop/clipvault/main.py:88
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
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/bae2545c-8673-4b8c-b121-7aad39d42350/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/bae2545c-8673-4b8c-b121-7aad39d42350/

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.