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.

woler1337/snippi

https://github.com/woler1337/snippi · scanned 2026-06-16 00:59 UTC (2 months, 1 week ago)

44 raw signals (0 security + 44 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 42 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 14 Low 21 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 42 Crowd 0 Layer: Frontend 14 Security 8 Cicd 3 Quality 17

Exclude dismissed / FP Exclude test files

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 87.4/100 with 77.8% coverage. It contains 364 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 44 findings — concentrated in quality (17), frontend (14), security (8). Risk profile is low: 0 critical, 0 high, 14 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 35 of 42 actionable findings. 44 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.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — server/src/worker.js:78

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 Tests conf 1.00 CI is configured but no tests are detected

A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.

CI/CDConfig theaterRepo hardening

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 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 'direct_innerhtml_assignment' in docs/index.html:687

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

docs/index.html:687 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/app.js:262

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

src/renderer/app.js:262 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/i18n.js:971

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

src/renderer/i18n.js:971 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/palette.js:161

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

src/renderer/palette.js:161 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/expander.js:5

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/expander.js:5 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/ocr.js:10

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/ocr.js:10 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/tray.js:132

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/main/tray.js:132 Node child process

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 14 placeholder/mock markers across 5 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 32 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: tests, lockfile. 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 36 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 3 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 32, 35, 69

.github/workflows/release.yml:32, 35, 69 (3 hits)

CI/CD securitySupply chainGithub actions

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: server/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.

server/package.json LockfileReproducibilityGenerated repo pattern

low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

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 — scripts/create-icon.js:164