You vibe-coded something great. It runs. But your AI builder cared about "does it work," not "is it safe" so most of these apps quietly leave stuff open: keys, admin pages, endpoints you forgot existed.
Xseth scans your site like an attacker would and gives you a PDF with everything it found and how to fix it. Then just hand that PDF to the AI you built with and let it patch things up. No security knowledge required.
I got tired of my AI agents (Claude/Cursor) losing the plot during long coding sessions because their context window was full of junk.
I spent my nights building YourMemory, a local MCP server that uses biological decay (Ebbinghaus curve) to prune stale logs while keeping important architectural "chains" alive.
We are incredibly excited to announce the rollout of ZygAI 3.7! This update brings massive new ways to customize your experience, share your creativity, and interact with a significantly smarter AI.
Hello, I just built a app for student pilots looking to learn ATC. I just published and I need a few users just to start out with before I setup stripe. I am not pilot approved yet I will get it very soon. The app name is ATCpal. I am looking for some feedback if possible.
Link: ATCpal.app
Even if you don t know how to talk to ATC like I said I am just looking for feedback! Thanks so much I hope you guys can help me!
Here's something nobody in tech talks about openly: Almost every serious tech role, frontend, full-stack, product design, DevOps, asks for a portfolio at some point in the hiring process. And yet, the majority of developers either:
Never build one at all
Start one and abandon it halfway
Have one from 2-3 years ago that no longer reflects what they can now do This isn't laziness. It's the nature of the craft.
Developers are always building for other people.
The client's product.
The startup's MVP.
The company's internal tool. When the work is done, it lives on someone else's domain, or worse, behind a login screen you can't share. So when a recruiter or client asks "can I see your work?", the honest answer is complicated. The work exists.
The proof doesn't.
And that gap costs people jobs. I've been thinking about this problem for a while, which is why I built Krilarr - a verifiable developer portfolio platform that lets your work speak with evidence, not just screenshots. With Krilarr, developers can: Showcase real projects with verified proof of contribution Generate AI-powered proposals that match their actual skill set Build a living portfolio that grows with them, not one they have to rebuild from scratch every 18 months Your skills are not the problem. Your proof is. If you're a developer who's been putting off the portfolio thing, or one whose current portfolio no longer represents what you're capable of - Krilarr was built for you. Try it free for 14 days (Pro tier included): krilarr.vercel.app Drop a comment if this hit close to home. I'd love to hear how you've been handling the portfolio and proof of work/experience problem. #developers #portfolio #techjobs #krilarr #careergrowth #software #opentowork #hiring