Mattermost v7.0 is generally available today and includes three of our top five most requested features, based directly on your input in our feature idea forum. The following new features are all included (see changelog for more details).

Building software is hard. Building cloud software is even harder because things move much faster — and require mission-critical reliability and availability. To effectively build software in the cloud, engineering teams need observability, CI/CD, reporting, and lots of tooling. At every organization I’ve worked at, we’ve needed a system of tools that lets us: But all the tools available to engineering teams never quite fit together with our specific processes.

Node.js is one of the best and most widely used Javascript runtimes used for building APIs. But, this popularity status has led to many hackers distributing insecure modules that exploit the Node.js application or provide a weak point for exploitation. In this tutorial, you will learn how to audit Node.js modules and also detect vulnerabilities in modules using npm audit.

Welcome to the 9th edition of Open Source Matters: our regular publication about the latest happenings in open source! Let’s dive into the news.

Suppose you have to use your phone or other devices frequently, and you don’t want to type your password every time you wish to access an application. By implementing Trusted Device authentication, your system will recognize the device’s authentication and help you log in to the application quickly and safely. The whole process will not only save your time but will also allow you to witness an advanced authentication procedure.

Mattermost v6.7 is generally available today and includes the following new features (see changelog for more details).

Ask any engineer what they’d like to eliminate from their daily to-do list, and the answer will almost certainly be some version of reducing toil. Engineering organizations can burn hours and hours of work time on repetitive, manual tasks that reduce bandwidth for high-impact projects. That being the case, it’s no surprise that reducing toil helps your team work more productively and experience better job satisfaction in the long run.

For teams who deploy software to users around the world, every second counts when responding to outages and other incidents. It’s important that you have tools in your arsenal that are up to the challenge. Service monitoring, alerting, collaboration, and visibility are all essential components of a well-implemented incident response plan.

Time and resource consumption have become the driving forces of developing modern applications. While building cloud-native applications, it’s important to ensure that you have the most optimized code in place, and oftentimes that means leveraging concurrency. While writing concurrent code may sound overwhelming at first, Golang makes it extremely easy to get a handle on.

Bringing the best software solutions to market as quickly as possible requires using automation to facilitate repetitive tasks (e.g., testing) so you can spend more time writing high-quality code. This is one of the main reasons why today’s top-performing dev teams build continuous integration (CI) and continuous delivery or continuous deployment (CD) pipelines, which enable them to ship new releases faster.