Fast warning checks for suspicious copy, phishing URLs, screenshots, and AI-heavy hype.

한국어 README · Install Guide · Release Draft · Architecture

What K-WarningCheck Is For

K-WarningCheck is built for one job: checking whether a message is trying too hard to make you click, install, pay, or trust it before you have time to inspect it.

It focuses on:

• phishing and scam copy that mimics normal operational language
• urgency-heavy promotional text designed to shortcut judgment
• AI-generated persuasion that sounds polished but weakens under inspection
• screenshots and clipped captures that need OCR before review

The same analysis engine powers both the Chrome extension and the desktop app, so the warning logic stays consistent across surfaces.

Product Tour

Desktop workspace Signal score, tags, provider selection, and full input review in one surface.	Chrome extension Fast first-run entry point with history preview and direct setup access.

Shared settings Theme, shortcuts, privacy defaults, and provider state all stay in one place.	History review Saved records can be expanded, reanalyzed, or cleared from the settings surface.

Setup Flow

Step 1 See the demo analysis cards before doing anything else.	Step 2 Choose Korean or English for the interface and the rendered analysis output.	Step 3 Connect Gemini, Groq, and platform-supported Codex only if you need them.

Why It Works

• Shared rule engine for text, URL, clipboard, selection, image, and capture inputs
• OCR-first pipeline for screenshots and image-heavy messages
• Provider-assisted critique with Gemini, Groq, and Codex where supported
• Platform-aware safety defaults, including hidden Codex flows on Windows
• Secure OS-backed storage for provider keys
• Desktop workflows for manual review, history, clipboard checks, and capture

Platform Matrix

Surface	Status	Codex availability
Chrome on macOS / Linux / non-Windows	Supported	Available
Chrome on Windows	Supported	Hidden and disabled
Desktop on macOS	Supported	Available
Desktop on Windows	Supported	Hidden and disabled

Windows intentionally ships without Codex UI, login, and connection flows.

Install

Chrome extension Load build/dist/ as an unpacked extension from chrome://extensions. Optional local host install: npm run native:install

macOS app Open the files in build/mac/. Use the DMG or the zipped app bundle, then launch and add provider keys.

Windows app Run the executable from build/windows/. Windows keeps Codex hidden and routes users toward Gemini or Groq.

Build From Source

npm install
npm run lint
npm run test
npm run build:extension
npm run build:mac
npm run build:windows

Raw build outputs are generated in dist/, mac-app/, and windows-app/. The repository-level handoff copies live in build/.

Repository Shape

k-warning-check/
├── build/       # release-ready extension and app files
├── docs/        # architecture, install, security, release draft, assets
├── main/        # shared frontend, extension runtime, renderer, native host scripts
├── tauri-app/   # Tauri v2 backend in Rust
├── README.md
├── README.ko.md
└── package.json

Documentation

Document	Description
docs/INSTALL.md	Install paths, release assets, local build flow
docs/ARCHITECTURE.md	Shared runtime structure, capability model, data flow
docs/ANALYSIS-ENGINE.md	Rule engine, scoring, classification, checklist logic
docs/CHROME-EXTENSION.md	Extension structure, runtime messages, local host integration
docs/DESKTOP-APP.md	Desktop architecture, platform behavior, renderer and Rust commands
docs/PROVIDERS.md	Gemini, Groq, Codex support rules
docs/SECURITY.md	Secure storage, bridge token handling, repo hygiene
docs/DEVELOPMENT.md	Setup, verification, packaging workflow
docs/GITHUB-RELEASE.md	Copy-ready release body draft

FAQ

Why is Codex missing on Windows?

Windows deliberately hides Codex UI and blocks Codex bridge flows in both the extension and the desktop app. Compatibility fields remain in stored state, but the runtime does not use them on Windows.

Where are the distributable files?

The files meant for handoff live in build/. Raw local outputs still originate in dist/, mac-app/, and windows-app/.

Where are provider keys stored?

Provider keys are stored through OS-backed secure storage. Checked-in credentials, personal paths, and private certificates do not belong in the repository.

Contributors

Role	Contributor
Maintainer	Habin Song

License

Private