What's in Your JS?
summary
Argues that the real question is what's actually in package.json not the topic, citing a real project with 300 packages and eight conflicting jQuery installs where the first-to-load wins caused subtle bugs. Shows concrete tooling: Jaeger tracing, Bluebird for richer promises, OWASP dependency-check and CVE alerts, plus profilers (commercial and open) to map call traces. Warns about typosquatting and planned a fake "flamingo" package demo that remains hypothetical rather than deployed.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:38Takeaways
- 4:11Core Differences between the Java Ecosystem
- 10:27Dependency Health
- 15:19Other Tooling
- 15:31Dependency Checker
- 17:29Project Flamingo
related talks
28mnpm Security: Key Threats & Real Cases | Anastasiya Egorova #JSConfAM25
53mArchitecting Robust JavaScript Applications
24mStrangerDanger: Finding Security Vulnerabilities Before They Find You!
21mKnow Your JS: SBOMs for Frontend Devs
52mBest Practices for Developers to Master Security
40mHostile JavaScript: Attacking and Defending the Browser
27mStrangerDanger: Finding Security Vulnerabilities Before They Find You
42mSecuring Your Software Supply Chain
