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.

alejoamiras/nulo

https://github.com/alejoamiras/nulo · scanned 2026-06-17 01:32 UTC (1 month, 2 weeks ago)

238 raw signals (0 security + 238 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -14.7 (diff) · 223 actionable findings from 1 signal source. 15 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 223 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 3 Medium 22 Low 57 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 223 Crowd 0 Layer: Frontend 29 Security 10 Cicd 5 Quality 179

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 133 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (8 lines) in packages/wallet-core/src/utils/serialization.…
info Commented-code block (6 lines) in packages/wallet-core/src/testing/fake-browser…
info Commented-code block (5 lines) in packages/wallet-bridge/src/scope-enforcement.…
info Commented-code block (6 lines) in packages/wallet-bridge/src/dispatcher.ts:282
info Commented-code block (5 lines) in packages/wallet-bridge/src/dispatcher.test.ts…
info Commented-code block (5 lines) in packages/extension-messaging/src/subscribe-wi…
info Commented-code block (6 lines) in packages/extension-messaging/src/background/c…
info Commented-code block (9 lines) in packages/extension-messaging/src/background/s…
info Commented-code block (6 lines) in packages/extension-messaging/src/offscreen/cl…
info Commented-code block (6 lines) in packages/extension-messaging/src/offscreen/se…
info Commented-code block (5 lines) in packages/wallet-crypto/src/zeroize.test.ts:43
info Commented-code block (5 lines) in packages/wallet-crypto/src/zeroize.ts:41

View all commented-out code findings →

Config drift 8 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

8 matching findings on this repo

info Commented-code block (6 lines) in packages/extension/vitest.e2e.config.ts:35
info Commented-code block (9 lines) in packages/extension/vitest.e2e.network.config.…
info Commented-code block (6 lines) in packages/extension/vite.config.ts:60
medium `fetch()` without try/.catch or AbortSignal — packages/extension/vite.config.ts…
info Commented-code block (7 lines) in packages/extension/vitest.e2e.all.config.ts:20
info Commented-code block (6 lines) in packages/extension/manifest/manifest.config.t…
info Commented-code block (8 lines) in packages/extension/manifest/manifest.firefox.…
info Commented-code block (5 lines) in packages/extension/src/wallet/config/config.t…

View all config drift findings →

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/88d926eb-3e0e-4624-a8d2-f0346313a692/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/88d926eb-3e0e-4624-a8d2-f0346313a692/

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.