Engineering Leader & Open Source Creator
Ofri Peretz
Building Products That Matter. Architect of the Interlace ESLint Ecosystem — 466 rules across 30 specialized plugins, designed for the AI/Agentic era.
Impact
The numbers behind the work
Cumulative totals across code, writing, and community engagement. Source-of-truth: Supabase v_* views, written by a daily ingest cron and cached for ~12 hours.
- npm downloads
- 0
- Packages published
- 0
- GitHub stars
- 0
- Contributions
- 0
- Articles published
- 0
- Article views
- 0
- Reactions
- 0
- Comments
- 0
Aggregate display values: npm downloads: 389.1K, Packages published: 36, GitHub stars: 15, Contributions: 0, Articles published: 81, Article views: 7.4K, Reactions: 85, Comments: 67
About
Building products that matter
Engineering Leader with a decade of experience shipping production JavaScript at scale. Currently focused on AI-native developer tools — building static analysis that empowers both humans and AI coding assistants to catch security issues before they ship.
Architect of the Interlace ESLint Ecosystem — 30 specialized plugins, 466 rules, covering OWASP Top 10, LLM Security, and database hardening. Built for the agentic era.
Featured
Interlace ESLint Ecosystem
30 specialized plugins. 466 rules. 100% OWASP Top 10 coverage. Built for the AI/Agentic era — LLM-friendly error messages mean Claude / Cursor / Copilot can fix vulnerabilities without context.
- ★ Stars
- 15
- npm downloads
- 389,107
Career
Work experience
- · Built first U.S. engineering team
- · Leading largest distributed team (US/EU)
- · 30 ESLint plugins, 466 rules
- · Deep dives on JS/TS, testing & platform engineering
- · First monetized API platform
- · 25+ shared packages, mono-repo
- · Scaled APIs 100x
- · 1,000+ tests, TypeScript migration
- ·Previous RolesatVarious
- · 6 years of platform engineering across startups and scale-ups
Open Source Philosophy
Open source is the ultimate learning accelerator. By building in public, I stay state-of-the-art, give back to the community, and build trust through transparent, well-documented code.
Writing
Latest articles
Nobody Writes Bad Crypto. They Write Correct Crypto at Four Layers.
Crypto failures are not one mistake repeated. They are four distinct layers of correctness, and each one looks fine from the layer above it.
· 6 min
142,076 Weekly Downloads. Zero Releases Since 2021. Is the Niche Defended?
A Serverless plugin with 142k weekly downloads last shipped a release in 2021. Downloads said taken; the registry said abandoned; the platform's roadmap said something else entirely. The incumbent map — weekly downloads × years since last publish × open-issue decay — is how I decide what to build next, including the pick I shipped against two months before the fact-check caught up with me.
· 6 min
We Were Wrong About sls remove
Our loudest serverless claim — 'ghost billing after sls remove' — failed our own E2E run. The trap is real, but it lives on a different path entirely. The full story of re-scoping a claim in public, and why the narrower version came out stronger.
· 7 min
25% of My Benchmark Verdict Is an Opinion. Here's the Anatomy.
My serverless benchmark prints 0.88 vs 0.3025 — real measurements running on editorial weights. Every index has a committee; the only real question is whether it publishes its votes. Mine are here: seven dimensions, the null policy, and a ±50% attack on the weights.
· 6 min
Marketing Pages Rot Silently. Mine Print an Expiry Date on Every Claim.
The claims registry: one file where every public claim has a row, every row points at a versioned result file, and a 90-day staleness rule decides when a claim must re-earn its place. The contract, the lifecycle, and how any product adopts it in an afternoon.
· 6 min
Fixtures First, Rules Second: How to Design a Ground-Truth Corpus
Building the 40-fixture corpus behind the Interlace security benchmarks meant making 40 judgment calls. The full design discipline: category selection, edge-case labeling, version pinning, corpus lifecycle, robustness checks — and Fixture Cards, a per-fixture documentation standard.
· 8 min
Stack
What I work with
Languages
- TypeScript
- JavaScript
- Node.js
Frameworks
- React
- Express
- NestJS
- Next.js
- Nuxt
Backend
- Kafka
- Redis
- PostgreSQL
- MongoDB
- Serverless
Cloud / DevOps
- AWS
- Docker
- Kubernetes
- Vercel
DevEx
- ESLint
- Nx Monorepos
- CLIs
- Static Analysis
AI-Native
- LLM-friendly errors
- MCP servers
- Agentic tooling
FAQ
Common questions
- What is the Interlace ESLint Ecosystem?
- A collection of 30 production-ready ESLint plugins designed for the AI/Agentic era. LLM-optimized error messages empower both human developers and AI coding assistants to catch and fix security vulnerabilities automatically.
- Why AI-native ESLint plugins?
- Traditional ESLint error messages are designed for humans reading them in an IDE. As AI coding assistants become more prevalent, error messages also need to be machine-parseable with clear remediation guidance. Our plugins bridge that gap.
- Which security standards do the plugins cover?
- Comprehensive coverage for OWASP Top 10 2021, OWASP Mobile 2024, and framework-specific patterns for Express, NestJS, Lambda, Postgres, MongoDB, and more. Each plugin includes detailed docs with Known False Negatives disclosed.
- What technologies do you work with?
- Languages: TypeScript, JavaScript, Node.js. Frameworks: React, Express, NestJS. Backend: Kafka, Redis, Serverless. Cloud: AWS, Docker, Kubernetes. DevEx: ESLint, Nx Monorepos, CLIs.