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.

you0810jmsdf/ns-factory

https://github.com/you0810jmsdf/ns-factory · scanned 2026-06-16 01:10 UTC (2 months, 1 week ago)

66 raw signals (0 security + 66 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

55.6% cov · 62 findings

Severity distribution — click a segment to filter

Active filters: severity: low × excluding tests × Reset all

Severity: Critical 5 High 0 Medium 45 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 62 Crowd 0 Layer: Frontend 2 Security 43 Cicd 1 Quality 16

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 64.0/100 with 55.6% coverage. It contains 382 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 66 findings — concentrated in security (43), quality (17), cicd (4). Risk profile is high: 5 critical, 0 high, 45 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 8 of 62 actionable findings. 66 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.

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 30 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 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 27, 36, 44, 66

.github/workflows/okcoin-price-notify.yml:27, 36, 44, 66 (4 hits)

CI/CD securitySupply chainGithub actions

low System graph security security conf 1.00 Insecure pattern 'document_write' in invoice/js/pdf.js:177

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

invoice/js/pdf.js:177 Document write

low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: scripts/site_monitor.py:check_url_once, scripts/site_monitor.py:check_url This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.

2 occurrences

repo-level (2 hits)

duplicatesduplication

low System graph quality License conf 1.00 No license file detected

No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.

Repo hardeningGenerated repo pattern

low System graph quality Docs conf 1.00 README lacks setup or run instructions

A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.

ReadmeRepo hardeningGenerated repo pattern

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 — invoice/js/editor.js:247

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

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/ca305b32-97f1-4f59-a2d4-daa5b4550563/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ca305b32-97f1-4f59-a2d4-daa5b4550563/

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.