Agriculture & Husbandry Solutions based on Ai & ML.
Learn more


You need a Code Audit if you are facing one of these scenarios:

Group 18320

The Source Code Audit.



Schedule Free Code Audit

Your codebase has not been looked at in more than two years

Enhancing the performance and responsiveness of your application

Planning to build a new feature for your app

Looking for a new development team

Fixing software bugs before selling your app

Scaling your application

Improving your application’s maintainability

Assessing an app that you want to buy

Finding security vulnerabilities in your codebase and wondering how to get them fixed

Not doing a code audit regularly sets your business up to fail.

A code audit provides a necessary defect filter during the requirements analysis of your application update.

It also guides the technical development of your app when scaling and adding new features. As a result, you save time and money and don’t risk breaking your app.

code audit jetruby
code audit

After a JetRuby systems architect carefully audits your code, you will receive a detailed report outlining:

Our core recommendations for your code.

A list of your code’s vulnerabilities and their locations

Our estimate to upgrade your code using industry-standard best practices

Ресурс 1

Abbreviated Example of Source Code Audit

1. Used technologies

Programming Language: Ruby 2.7.0
Framework: Rails gems (is not used directly, the Gemfile explicitly contains the Rails libraries that are needed)
Search Engine: Solr (open-source search engine from Apache)
Background Processing: DelayedJob
Scheduler: Cron


2. Code quality and security

2.1 Rubocop

The standard tool used for code style and code quality checks in Ruby is rubocop. In the project there is a config file for rubocop, but it was added in 2016 and was not updated since 2019. We made some minimal changes to this config to make rubocop run. With these changes rubocop reports:

2028 issues in total
633 issues can not be fixed automatically

Most issues (autofixable) are related to the code styling and can safely be applied or disabled in the config. On the other hand, non-autofixable issues need investigation, for they may reveal actual code issues.


2.2 Rails Best Practices

Another tool we used is called Rails Best Practices. It reports 423 warnings. Some of the warnings are related to the code style and are not too important, while the others are. The rails_best_practices report file is attached to the current document.


2.3 Brakeman

Brakeman reports possible security vulnerabilities. At the moment of writing it reports

== Overview ==
Controllers: 68
Models: 45
Templates: 237
Errors: 3
Security Warnings: 27

== Warning Types ==
Cross-Site Request Forgery: 1
Cross-Site Scripting: 8
File Access: 2
Mass Assignment: 7
Redirect: 1
SQL Injection: 8

Which is a pretty good result for the project of this age. There are no critical issues reported by brakeman. Non-critical issues/warnings should be fixed though. In general, security issues should always be prioritized.

The complete brakeman report is attached to this document.


3. Implementation’s quality review

3.1 Common code & architecture review

All of the application's business logic is implemented in models and controllers. The project uses almost no methods of organizing code, such as ServiceObjects or other ways of encapsulating business logic and organizing code using design patterns.

All of the application's business logic is implemented in models and controllers. The project uses almost no methods of organizing code, such as ServiceObjects or other ways of encapsulating business logic and organizing code using design patterns.

Cyclomatic complexity is a measure of the number of paths through a particular piece of code. High cyclomatic complexity usually leads to difficulty in testing and a significant deterioration in the comprehensibility of the codebase.


3.2 Data structures and data consistency

The application contains 307 tables. These tables are highly interrelated.

The application uses optimization techniques such as splitting data into tables to filter it using table joins and indexes easily.

DB Schema contains a lot of indexes that should speed up a search (Now, there is no way to test how these indexes are really used by a DB planner).

Most of the tables are using Integer type for IDs, while since Rails 5.1 the Rails Core Team is advocating to use bigint (Update on Basecamp 3 being stuck in read-only as of Nov 8, 9:22am CST). For an application like this, it’s quite easy to reach the default integer max value, which could lead to an unexpected outage or switch the whole system to a read-only state.


3.3 Environment

Based on the information about the environment files, all environments have a similar configuration as possible. This is a good indicator and reduces the chance of errors due to different environment settings.


3.4 Testing

The application didn’t have automated tests at all. That leads to problems with code refactoring and adaptation to new requirements. In addition, the codebase is quite large and has a lot of interconnections, which means the team will never know how any change will affect the whole system. So to prove that everything works, the business will need to invest more money in manual testing.

Tests are often used as documentation for developers to understand how the whole system works. So if there are no tests, it’s also necessary to create and support comprehensive technical documentation.

  • Hard-to-impossible refactoring
  • Slower feature development
  • Slower onboarding of developers
  • Slower Time To Market
  • More expenses on technical documentation


3.5 Other

Project README doesn’t contain helpful links such as API documentation, other documentation, third-party services used, development process prescribed in the team, such as branching or/and deployment rules.

Bundler Audit results are perfect. That means that all the gems in the project don’t have known vulnerabilities or don’t use insecure connections.


4. Possible issues & bottlenecks

4.1 Issues

Rubocop (ruby static code analyzer) with a default config resulted in 628 files inspected, 39155 offenses detected, 32120 offenses auto-correctable.


4.2 Bottlenecks

A lot of business logic on controllers with many filters will be a problem during the initial test suite setup. The team will need to understand every aspect of the specific part to write down even the most straightforward test examples.

The lack of code isolation (e.g., using PORO classes) deprives the team of the ability to write unit tests on isolated logic. It is easier to test the interaction of parts of the system with each other afterward.


5. Conclusion

The app follows Rails Way, which was very popular about ten years ago. But it is written without using development approaches that guarantee quality and make it easy to maintain. Such a codebase is complicated to work with and develop. Any change in requirements and new functionality is complicated to build in. And reusing existing logic is virtually impossible. Most controllers in an application depart from the REST standards for this very reason. Because of this, they become extremely large. On the implementation side, testing is just one of the first steps needed to refactor the application. Refactoring, in the long run, Refactoring will increase the development speed and Time To Market for new functionality while increasing the system's fault tolerance.

In the Gemfile of the project, there is also no bug tracker such as Sentry or its alternatives. This leads to the difficulty of catching bugs in the production environment.

Our teams should cooperate closely to start automated tests development because of the reasons above; this will increase the time required for high quality and complete coverage of the application by automated test scenarios.


This month only!

Celebrating our 11th anniversary

Group 18205

App Idea Audit is Free

Our analysts will audit your project to ensure there are no critical issues. Read more

Code Audit is Free

We analyze your source code to eliminate all the bugs. Read more

We’ve probably already built several Apps similar to yours

We’ve probably
already built several Apps
similar to yours

250+ successful applications in 16 industries





Social Media

Real Estate

Food delivery



Taxi booking







tild3062 3333 4463 a130 373865353930 main


We have extensive first-hand experience developing cutting-edge HIPPA-compliant, EHR, EMR, ERX, HCRM custom solutions. It allows us to save a lot of time and money for our new clients.

Online wishes list pana 1 1


We develop custom, profitable solutions that can easily handle any flow of customers and provide stable business growth.

Online Groceries pana 1


JetRyby’s marketplace solution OzMarkt allows you to build a fully custom marketplace with the features you need, making it a huge budget-saver for startups and small businesses.

Webinar pana 1


From corporate virtual training platforms with complex infrastructure to microlearning applications with progress tracking.

Social media pana 1

Social Media

Social media apps
SM Publishing & Scheduling Platforms
Messaging Apps
Video-based Networks
Social Network Analytic Tools
Online Reviews and Polling

House searching pana 1

Real Estate

Grow your real estate business with a custom digital solution built by Jetruby experts.

Take Away pana 1

Food delivery

Now is a good time to lunch your on demand delivery app.We’ve built several apps in this field. So we’ll develop yours faster and cheaper.

New entries bro 1


Vehicle Location tracking
Route Optimization
Vehicle Management
Nearest Gas Station
Mechanical Support
Merchants Real-time Notifications

Finance app pana 1


Banking Apps
Investment Apps
Insurance Apps
Digital Wallet Apps

Order ride pana 1

Taxi booking

Taxi Business apps
Taxi Business for Corporations
Car Rental apps
Air Taxi apps

Growing rafiki 1


Optimize your farming processes with our industry-specific expertise.
Weather Data
Farm Maps
Satellite & Drones
IoT Solutions

Opened pana 1


Flawless Registration Process
Engagement Features
Listings and Schedules
Event Feed Optimization
Search and Categories
Events Tracking

In no time pana 1


Multiple purchase options
Quick, problem-free purchasing
Track and show inventory
Personalized customers' experience
Supply chain management
Customer behavior analysis

Telecommuting pana 1


Project planning
Task time tracking
Notifications and reminders

Flight Booking pana 1


Travel Itinerary Generator
Geo-Tracking Services
Weather or Climate Forecasting
Location-Based Emergency Services
Currency Converter
In-App Language Translator

Fitness tracker pana 1


Diet and Nutrition apps, Workout and Personal trainer apps, Meditation and yoga apps, Activity tracking apps
We’ve done it all.

We are experts in the most popular Technologies


Ruby on Rails


React Js






React Native


Spree commerce










Spree commerce

Amazing projects we built

Sortly is the #1 inventory app for the iOS platform that enables you to visually track all your possessions.
  • 4.7⭐ rating, 6.2k reviews on Apple Store
  • 300,000+ downloads on Google Store
  • Backed by Phase4, Lombardstreet Ventures, Shamrock, Y Media Labs
Read more ➜
Jetruby guide

The MOST complete Guide to Finding the Best Developer for your App.

Freelancer vs Agency. Pros & Cons

How & Where to look for developers

26 questions to ask any developer

12 signs of a good and bad developer

bonus gift

Automated Developer Evaluation Matrix

Score every developer and hire the best one!

Developers Comparison Template

Most important decision-making information organized in one place.

Unbiased reviews from credible review platforms


Let's build great things together!

By submitting request you agree to our Privacy Policy