--- description: DeepSourceを実際に使用したユーザーのレビューから、製品の機能や価格、メリットデメリットをご覧いただけます。類似製品との比較も簡単、ぴったりのSaaSが見つかるはず！ image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: DeepSourceとは？ | 機能や料金、導入事例をご紹介【キャプテラ】 --- 現在地表示: [ホーム](/) > [ソースコード管理ツール](/directory/31420/source-code-management/software) > [DeepSource](/software/199025/deepsource) # DeepSource Canonical: https://www.capterra.jp/software/199025/deepsource ページ：1 / 2\ 次へ: [次ページ](https://www.capterra.jp/software/199025/deepsource?page=2) > メンテナンス可能で安全なソフトウェアを構築するために必要なあらゆる機能を組織に提供する、オールインワンのコード開発ヘルスプラットフォームです。 > > 評価：10人のユーザーによる評価は**4.8/5**。**おすすめ度**で最高の評価。 ----- ## 概要 ### DeepSourceの対象ユーザー ソフトウェアエンジニアリングおよびセキュリティチーム。 ## 簡単な統計と評価 | 測定基準 | 評価 | 詳細 | | **総合評価** | **4.8/5** | 10 レビュー | | 使いやすさ | 4.5/5 | レビュー全体に基づく | | カスタマー・サポート | 4.5/5 | レビュー全体に基づく | | 価格の妥当性 | 4.8/5 | レビュー全体に基づく | | 機能 | 4.5/5 | レビュー全体に基づく | | おすすめ率 | 80% | (8/10 おすすめ度) | ## 企業情報 - **キャプテラについて**: DeepSource - **設立**: 1 ## ビジネスコンテキスト - **価格プラン**: $8.00 - **価格モデル**: (無料版が利用可能) (無料のトライアル) - **対象となる企業**: 51～200, 201～500, 501～1,000, 1,001～5,000 - **デプロイとプラットフォーム**: クラウド、SaaS、ウェブベース, Linux（オンプレミス） - **サポートされる言語**: 英語 - **利用可能な国**: アイスランド, アイルランド, アゼルバイジャン, アフガニスタン, アメリカ合衆国, アラブ首長国連邦, アルジェリア, アルゼンチン, アルバ, アルバニア, アルメニア, アンギラ, アンゴラ, アンティグア・バーブーダ, アンドラ, イエメン, イギリス, イスラエル, イタリア, イラク さらに210件 ## 機能 - Real-Time Analytics - アプリケーション・セキュリティ - コードレポジトリ統合 - コード点検 - ダッシュボード - デバッグ - バグ検出、問題検出 - バグ追跡 - バージョン管理 - 変更管理 - 統合型開発環境 - 継続的インテグレーション - 脆弱性診断 - 複数プログラミング言語をサポート ## 統合 (合計4件) - Bitbucket - GitHub - GitLab - Google Cloud ## サポートのオプション - メール/ヘルプデスク - FAQ/フォーラム - ナレッジベース - チャット対応有 ## Category - [ソースコード管理ツール](https://www.capterra.jp/directory/31420/source-code-management/software) ## 関連カテゴリー - [ソースコード管理ツール](https://www.capterra.jp/directory/31420/source-code-management/software) - [静的アプリケーション・セキュリティテストツール](https://www.capterra.jp/directory/32818/static-application-security-testing-%28sast%29/software) ## 代替製品 1. [SonarQube](https://www.capterra.jp/software/210481/sonarqube) — 4.5/5 (65 reviews) 2. [GitHub](https://www.capterra.jp/software/129067/github) — 4.8/5 (6148 reviews) 3. [Aikido Security](https://www.capterra.jp/software/1060185/aikido) — 4.7/5 (6 reviews) 4. [GitLab](https://www.capterra.jp/software/159806/gitlab) — 4.6/5 (1211 reviews) 5. [OX Security](https://www.capterra.jp/software/1043847/ox-security) — 4.7/5 (3 reviews) ## レビュー ### "Pros and Cons of DeepSource: My Personal Review" — 5.0/5 > **Reunaldo** | *2023年2月27日* | マーケティング、広告 | おすすめ評価：9.0/10 > > **良いポイント**: DeepSource's ease of use and comprehensive code analysis impressed me. I also liked how simple the setup process was, as well as the comprehensive dashboard, which allows me to easily track the progress of my codebase. Furthermore, the ability to customize the rules for code analysis and track code quality trends over time was a huge plus. Overall, DeepSource has been an excellent tool for assisting us in quickly identifying and resolving potential coding issues. > > **改善点**: The least appealing aspect of DeepSource is that the free plan does not include any automated analysis. You would have to manually review all of the pull requests and issues. ----- ### "How good is DeepSource for code" — 5.0/5 > **Adrian** | *2020年5月1日* | 工業オートメーション | おすすめ評価：9.0/10 > > **良いポイント**: The feature of automatic linkage with the GitHub repositories is very useful and time saving, I also like that the linkage remains. Code's analysis is very complete and specific, pointing to the exact line with the issue. And It also can resolve them automatically with is also time saving and I learn from them. > > **改善点**: I would like that the issues would be reflected in GitHub, so I can resolved manually if I like. > > It very easy to use, and useful for improving code quality and save time. ----- ### "DeepSource Review" — 4.0/5 > **Marek** | *2023年5月15日* | 金融サービス | おすすめ評価：5.0/10 > > **良いポイント**: One of the things I liked most about DeepSource was its powerful code analysis capabilities. It provided comprehensive and detailed feedback on potential code issues, including code smells, security vulnerabilities, and best practice violations. The ability to catch these issues early on and improve code quality was highly valuable. Additionally, DeepSource's seamless integration with popular code repositories made it easy to incorporate into my development workflow. > > **改善点**: While DeepSource had many aspects, one thing I liked least was the occasional false positives generated by the code analysis. There were instances where it flagged certain code segments as problematic when, in reality, they were not. This required additional time and effort to manually review and verify the reported issues. Although DeepSource continuously improved its analysis engine, reducing false positives further would enhance the overall experience. > > Its robust code analysis capabilities significantly contributed to improving code quality and maintainability. The seamless integration with my development workflow made it easy to adopt and incorporate into my projects. While there were occasional false positives, the benefits of catching potential issues early on outweighed this minor inconvenience. DeepSource proved to be a valuable tool in my code review and quality assurance process. ----- ### "DeepSource analyzes, improves code quality and keeps our codebase clean" — 5.0/5 > **Anirudh** | *2021年8月10日* | インターネット | おすすめ評価：10.0/10 > > **良いポイント**: We have been using DeepSource for six months now. I can see the difference in the code style and the code quality of the files that have gone through DeepSource and not gone through DeepSource. There's a clear difference in the way indentation happens or the number of whitespaces that are left, or the number of columns that are present in the code. If you compare, if you take the difference between these two files there will definitely appear a difference between the files that have been processed through DeepSource and the files that have not been processed. > > **改善点**: We would like to see the support added for multiple files for the Autofix feature. > > Most of the time, developers miss out on formatting their code in the local development environment, and having DeepSource integrated removes the headache of manually going through the code and seeing if there are any accidental linting or formatting errors that developers might've left in their code. So it just does the job automatically for us. ----- ### "The strength of DeepSource its capacity to offer thorough feedback on the security and code quality." — 5.0/5 > **Sanket** | *2023年3月1日* | 情報技術、情報サービス | おすすめ評価：8.0/10 > > **良いポイント**: The tool's smooth integration with well-known code repositories like GitHub, GitLab, and Bitbucket makes it simple to integrate it into current processes. It can also be integrated with well-known code editors like PyCharm, IntelliJ IDEA, and VS Code. Moreover, DeepSource provides customization possibilities so that teams can adapt the tool to their own requirements. For instance, they can set the severity levels of various concerns or configure the programme to disregard particular issues. > > **改善点**: One potential drawback is that it could generate a lot of input, which some engineers might find overwhelming. It can take a lot of time and effort to prioritise problems after going through all the input.The tool's potential for producing false positives or failing to detect all problems is another potential downside. > > Overall, DeepSource is a great solution for teams looking to increase the security and quality of their code. It is simple to use, effortlessly incorporates with current procedures, and offers thorough feedback on code errors. Teams that wish to produce better code and steer clear of future costly blunders should give it some serious thought. ----- ページ：1 / 2\ 次へ: [次ページ](https://www.capterra.jp/software/199025/deepsource?page=2) ## リンク - [Capterraで表示する](https://www.capterra.jp/software/199025/deepsource) ## このページは以下の言語で利用できます | ロケール | 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 | | | nl | | | nl-BE | | | pl | | | pt | | | pt-PT | | | tr | | ----- ## 構造化データ