Viktor.comAn AI coworker that actually does the work
CoreDhristi
Don't replace yourself. Deploy yourself
10 followers
Don't replace yourself. Deploy yourself
10 followers
Most marketplaces either list AI tools with zero vetting, or lock creators into subscription tiers. CoreDhristi does neither. Every AI agent, automation, and MCP server passes a 3-layer security scan (Semgrep, Gitleaks, npm audit) before earning a verified badge. Companies see the badge, never the code your GitHub repo stays private, always. Creators keep a flat 80% of every subscription, no tiers. Global from day one: INR + USD/EUR/GBP via Razorpay and Stripe.
How does the 3-layer scan actually run when my repo stays private - does it pull from my repo each time or do I need to push code somewhere for vetting?
@glzararkanzqio Good question it's pull-based, not push-based. Once you connect via our GitHub App, we mint a short-lived installation token and the 3 layer of scan runs server-side against that token directly nothing gets copied out, nothing goes public, and you don't need to push code anywhere separately. It re-runs automatically whenever you push updates too, so the verified badge stays current. Let me know if you want to try connecting a repo happy to walk you through it.
The verified badge concept is genuinely useful, I spent less time second-guessing what was safe to install. Keeping 80% as a flat split with no tiers is a nice change from the usual marketplace math.
@kymetwpmb Thanks Kiymet! That's honestly the exact problem I built the badge for nobody should have to eyeball a repo and guess if it's safe. Curious: before this, what usually made you trust (or not trust) installing something like this was it more about code quality, or just not knowing who actually built it?
The 80% creator cut is genuinely generous compared to most marketplaces I have seen. Liked that you can verify the security badge without exposing your repo, that is a nice balance for indie builders.
@ilbugasare30519 Really appreciate that, thank you! Yeah, keeping the repo private was non-negotiable for me I'm a security consultant by day, so I know most developers (rightly) don't want to hand over their IP just to prove it's safe. Are you building anything right now you'd consider listing once we're out of beta? Would love to have you on the waitlist either way link's in the post above if you want to grab a spot.
The privacy-first approach where my repo stays hidden but still gets a verified badge is honestly the missing piece I kept running into elsewhere. Flat 80% with no tier shuffling sealed it for me.
@melikedinikak2 Thanks Melike, that means a lot! The private-repo + verified badge combo was the one thing I refused to compromise on while building this figured if I wouldn't hand over my own repo just to prove it's safe, I couldn't ask anyone else to either. Are you working on something you'd consider listing once we're out of beta? Happy to add you to the waitlist either way link's in the post above if you want a spot.