Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

10 Node.js runtime features you SHOULD be using in 2024

Here are 10 Modern Node.js runtime features to start using in 2024! ✍️ Resources ✍️ ⏲️ Chapters ⏲️ ⚒️ About Snyk ⚒️ Snyk helps you find and fix vulnerabilities in your code, open-source dependencies, containers, infrastructure-as-code, software pipelines, IDEs, and more! Move fast, stay secure.

11 Best Practices to Secure your Nodejs API

If you are building an API, you are most likely evaluating the pros and cons of available technologies. Sooner or later, you will surely come across NodeJS. NodeJS helps to create stable, scalable, and backward-compatible APIs. Besides the functionalities, you can’t overlook the security risk that comes with them. Misconfigured, insecure APIs leave your companies with high-profile cyber-attacks. Like any APIs, those developed with NodeJS come with security threats.

How to choose the Best Node.js Docker Image

Today we walk through the best options for your Node.js Docker Image, how to avoid common pitfalls and mistakes, and the best ways to strengthen the security of your projects effectively. ⏲️ Chapters ⏲️ ⚒️ About Snyk ⚒️ Snyk helps you find and fix vulnerabilities in your code, open-source dependencies, containers, infrastructure-as-code, software pipelines, IDEs, and more! Move fast, stay secure.

Nine Docker pro tips for Node.js developers

If you spend quite a bit of time in the command line, working with Docker images and containers locally to build and test them, you might be in the mood for some power-user Docker commands. We're skipping the basics and diving straight into the lesser-known yet highly effective commands that can significantly improve your Docker experience.

NPM Manifest Confusion: Six Months Later

Several months ago, Darcy Clarke, a former Staff Engineering Manager at GitHub, discovered the “Manifest Confusion” bug in the npm ecosystem. The bug was caused by the npm registry not validating whether the manifest file contained in the tarball (package.json) matches the manifest data published to the npm server. Clarke claims this to be a large threat, allowing malicious actors to deceive developers and hide harmful code from detection.