Tricorder: Building a Program Analysis Ecosystem
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Static analysis tools help developers find bugs, improve code readability, and ensure consistent style across a project. However, these tools can be difficult to smoothly integrate with each other and into the developer workflow, particularly when scaling to large codebases. We present Tricorder, a program analysis platform aimed at building a data-driven ecosystem around program analysis. We present a set of guiding principles for our program analysis tools and a scalable architecture for an analysis platform implementing these principles. We include an empirical, in-situ evaluation of the tool as it is used by developers across Google that shows the usefulness and impact of the platform.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Why don't software developers use static analysis tools to find bugs?
Johnson, B., Song, Y., Murphy-Hill, E., & Bowdidge, R. (2013) · 2013 35th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2013.6606613 · Cited by 568 · cited 5×
“High false positive rates, confusing output, and poor integration into the developers’ workflow all contribute to the lack of use in everyday development activities [23], [27].”
BackgroundInfluential
Cited by
Modern code review: a case study at google
Sadowski, C., Söderberg, E., Church, L., Sipko, M., & Bacchelli, A. (2018) · Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice · doi:10.1145/3183519.3183525 · Cited by 280
Self-citationA large-scale longitudinal study of flaky tests
Lam, W., Winter, S., Wei, A., Xie, T., Marinov, D., & Bell, J. (2020) · Proceedings of the ACM on Programming Languages · doi:10.1145/3428270 · Cited by 64
API Designers in the Field: Design Practices and Challenges for Creating Usable APIs
Murphy, L., Kery, M. B., Alliyu, O., Macvean, A., & Myers, B. A. (2018) · 2018 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vlhcc.2018.8506523 · Cited by 38
(2020) · doi:10.1145/3379597.3387491 · Cited by 24
“example Google’s Tricorder [22] enforces a false positive rate < 10%.”
BackgroundInput splitting for cloud-based static application security testing platforms
Christakis, M., Cottenier, T., Filieri, A., Luo, L., Mansur, M. N., Pike, L., Rosner, N., Schäf, M., Sengupta, A., & Visser, W. (2022) · Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3540250.3558944 · Cited by 4
Metadata
- Authors
- Sadowski, C., Van Gogh, J., Jaspan, C., Soderberg, E., & Winter, C.
- Venue
- 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering
- Publisher
- IEEE
- Published
- 2015-05
- Pages
- 598-608
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W4254666025
- Cited by
- 145
- References
- 1
- FWCI
- 9.06
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Tricorder: Building a Program Analysis Ecosystem. https://app.cochat.ai/papers/10.1109/icse.2015.76
- The paper
- Sadowski, C., Van Gogh, J., Jaspan, C., Soderberg, E., & Winter, C. (2015). Tricorder: Building a Program Analysis Ecosystem. 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering. https://doi.org/10.1109/icse.2015.76
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.