3d ago · 2 min read · When the port.io pattern meets vertex ai A friend suggested, "get repOptics into Vertex AI." what followed was exactly the kind of deep dive we engineered the port.io sprint for: look at the existing codebase, map the tool's strengths, and find the h...
Join discussion
Apr 16 · 7 min read · The polarity problem A number that fights its own label RepOptics has seven scoring categories. Six of them are named after a thing you want more of: decisions, architecture, governance, delivery, dependencies, security. The seventh was named after a...
Join discussion
Apr 16 · 3 min read · Repoptics recalibration: from community pain to calibrated scoring When we first launched repOptics, the scoring engine was incredibly fast, but honestly, it was painfully tone-deaf. We were judging every single github repo against one universal rubr...
Join discussion
Apr 16 · 3 min read · The problem I met with my friend julio last night and we talked about the current market of ai builders. Everyone is building agents and wrappers, but how many of them are actually testing their products for vulnerabilities? How many get tangled in t...
Join discussion
Apr 16 · 3 min read · The export test The problem I built repOptics to scan GitHub repos and score them across five categories. It generates reports, runs AI analysis, even has a pentest lab. All very pretty in the browser. But then i exported a report as JSON and asked m...
Join discussion
Apr 16 · 3 min read · The widget that finally learned where it was RepOptics has had a Port.io floating widget for a while. Little violet button, bottom-right corner. Click it and you get the global view — repo count, aggregate vulns, scorecard distributions across everyt...
Join discussion
