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

talstilkol/lumen-md

https://github.com/talstilkol/lumen-md · scanned 2026-06-16 00:29 UTC (2 months, 2 weeks ago)

100 raw signals (0 security + 100 graph)

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

Complete repo analysis

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

JSON
Combined
45.0
/100
Security checks
45
0 findings
System graph
45
88.9% cov · 92 findings
Critical
1
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 1 High 1 Medium 38 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 92 Crowd 0 Layer: Frontend 12 Hardware 5 Security 20 Cicd 2 Quality 53
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 45.0/100 with 88.9% coverage. It contains 2060 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 100 findings — concentrated in quality (53), security (22), frontend (12). Risk profile is high: 3 critical, 1 high, 38 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 58 of 92 actionable findings. 100 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 3 occurrences Possible secret in src/sync/git.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 152, 215, 309
src/sync/git.ts:152, 215, 309 (3 hits)
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in src/plugins/LiveJsBlock.tsx:108
Found a known-risky pattern (new_function_used). Review and replace if possible.
src/plugins/LiveJsBlock.tsx:108 New function used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/plugins/InsightsBlock.tsx:591
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 — src/plugins/LiveSvgBlock.tsx:78
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 — src/plugins/PlantUMLBlock.tsx:141
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 — edge-workers/audit/worker.ts:106
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 — edge-workers/billing/worker.ts:69
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 — edge-workers/publish/worker.ts:40
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 — scripts/publish-plugin.mjs:116
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 — scripts/translate-locale.mjs:86
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 — src/ai/ollamaProvider.ts:98
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 — src/lib/fetchRetry.ts:95
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 — src/plugins/useFetchSource.ts:17
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 — src/storage/templateMarketplace.ts:188
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 — src/sync/cloud/githubGist.ts:105
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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: docs/src/content/docs/ai/agents.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
docs/src/content/docs/ai/agents.md VerificationAgents md
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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: marketplace-server/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: sync-server/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 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.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api-server/server.ts:19
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api-server/server.ts:19 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in edge-workers/audit/worker.ts:37
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
edge-workers/audit/worker.ts:37 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in edge-workers/billing/worker.ts:36
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
edge-workers/billing/worker.ts:36 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in edge-workers/publish/worker.ts:34
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
edge-workers/publish/worker.ts:34 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in marketplace-server/server.mjs:50
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
marketplace-server/server.mjs:50 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/plugins/LiveSvgBlock.tsx:78
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/plugins/LiveSvgBlock.tsx:78 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/plugins/PlantUMLBlock.tsx:141
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/plugins/PlantUMLBlock.tsx:141 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/roadmap.html:334
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/roadmap.html:334 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/editor/insertMenu.ts:400
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/editor/insertMenu.ts:400 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/editor/WysiwygEditor.tsx:611
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/editor/WysiwygEditor.tsx:611 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/lib/trustedTypes.ts:56
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/lib/trustedTypes.ts:56 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/plugins/Model3DBlock.tsx:96
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/plugins/Model3DBlock.tsx:96 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/ui/PrintExport.tsx:123
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/ui/PrintExport.tsx:123 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in src/storage/fileFormats.ts:115
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
src/storage/fileFormats.ts:115 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/benchmark.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/benchmark.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/lighthouse-a11y.mjs:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/lighthouse-a11y.mjs:17 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 85 placeholder/mock markers across 30 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 quality Integrity conf 1.00 10 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CI`, `DEV`, `GITHUB_TOKEN`, `HOME`, `LUMEN_WORKSPACE`, `MARKETPLACE_DATA`, `PLAYWRIGHT_BASE_URL`, `PORT` + 2 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
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 40 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: nginx:alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:17 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 4 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
3 files, 4 locations
sync-server/Dockerfile:5, 10 (2 hits)
Dockerfile:2
marketplace-server/Dockerfile:2
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 20, 23, 131, 172
.github/workflows/ci.yml:20, 23, 131, 172 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/ui/KeyboardShortcuts.tsx:137
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/create-lumen-plugin/template/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/create-lumen-plugin/template/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `handleConvertLegacy` in src/ui/CanvasTldraw.tsx:256
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — api-server/server.ts:52
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — e2e/dynamic-blocks-hardening.spec.ts:22
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/create-lumen-plugin/bin.js:40
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/__tests__/a11y.test.tsx:100
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/editor/insertMenu.ts:175
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/lib/logger.ts:30
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — sync-server/persistent-server.js:89
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — sync-server/server.js:4
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Complexity conf 1.00 Very large file: src/commands/useCommands.ts (1456 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/i18n/index.ts (1532 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/baf2a0a0-8bdc-4924-860e-172ae540a116/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/baf2a0a0-8bdc-4924-860e-172ae540a116/

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.