For product-related support, please visit our Support Hub.
CodeScene is free for open-source projects. We also have a set of paid plans so that you can tailor CodeScene to your needs or analyze private repositories. This allows larger organizations to benefit from advanced analyses like CodeScene's cost metrics and delivery performance measures. We have a free trial so you can evaluate CodeScene before starting a plan.
CodeScene’s license is based on the number of active authors. An active author is anyone who has committed code over the past three months to the codebases you want to analyse. This time period is a sliding window that always starts at the date of the most recent commit in your repositories. Each author is only counted once. That is, if you analyse multiple codebases, the same persons only count once no matter how many projects they contribute to. Historic authors are free. People who haven’t committed code within the last three months are included for free and don’t add to the license fee.
During the Free Trial period, you get access to all the features in the plan of your choice. When you start your trial you choose if you want to try the Standard or the Pro plan.
We accept all major credit cards and invoicing.
There’s no limit on the number of active authors. The total cost of using CodeScene is based on how many active authors you have. The number of users that can login and use any of the CodeScene features, such as the automatic pull request reviews, are unlimited.
Cancellations can be done according to our terms which is 30 days before the end of the yearly subscription period. Monthly subscriptions can be cancelled at any time and will take effect the day after the last day of the current subscription period.
Yes, we have a completely free version for students which you can access by first getting a GitHub Student Developer Pack. Also see: https://codescene.com/github-students
In all major aspects they are the same product but it makes it possible for you to integrate and use CodeScene on matter if your current tooling and handling of your source code is cloud based or running on private servers.
It’s easy. You purchase CodeScene at our website, see pricing. Choose between our On-Prem or cloud solution, add the amount of active authors you have, press purchase and follow payment instructions. Three clicks later you are done.
Do you want to scale up with more active authors?
For On-Prem just go to your personal site in our customer portal and upgrade the subscription. If you are running our Cloud version, just login to your CodeScene cloud, find your price plan, change to the new subscription. Scale up or down. Your choice.
CodeScene is a quality visualization tool for software. Prioritize technical debt, detect delivery risks, and measure organizational aspects. It's fully automated.
CodeScene's paid plans also integrates with Pull Requests to provide real-time feedback on hotspots that decline in code health. Use this feature as a soft quality gate and as code review input.
CodeScene takes a behavioral view of of your codebase by adding insights into the people side of your code. This means you can detect coordination bottlenecks, simulate upcoming knowledge loss used for off-boarding, and measure how well your organization aligns with Conway's Law. All in one tool.
Yes, we do. Check out our plans for details on private repositories.
Yes, all plans let you analyze repositories owned by organizations that you are a member of. However, with the Community Edition plan you can only analyze public organizational repositories.
Yes, CodeScene supports multi-repository analyses.
CodeScene's X-Ray is an analysis that investigates the evolution of each function or method within a Hotspot. X-Ray is a great tool to prioritize technical debt and lets you refactor large files iteratively guided by data as described here and here.
CodeScene supports X-Ray for Hotspots. Just click on a Hotspot in your Hotspot Map and launch an X-Ray.
CodeScene lets you build knowledge maps over your code and measure the potential knowledge loss in your codebase (aka the Bus factor). You can also analyze the development efforts across teams. That team-level measurement lets you inspect how well-aligned your organization and architecture are with respect to Conway's Law. All you have to do is to visit your project's configuration page and define the teams in your organization.
a. On-Prem supports any git provider on a basic level (you can specify any git remote URL).
b. Cloud supports GitHub, Bitbucket, GitLab, and Azure DevOps.
CodeScene integrates with Pull Requests and triggers analyses automatically. This integration uses the Git provider API, which provides a (soft) quality gate for your hotspots. CodeScene also provides detailed information on possible degradations. This lets you act early on any issues before the code is merged. You'll never miss a hotspot again.
Yes, CodeScene integrates with Jira, Trello, Azure DevOps, and GitHub Issues. This integration lets you visualize and detect defect-dense modules, as well as putting a cost dimension on top of the findings. CodeScene’s cost analyses let you reason about the technical and organizational findings from a financial perspective. For example, how much time do you spend on defects in your top hotspots? What amount of work is unplanned? And what happens over time?
Sure, check out our On-Prem version of CodeScene. CodeScene On-Prem comes packaged as a Docker container and can be hosted in a private cloud.
CodeScene integrates with Jira, Trello, Azure DevOps, and GitHub Issues.
That's good! In fact, many of our users are already using other code analysis tools. Often, these tools complement the information that CodeScene provides. A traditional static analysis tool serves well to catch common coding mistakes or style violations. It's genuinely useful. However, a static analysis will never be able to tell you if some excess code complexity actually matters –- this is where CodeScene’s behavioral code analysis fills an important gap.
We also find that CodeScene's higher-level information, clear priorities, and intuitive visualizations attract a wide range of stakeholders. As such, CodeScene's sweet spot is that we serve the whole engineering organization, not just developers or managers, but both. This enables you to have a conversation around a deeply technical topic like code with your non-technical stakeholders. It's all about communication and shared situational awareness.
This integration lets you visualize and detect defect-dense modules, as well as putting a cost dimension on top of the findings. CodeScene’s cost analyses let you reason about the technical and organizational findings from a financial perspective. For example, how much time do you spend on defects in your top hotspots? What amount of work is unplanned? And what happens over time?
A traditional static analysis tool serves well to catch common coding mistakes or style violations. It's genuinely useful. However, a static analysis will never be able to tell you if some excess code complexity actually matters –- this is where CodeScene’s behavioral code analysis fills an important gap.
We also find that CodeScene's higher-level information, clear priorities, and intuitive visualizations attract a wide range of stakeholders. As such, CodeScene serves the entire engineering org organization, not just developers or managers, but both. This enables you to have a conversation around a deeply technical topic like code with your non-technical stakeholders. It's all about communication and shared situational awareness.
The main difference between CodeScene’s behavioral code analysis and traditional code scanning techniques is that traditional static analysis tools work on a snapshot of the codebase. CodeScene considers the temporal dimension and can analyze the evolution of the whole system. This makes it possible for CodeScene to prioritize based on how the organization actually works with the code. Hence, we can limit the results to information that is relevant, actionable, and translates directly into business value. CodeScene also goes beyond code as we consider the organization and people side of the system. This gives you information that is invisible in the source code itself.
You need to create a Slack app and configure CodeScene to use the correct API token.
All the details are described in our docs: https://docs.enterprise.codescene.io/versions/4.5.0/integrations/slack/notifications.html
The list is in the configuration. See: https://docs.enterprise.codescene.io/versions/4.5.0/integrations/slack/notifications.html#notifications-settings
You can use @username style to notify a user. See the help text for the Notification recipient config field and our docs.
Yes, you can. See Per-Project Configuration section in our docs.
Early warnings and staying in the loop especially for people and teams that “live in Slack”.
Currently REST API is only available for the On-Prem version but support will be added to our Cloud version soon.
REST API can be used directly from a shell script, we provide some use cases and scripts: See: examples-use-cases-and-scripts in our docs.
REST API imply using http protocol and every modern programming language already have a library for that so another option is to implement a client using your favorite library.
For using the REST API you need an user with role RestApi which can be created by CodeScene admin. See: the-rest-api-user in our docs.
You can automatically create a CodeScene project for example when the project is created in your favorite code repository platform.
You can manage CodeScene users, teams and project developers.
You can fetch analysis data from CodeScene for a particular list of projects or architectural components and integrate them into your reporting system.
The REST API is for people with knowledge in scripting and/or coding.
Because of how the Git provider API works, we are forced to request read and write access for CodeScene in order to read your code (see repo and public_repo scopes). CodeScene will of course never write any data to the Git repository itself.
We have two ways to share projects with other CodeScene users.
Organizational accounts are the primary way to share multiple projects with other members of your GitHub organization or Bitbucket workspace. When you create a new organizational account you can add/remove organization members in Configuration.
Organization members have access to all projects inside your organization. You can also give a collaborator access to a single project in the "Access Management" section in project configuration using the corresponding email addresses of those accounts. To find the email address, check the "My Account" page of the collaborator.
As a collaborator, you get read access to a project and its analysis results, as well as the ability to run new analyses, and to X-Ray files.
See the docs:
With the On-Prem version, all data stays on your servers. For environments with high security requirements, there is even an offline mode that allows On-prem to run without an external network connection. The Cloud security model is based on your Git provider's model. Only users with access to the code on GitHub, Bitbucket or Gitlab can have access to the analysis results on CodeScene. In CodeScene cloud we never share data in private repositories. CodeScene cloud does fetch your repository to do an analysis but deletes the local copy immediately afterwards. The analysis results are only available to you and the people you chose to invite. You can also delete an analysis project at any time and we make sure all your data is removed.
The new identity revolves around our vision to “give code an intelligent voice” and reflects our forward-looking culture. The new logo reinforces the idea of artificial intelligence and CodeScene being there as an extra team member, guiding you toward better software and teams.
The new website presents relevant content in a clean, minimalistic and modern way with an aim to give visitors easy access to solutions and information.
We are proud to share this new identity with our community and hope that it will inspire all of us to write better code, build happier teams and future proof our software.