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

RtlZeroMemory/Rezi

https://github.com/RtlZeroMemory/Rezi · scanned 2026-06-15 23:57 UTC (2 months, 3 weeks ago)

139 raw signals (0 security + 139 graph)

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

Complete repo analysis

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

JSON
Combined
39.5
/100
Security checks
40
0 findings
System graph
40
66.7% cov · 76 findings
Critical
0
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 0 High 5 Medium 24 Low 43 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 76 Crowd 0 Layer: Frontend 9 Network 1 Security 21 Cicd 4 Quality 41
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 39.5/100 with 66.7% coverage. It contains 7102 nodes across 29 cross-layer flows, written primarily in mixed languages. Engine surfaced 139 findings — concentrated in cicd (67), quality (41), security (21). Risk profile is high: 0 critical, 5 high, 42 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 68 of 76 actionable findings. 139 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.

high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/bench/src/scenarios/construction.ts:128
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/bench/src/scenarios/construction.ts:128 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/bench/src/scenarios/content-update.ts:352
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/bench/src/scenarios/content-update.ts:352 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/bench/src/scenarios/memory.ts:371
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/bench/src/scenarios/memory.ts:371 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/bench/src/scenarios/rerender.ts:191
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/bench/src/scenarios/rerender.ts:191 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in packages/bench/src/scenarios/startup.ts:231
Found a known-risky pattern (exec_used). Review and replace if possible.
packages/bench/src/scenarios/startup.ts:231 Exec used
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: docs/protocol/cursor.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/protocol/cursor.md VerificationAgent instruction
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 cicd CI/CD security conf 1.00 19 occurrences GitHub Action is tag-pinned rather than SHA-pinned
dtolnay/rust-toolchain@stable can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
7 files, 19 locations
.github/workflows/release.yml:112, 183, 242, 265, 324, 330 (6 hits)
.github/workflows/codeql.yml:29, 36, 47, 54 (4 hits)
.github/workflows/nightly.yml:43, 111, 169 (3 hits)
.github/workflows/ci.yml:286, 345 (2 hits)
.github/workflows/prebuild.yml:63, 69 (2 hits)
.github/workflows/bench.yml:27
.github/workflows/docs-dispatch.yml:24
CI/CD securitySupply chainGithub actions
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/docs.yml CI/CD securitySupply chainGithub actions
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 'node_child_process' in packages/bench/src/frameworks/bubbletea.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/bench/src/frameworks/bubbletea.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/bench/src/frameworks/opentui.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/bench/src/frameworks/opentui.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/bench/src/frameworks/ratatui.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/bench/src/frameworks/ratatui.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/bench/src/ratatui-runner.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/bench/src/ratatui-runner.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/bench/src/run.ts:30
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/bench/src/run.ts:30 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/native/scripts/build-native.mjs:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/native/scripts/build-native.mjs:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-native-vendor-integrity.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-native-vendor-integrity.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/hsr/record-runner.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/hsr/record-runner.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/record-hsr-gif.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/record-hsr-gif.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/run-api-extractor.mjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/run-api-extractor.mjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/run-bench-ci.mjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/run-bench-ci.mjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/run-e2e.mjs:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/run-e2e.mjs:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/verify-native-pack.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/verify-native-pack.mjs:2 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 87 placeholder/mock markers across 21 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 Debug conf 1.00 Debug logging residue appears in source files
Found 81 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 46 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.
6 files, 46 locations
.github/workflows/release.yml:21, 94, 130, 156, 161, 232, 237, 310, +6 more (14 hits)
.github/workflows/ci.yml:110, 123, 193, 220, 260, 265, 335, 340, +3 more (11 hits)
.github/workflows/prebuild.yml:46, 51, 85, 96, 120, 134, 139, 151 (8 hits)
.github/workflows/nightly.yml:25, 60, 85, 90, 159, 164 (6 hits)
.github/workflows/docs.yml:27, 47, 51, 64 (4 hits)
.github/workflows/bench.yml:13, 18, 65 (3 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/gallery/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.
examples/gallery/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/hello-counter/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.
examples/hello-counter/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/inline-status/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.
examples/inline-status/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/raw-draw-demo/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.
examples/raw-draw-demo/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/regression-dashboard/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.
examples/regression-dashboard/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/bench/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/bench/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/core/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/core/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/create-rezi/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-rezi/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/create-rezi/templates/cli-tool/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-rezi/templates/cli-tool/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/create-rezi/templates/minimal/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-rezi/templates/minimal/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/create-rezi/templates/starship/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-rezi/templates/starship/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/jsx/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/jsx/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/native/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/native/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/node/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/node/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `computeDropdownGeometryLegacy` in packages/core/src/runtime/__tests__/overlayUnification.test.ts:78
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 `maxOld` in packages/core/src/app/widgetRenderer/renderCaches.ts:223
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 `maxOld` in packages/core/src/renderer/renderToDrawlist/widgets/editors.ts:445
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 `zrev_v1` in packages/core/src/app/createApp/eventLoop.ts:10
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 `zrev_v1` in packages/core/src/index.ts:103
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 `zrev_v1` in packages/core/src/protocol/__tests__/zrev_v1_fuzz_lite.test.ts:2
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 `zrev_v1` in packages/core/src/protocol/__tests__/zrev_v1_invalid.test.ts: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 `zrev_v1` in packages/core/src/protocol/__tests__/zrev_v1_valid.test.ts:2
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 `zrev_v1` in packages/core/src/protocol/zrev_v1.ts:2
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 `zrev_v1` in packages/core/src/repro/replay.ts:25
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 `zrev_v1` in packages/core/src/testing/__tests__/eventBuilder.test.ts:2
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 `zrev_v1` in packages/core/src/testing/events.ts:199
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 — examples/gallery/src/index.ts:74
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/bench/src/profile-construction.ts:38
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/bench/src/profile-packed-style.ts:96
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/bench/src/profile-phases.ts:64
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/bench/src/ratatui-runner.ts: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 — packages/bench/src/report.ts:234
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/bench/src/run.ts:279
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/core/src/widgets/__tests__/editors.test.ts:8
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 — scripts/generate-drawlist-writers.ts:253
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: packages/bench/opentui-bench/run.ts (1958 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/core/src/app/__tests__/widgetRenderer.integration.test.ts (2957 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/core/src/app/widgetRenderer.ts (3808 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/core/src/app/widgetRenderer/mouseRouting.ts (1875 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/a6526fff-19b9-49eb-872e-81b5e1d89d1b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a6526fff-19b9-49eb-872e-81b5e1d89d1b/

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.