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

usememos/memos

https://github.com/usememos/memos · scanned 2026-06-16 00:46 UTC (2 months, 1 week ago)

127 raw signals (0 security + 127 graph)

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

Complete repo analysis

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

JSON
Combined
58.4
/100
Security checks
58
0 findings
System graph
58
100.0% cov · 67 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 12 Low 16 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 67 Crowd 0 Layer: Frontend 27 Hardware 4 Security 5 Cicd 3 Quality 28
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 58.4/100 with 100.0% coverage. It contains 2642 nodes across 20 cross-layer flows, written primarily in mixed languages. Engine surfaced 127 findings — concentrated in cicd (54), quality (30), frontend (27). Risk profile is high: 9 critical, 0 high, 37 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 30 of 67 actionable findings. 127 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 internal/email/doc.go
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
internal/email/doc.go:15
critical System graph security Secrets conf 1.00 8 occurrences Possible secret in internal/email/README.md
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 32, 70, 83, 97, 111, 127, 141, 220
internal/email/README.md:32, 70, 83, 97, 111, 127, 141, 220 (8 hits)
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/src/components/MemoContent/CodeBlock.tsx:151
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 — web/src/components/MemoContent/MermaidBlock.tsx:98
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 — web/src/connect.ts:58
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 hardware Security conf 1.00 Dockerfile runs as root: scripts/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 3 occurrences Frontend route `/explore` has no Link/navigate to it — web/tests/guards.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
3 occurrences
repo-level (3 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 22 occurrences GitHub Action is tag-pinned rather than SHA-pinned
golangci/golangci-lint-action@v9 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
6 files, 22 locations
.github/workflows/build-canary-image.yml:73, 76, 79, 85, 93, 134, 138, 149, +1 more (9 hits)
.github/workflows/release.yml:73, 245, 278, 281, 284, 290 (6 hits)
.github/workflows/backend-tests.yml:41, 87 (2 hits)
.github/workflows/frontend-tests.yml:28, 59 (2 hits)
.github/workflows/proto-linter.yml:26, 31 (2 hits)
.github/workflows/release-please.yml:32
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 3 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.
3 files, 3 locations
.github/workflows/build-canary-image.yml
.github/workflows/release-please.yml
.github/workflows/release.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/src/components/MemoContent/CodeBlock.tsx:151
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/src/components/MemoContent/CodeBlock.tsx:151 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/src/components/MemoContent/MermaidBlock.tsx:98
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/src/components/MemoContent/MermaidBlock.tsx:98 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in web/src/App.tsx:34
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
web/src/App.tsx:34 Direct innerhtml assignment
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 301 placeholder/mock markers across 72 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
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 5 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: alpine:3.21
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
scripts/Dockerfile:29 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: golang:1.26.2-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
scripts/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 29 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
6 files, 29 locations
.github/workflows/release.yml:70, 78, 90, 105, 134, 137, 143, 194, +6 more (14 hits)
.github/workflows/build-canary-image.yml:33, 45, 67, 112, 127 (5 hits)
.github/workflows/backend-tests.yml:26, 29, 55, 58 (4 hits)
.github/workflows/frontend-tests.yml:25, 33, 56, 64 (4 hits)
.github/workflows/proto-linter.yml:21
.github/workflows/stale.yml:16
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `library_v2` in web/src/types/proto/google/api/client_pb.ts:427
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 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: proto/gen/api/v1/apiv1connect/user_service.connect.go (857 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: proto/gen/api/v1/instance_service.pb.go (2047 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: proto/gen/api/v1/memo_service.pb.go (2695 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: proto/gen/api/v1/memo_service.pb.gw.go (1789 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: proto/gen/api/v1/user_service.pb.go (3787 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: proto/gen/api/v1/user_service.pb.gw.go (2279 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: proto/gen/store/instance_setting.pb.go (1501 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: server/router/api/v1/user_service.go (2032 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/src/types/proto/api/v1/user_service_pb.ts (1975 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/29e27f24-c6dc-4f8c-93e6-9d4f294fdbe7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/29e27f24-c6dc-4f8c-93e6-9d4f294fdbe7/

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.