Fixing leaky logs: how to find a bug and ensure it never returns
I lay out a case for moving security enforcement into the hands of developers. I show how I and another developer at r2 c successfully identified data leakage in our logs, fixed the issue, and prevented it from happening in the future.
London calling: Highlights from the 2025 cloud & cyber security expoSemgrep
Boosting Security Scan Performance for Monorepos with Multicore Parallel ProcessingSemgrep
Beyond Benchmarks: How Semgrep Redefines Javascript SecuritySemgrep
Benchmarking Semgrep Community Edition Performance ImprovementsSemgrep
Beyond vulnerabilities: Detect malicious dependencies in your supply chainSemgrep
Go.dev: a new hub for Go developers - The Go Programming LanguageGo
How Ramp automated receipt processing with fine-tuned LLMsModal
New Docker and JFrog Partnership Designed to Improve the Speed and Quality of App DevelopmentDocker
Capturing Logs in Docker DesktopDocker
How the world’s biggest YouTuber served millions of users on VercelVercel
ESLINT_CONFIGURATIONVercel
Get assistant conversations - MintlifyMintlify
Introducing AI AssistantMintlify
We Raised $25 Million from Tiger Global and Others to Unlock the Power of Voice Data and FuelDeepgram
How to Create an Online Training CourseSynthesia
How to instantly follow up on Facebook Lead Ads with custom notificationsZapier
The Coana Approach to Reachability AnalysisSocket
Forward Compatibility and Toolchain Management in Go 1.21 - The Go Programming LanguageGo
Product updates: Logs v2, live container profiling, and region selection on all plansModal
