Hello from Helsinki, San Francisco, and Barcelona. We founded Codescoop in 2017 as a distributed team and have been toiling away at an Enterprise edition, which is now up and running in several large companies, and will be announcing a free Developer edition soon. More on that in a few months. For now, let’s talk about what we do and introduce the concept of software intelligence…
Software Intelligence is…
Simply do a search for top business intelligence software tools and you will find that there are dozens, if not hundreds, of tools for business intelligence. BI software has helped businesses for years measure the health of their, well, business.
It is almost surely a truism to state that software engineers are very analytical people, yet we have lacked our own ways of analyzing code at scale. That’s not to say that there aren’t plenty of code scanning programs such as static code analysis. Those systems are fantastic (we use them ourselves!) for answering specific questions about security or code quality, but they are not capturing the bigger picture to answer the questions: how is my software doing today? And how will it be doing tomorrow?
To answer the bigger picture questions, we need to be gathering a lot of data; not just what’s in the code, but metadata from the entire software supply chain — from commits to builds to the community supporting it. This also includes news, blogs, and hullabaloo from the interwebz. All of this correlated data can be combined to provide a big picture overview of the software used inside of your repo.
Because more than 90% of code used by companies contains open source components (the number varies from report to report depending on how it’s being measured), that meant we needed to provide a way to analyze code wherever it lives — in the public domain, private cloud-hosted repos, or on-premise behind firewalls.
We wanted to build a product that helps companies and development answer questions such as:
- What percent of my code is out of date?
- What is the best component to use for my project?
- What dependencies are in my code?
- What license types are in my code?
- Are there libraries, components, or frameworks already in-use in my company that I could leverage for my work?
- How is my company contributing to the OSS projects we depend on?
- How is the broader software community contributing projects we open sourced?
- Should I pick an internal, proprietary or open source component to use in my new feature?
Open for Business
We have been working diligently for months with a small team spread across two continents and eight countries to build a product that answers the aforementioned questions… and then some! We are now shipping to several large innovative companies to help them answer questions about their code and then take action.
We’re super excited to finally share what we’ve been working on! As mentioned at the start, we will soon have a beta that anyone can try. Over the next few months, we will be blogging more about the work we’re doing, the open source projects we are leveraging and contributing back to to build Codescoop, and some interesting findings along the way.
If we have piqued your interest in any way, please visit us at www.codescoop.com and drop us a line.
Virginia & Valtteri, co-founders