--- description: SonarQubeを実際に使用したユーザーのレビューから、製品の機能や価格、メリットデメリットをご覧いただけます。類似製品との比較も簡単、ぴったりのSaaSが見つかるはず！ image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: SonarQubeとは？ | 機能や料金、導入事例をご紹介【キャプテラ】 --- 現在地表示: [ホーム](/) > [CIツール](/directory/31119/continuous-integration/software) > [SonarQube](/software/210481/sonarqube) # SonarQube Canonical: https://www.capterra.jp/software/210481/sonarqube ページ：1 / 4\ 次へ: [次ページ](https://www.capterra.jp/software/210481/sonarqube?page=2) > SonarQubeを使用すると、あらゆる規模の開発チームがワークフロー内のコード品質およびコード・セキュリティの問題を解決できるようになります。 > > 評価：67人のユーザーによる評価は**4.5/5**。**おすすめ度**で最高の評価。 ----- ## 概要 ### SonarQubeの対象ユーザー クリーンで安全なアプリケーションを構築したいと考えるあらゆる開発者向けです。SonarQubeを使用すると、あらゆる規模の開発チームがワークフロー内のコード品質およびコード・セキュリティの問題を解決できるようになります。 ## 簡単な統計と評価 | 測定基準 | 評価 | 詳細 | | **総合評価** | **4.5/5** | 67 レビュー | | 使いやすさ | 4.2/5 | レビュー全体に基づく | | カスタマー・サポート | 4.0/5 | レビュー全体に基づく | | 価格の妥当性 | 4.4/5 | レビュー全体に基づく | | 機能 | 4.4/5 | レビュー全体に基づく | | おすすめ率 | 90% | (9/10 おすすめ度) | ## 企業情報 - **キャプテラについて**: SonarSource - **ロケーション**: Geneva, スイス ## ビジネスコンテキスト - **価格プラン**: $720.00 - **価格モデル**: (無料版が利用可能) (無料のトライアル) - **対象となる企業**: 自営業, 2～10, 11～50, 51～200, 201～500, 501～1,000, 1,001～5,000, 5,001～10,000, 10,000+ - **デプロイとプラットフォーム**: クラウド、SaaS、ウェブベース, Mac（デスクトップ）, Windows（デスクトップ）, Linux（デスクトップ）, Windows（オンプレミス）, Linux（オンプレミス） - **サポートされる言語**: 英語 - **利用可能な国**: アイルランド, アメリカ合衆国, アラブ首長国連邦, イギリス, イタリア, インド, オランダ, オーストラリア, カナダ, シンガポール, スイス, スウェーデン, スペイン, ドイツ, ニュージーランド, フィリピン, フランス, ブラジル, 南アフリカ, 日本 ## 機能 - API - Real-Time Analytics - アプリケーション・セキュリティ - グラフィカル・ユーザーインタフェース - コラボレーションツール - ダッシュボード - デバッグ - ワークフロー管理 - 品質保証 - 統合型開発環境 - 継続的デプロイ - 継続的デリバリ - 脆弱性診断 ## 統合 (合計5件) - Bitbucket - GitHub - GitLab - Jenkins - Microsoft Azure ## サポートのオプション - メール/ヘルプデスク - FAQ/フォーラム - 電話サポート ## Category - [CIツール](https://www.capterra.jp/directory/31119/continuous-integration/software) ## 関連カテゴリー - [CIツール](https://www.capterra.jp/directory/31119/continuous-integration/software) - [アプリ開発ツール](https://www.capterra.jp/directory/30082/application-development/software) - [静的アプリケーション・セキュリティテストツール](https://www.capterra.jp/directory/32818/static-application-security-testing-%28sast%29/software) ## 代替製品 1. [Jira](https://www.capterra.jp/software/19319/jira) — 4.4/5 (15371 reviews) 2. [GitHub](https://www.capterra.jp/software/129067/github) — 4.8/5 (6172 reviews) 3. [GitLab](https://www.capterra.jp/software/159806/gitlab) — 4.6/5 (1220 reviews) 4. [Bitbucket](https://www.capterra.jp/software/157785/bitbucket) — 4.6/5 (1345 reviews) 5. [Buddy](https://www.capterra.jp/software/157673/buddy) — 4.8/5 (176 reviews) ## レビュー ### "Code Analysis and ensuing security against threats" — 5.0/5 > **Sachin** | *2022年5月23日* | コンピュータ・ソフトウェア | おすすめ評価：9.0/10 > > **良いポイント**: Feature like Code Analysis and publishing those analysis report to end user. You can use default Quality Gates and Quality Profiles for scanning of your code. In case you want to modify these you can do that and define your own rule. Whenever there's commit in repo you just need to configure the task in your continuous integration pipeline if it passed the parameter only then commit will happens the master/main branch otherwise it will not. With these features you can eliminate the security threats and ensure that developers are following good practices while developing their code. I have integrated it with Azure DevOps. > > **改善点**: Only thing which I can think can be improved is logging of events. Sometime it becomes hard to debug the issues. Other then that, I think over all this fulfills all the requirements. > > Overall experience with Sonarqube is pretty wholesome integration came handy with my CI/CD tools such as Azure Devops and Jenkins. Provides insights against vulnerabilities and common threats so that necessary actions can be taken by developers to ensure the security and good coding practices to follow. Features like PR decoration allows to get results in CI/CD tools itself if passed then only commit happens to master branch. ----- ### "SonarQube is Great for Developers\!" — 5.0/5 > **認証済みレビュアー** | *2022年12月23日* | 高等教育 | おすすめ評価：8.0/10 > > **良いポイント**: It is simple for developers to recognize their code smells, unused lines of code, errors, problems with the third-party libraries they are using, etc. information and the precise location of the issue. It also offers answers to those problems. As a result, figuring out the problems and fixing them is simple. This will be a terrific tool for developers. Except that, we can introduce our own rules for checking the code quality. It could identify the code issues that are vulnerable to cyber attacks such as XSS, SQL Injection, etc. > > **改善点**: It was difficult to use the SonarQube on-premise application. Once we pushed a new code section, the server needed to restart in order for the application to work. > > We could identify many code related issues that are presented in our code and improve the quality of the application that we are developing. As a overall, SonarQube tool is able to add a value to our applications. ----- ### "Great tool for improving code quality" — 4.0/5 > **認証済みレビュアー** | *2026年5月9日* | 情報技術、情報サービス | おすすめ評価：6.0/10 > > **良いポイント**: What I liked most about SonarQube is how helpful it is for improving code quality and catching issues early in development. The vulnerability detection is one of its strongest features because it points out security risks, bugs, and code smells before they become bigger problems. It also integrates well with source code management and CI/CD pipelines, which makes it easier to include code analysis as part of the normal development workflow. That saves time and helps maintain cleaner code across projects. The platform has a bit of a learning curve in the beginning, especially when configuring rules and understanding reports, but after some use it becomes much easier to manage. The dashboard is detailed and gives a clear overview of code health. From a value for money perspective, it feels worth it for teams that care about code quality and security. It helps reduce issues before deployment, which can save a lot of time later. > > **改善点**: One thing I liked least about SonarQube is that the initial setup can take time, especially when configuring quality rules and integrating it with existing workflows. It is not something that feels fully plug and play. Scans on bigger projects can also be a bit slow at times, which can affect development speed during heavy usage. Another small issue is that some warnings feel too strict or unnecessary, so developers still need to manually review results instead of trusting every suggestion directly. For new users, understanding all the settings and customization options can also take a while, so there is definitely a learning curve before getting the most out of the tool. ----- ### "Never use SonarQube" — 1.0/5 > **Zach** | *2025年2月13日* | コンピュータ、ネットワーク・セキュリティ | おすすめ評価：0.0/10 > > **良いポイント**: There is nothing about this company that I would ever recommend. > > **改善点**: Of all the terrible things about this service and company, it's their customer support that takes the cake\! > > This service is a complete scam. Let's start with how it ended. I canceled my account, only to find out that it did not actually cancel. So I contacted support. It took them 2 months to resolve my request and they continued billing my card when the account was 100% not in use and I had no access to it. Now they refuse to refund my money. This is after they increased the cost of my plan by 3x without my approval (which is what prompted me to want to leave). In order to try to reduce my cost, our engineering team attempted to discsonnect some unused repos... nope, not possible. NEVER use this service. You absolutely cannot trust them. It's unbelievable that their system cannot be canceled and yet somehow it's my fault and I continue to get billed while their support team takes weeks to respond. ----- ### "Smooth experience for code reviewers" — 4.0/5 > **認証済みレビュアー** | *2026年4月3日* | 健康、ウェルネス、フィットネス | おすすめ評価：8.0/10 > > **良いポイント**: It makes our team consistent. For example, one of our devs was notorious for PRs with high cognitive complexity in their functions. Now, all we need to do in our azure pipelines is ensure that all sonarqube code smells are solved before they can merge their work to main. > > **改善点**: Sometimes it can create a loop in code smells. For example, if there are many commands in a Dockerfile, it will ensure that commands are merged together (but not necessarily correctly), which causes the dev to break the commands apart again. And the loop goes on until it is silenced. > > Overall, it's made our team much more consistent and efficient.PRs are a smoother process because the code smells are already fixed. ----- ページ：1 / 4\ 次へ: [次ページ](https://www.capterra.jp/software/210481/sonarqube?page=2) ## リンク - [Capterraで表示する](https://www.capterra.jp/software/210481/sonarqube) ## このページは以下の言語で利用できます | ロケール | URL | | de | | | de-AT | | | de-CH | | | en | | | en-AE | | | en-AU | | | en-CA | | | en-GB | | | en-IE | | | en-IL | | | en-IN | | | en-NZ | | | en-SG | | | en-ZA | | | es | | | es-AR | | | es-CL | | | es-CO | | | es-CR | | | es-DO | | | es-EC | | | es-MX | | | es-PA | | | es-PE | | | fr | | | fr-BE | | | fr-CA | | | fr-LU | | | it | | | ja | | | ko | | | nl | | | nl-BE | | | pt | | | pt-PT | | ----- ## 構造化データ