M Montpas on Aug 2, 2020

Our Problem Statement

Monitoring changes across large codebases is a tedious task. It requires a lot of work-hours, it doesn’t scale and most importantly: doing it wrong may cost you - missing a single breaking change in a library you’re using could add hours of additional debugging and development time at your organization’s costs.

This is an issue not only for big corporations, but for all teams relying on open-source projects as well. For instance: GitHub’s State of the Octoverse mentions that open-source projects have an average of 180 package dependencies. This is a lot of code to periodically review for changes, specially for teams using a fraction of a given project’s functionalities!

At Sasca, we aim to make this process not only intuitive, but also faster by prioritizing changes based on the impact it has on your projects.