Codekvast detects Truly Dead Code in your app Starting at $0/mo.
Methods that have not been invoked in production for a significant period of time can be considered Truly Dead Code.
Truly Dead Code brings no value to your customers, and should probably be removed.
By eliminating truly dead code you can maintain your development speed over time.
Less code means less build time, less testing time, less deployment time, less training time.
Most code contains technical debt. Code that is accidentally complex, uses dated libraries and frameworks, lacks test coverage and so on.
The easiest way to reduce technical debt is to simply remove unused code.
The problem is to know what is unused code. This is where Codekvast can help.
Codekvast detects Truly Dead Code, and helps you make informed decisions about what code that safely can be deleted.
A bloated code base that contains dead features - features that no real user uses - will make team onboarding more expensive.
By continously removing dead code you make developer onboarding faster and cheaper.
A smaller code base makes a smaller attack vector for hackers.
By continuously removing dead features you keep the attack vector minimal.
The method call overhead incurred by Codekvast is measured in nanoseconds on a developer laptop.
Time-critical parts of the code base can be excluded from being tracked by Codekvast.
You should use Codekvast in production, where your real users are!
The available application locations for this add-on are shown below, and depend on whether the application is deployed to a Common Runtime region or Private Space. Learn More
|Region||Available||Installable in Space|
This add-on is in alpha and can only be provisioned if you have been invited by this add-on partner. To provision, copy the snippet into CLI