When DevSecOps goes wrong
There’s a trend to unify security and developer flows that goes by various names like Dev Sec Ops and “shift left.” Generally security teams seem more enthusiastic about this than developer teams, who refer to security as a “soul-withering chore” or “insufferably boring procedural hinderance.” If developers don’t believe in code hardening ideas, things can go wrong in amusing ways.
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
Publish changes - MintlifyMintlify
Breaking down common documentation mistakesMintlify
How we grew Mintlify by doing things that don't scaleMintlify
Six Things to Consider When Using Redis on HerokuRedis
How to Conduct an AI Agent Security Audit [+ Checklist]Zapier
Workato integrations: What's included and when to use ZapierZapier
6 ways to use the Zapier Zoho CRM integrationZapier
Get email alerts for Facebook Messenger messagesZapier
Grafana Is Not Worried About AWS CommercializationThenewstack
When CI Meets CD: Deliver With ConfidenceThenewstack
DevSecOps: Why Security Shouldn’t be Sacrificed for SpeedThenewstack
Managing dependencies - The Go Programming LanguageGo
Unpacking sandbox startup latency: why started ≠ readyModal
What is a Streaming Multiprocessor?Modal
