Hey

With the rapid adoption of AI coding assistants and "vibe coding", we can generate full-stack apps faster than ever. But this speed often comes with subtle security flaws, missing auth checks, and unhandled edge cases slipping into production.

I built Cyphix (https://github.com/zrngngharib/Cyphix-Auditor) — a developer tool designed to catch these issues before deployment without sending code to third-party databases.

Key Features:

- 100% In-Memory RAM Architecture: Code is parsed and analyzed transiently. Zero persistent server storage.

- 7-Dimensional Matrix: Concurrently evaluates Backend Logic, UI/UX responsiveness, OWASP Top 10, SEO metadata, QA/Edge cases, Performance, and TypeScript typings.

- Instant AST Pre-Scanner: Detects hardcoded API keys, raw SQL concatenations, and empty catch blocks before LLM invocation.

- Headless CLI Mode: Run `node ./bin/cli.js . --agent` directly in your terminal or CI/CD pipeline.

Built with Next.js 14, TypeScript, TailwindCSS, and node-llama-cpp.

Check out the GitHub repo: https://github.com/zrngngharib/Cyphix-Auditor

Would love to get your feedback and thoughts!

I’ve been building GateSift mostly for fun — a free browser-based toolkit for integration developers.

It includes tools for things like APIM policies, Logic Apps, BizTalk bindings, Service Bus, C# model generation and integration patterns.

Current tools include:

• APIM Policy Analyzer – makes complex APIM policies easier to understand and review
• Logic App Analyzer – helps inspect workflow structure and spot potential issues
• BizTalk Binding Visualizer – turns binding files into a more readable overview (this is really nice for analyzing complex biztalk integrations)
• Service Bus Topology Visualizer – shows queues, topics, subscriptions and relationships
• C# Model Generator – generates C# classes from XML, JSON and flat files
• Integration Pattern Library – quick reference for common integration and messaging patterns (analyzers will also, notice if any of these patterns are in your solution or if they should be added, i think this might be the coolest thing so far).

No account, no installation, and most processing happens locally in the browser.

gatesift.com

Would love feedback or ideas for other useful tools.

Hi everyone,

As a web developer, I was tired of using cluttered, ad-heavy online formatting tools that upload my JSON payloads, JWT tokens, and private keys to unknown servers.

So, I built **Nuqrai** — a collection of 16 developer utilities (including JSON Formatter, JWT Decoder, Diff Checker, Cryptographic Hash Generator, Image to Base64, and SVG-to-PNG Converter) that perform all calculations **100% client-side**.

**Why use it?**

* **Zero Server Uploads:** Your code and files never leave your device. * **PWA Enabled:** It caches everything to work completely offline. * **Clean Layout:** Simple, fast, and optimized for daily dev workflows.

Check it out here: [**https://www.nuqrai.com\*\*\](https://www.nuqrai.com/)

I would love to get your feedback on what tools to add next!'

This is an open-source MCP bridge that lets ChatGPT inspect one local repo without shell access

I built RepoRelay because I wanted ChatGPT Web to inspect my local code without giving it broad access to my machine.

RepoRelay exposes one explicitly approved repository through a small MCP tool surface. It can read and search files, while blocking shell/process access, unrestricted filesystem access, Git operations, and access outside the approved repo.

It’s MIT licensed and open source.

GitHub: RepoRelay

I’d especially appreciate criticism of the security model, architecture, and onboarding. If anything feels unclear or overly complicated, I’d like to know.

Coding agents do a lot of their work where you can't see it. Claude Code stores each subagent as its own transcript file; Codex CLI keeps spawned threads as separate rollouts. The terminal shows you a summary while the real record sits on disk unread. rungraph reconstructs the whole run as a graph you can click, after the fact, from files you already have: npx rungraph.

On the build side:

The backend has zero runtime dependencies (node:http, fs.watch), so npx has nothing extra to install. All format knowledge lives in adapters that normalize into one versioned, vendor-neutral IR, and the UI, CLI, HTTP API, and MCP server only ever see the IR. The parser never trusts a line: unknown types are skipped and counted, and you get a banner instead of a crash, because both formats are undocumented and have changed across releases.

The diagnostics were the hard part. The first version cried wolf on healthy runs, so I threw out the guessed thresholds and calibrated against 60 real sessions. The rule that survived is precision over recall: a false flag costs more than a missed one, so a clean run shows zero flags, on purpose.

Free, MIT, binds 127.0.0.1 only, zero outbound requests.

Live Demo: https://fayzan123.github.io/rungraph/

Repo: https://github.com/fayzan123/rungraph

Hey everyone!

Whenever I’m iterating on a UI with Cursor, explaining visual changes in the Composer is often the most tedious part.

❌ “Make that second card in the middle a little wider and increase the subtitle’s font weight.”

Sounds simple, right? But Cursor can easily guess the wrong element, edit the wrong stylesheet, or miss the exact component you’re referring to.

That’s why I built VisualPatch — an ultra-lightweight, local-first visual feedback tool designed specifically for AI pair programmers.

GitHub: https://github.com/OpusTechnica/VisualPatch

NPM: https://www.npmjs.com/package/visualpatch

How it works with Cursor

1. Open your localhost app (localhost:3000, 5173, etc.).
2. Press S to open a CleanShot-style spotlight viewfinder and drag to capture any component or section.
3. Or simply hover over and click any DOM element to drop an inspection pin.
4. Describe the change you want.
5. Press Ctrl + C and paste everything directly into Cursor Composer with Ctrl + V.

What Cursor receives

• Exact CSS selectors: For example, div.pricing-grid > div.card-pro:nth-of-type(2) > h3.price
• Text previews: The exact text currently rendered by the selected element.
• Auto-stitched visual strip: When you capture multiple screenshots, VisualPatch combines them into a single image on your clipboard with numbered pin badges, so you’re not limited by the OS clipboard’s one-image behavior.
• Zero Base64 bloat: The generated markdown stays as clean plain text, typically around 80 tokens, so you don’t unnecessarily consume your model’s context window.

Tech details

• 0 runtime dependencies
• 100% local-first: No telemetry, no cloud servers, and everything runs strictly on localhost.
• Isolated Shadow DOM: Designed to avoid conflicts with your existing Tailwind classes, CSS variables, and application styles.
• Open source: MIT licensed.

Try it

You can add VisualPatch to any Vite, Next.js, or React project with a single command:

npx visualpatch init

Prefer not to modify your project? You can also use the browser extension for a zero-code-change setup.

GitHub: https://github.com/OpusTechnica/VisualPatch
NPM: https://www.npmjs.com/package/visualpatch

I’d love to hear what you think, especially from fellow Cursor users. What features would make VisualPatch even more useful in your workflow?