epam/Indigo

Universal cheminformatics toolkit, utilities and database search tools

Owned by EPAM Systems

View on GitHub ↗Jump to charts ↓Open shareable report →

epam/Indigo has 400+ stars and 100+ forks on GitHub, is written in C++, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 39 minutes ago
Added to GitGenius on October 12th, 2026
Created on June 16th, 2015
Open Issues & Pull Requests: 808 (+0)
GitHub issues: Enabled
Number of forks: 134
Total Stargazers: 410 (+0)
Total Subscribers: 38 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.4 hours
Mean response time: 41.3 days
90th percentile: 68.5 days
Tracked items: 1,495

Maintainer activity

41 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 34% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "query features phase II" is answered fastest, typically in under an hour, while "Severity: Medium" waits about 3 weeks. 31% of tracked open issues have had no activity in three months. Only 53% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 623
New in 7 days: 11
Closed in 7 days: 6
Avg open age: 970 days
Stale 30+ days: 480
Stale 90+ days: 435

Recent activity

Opened in 7 days: 11
Closed in 7 days: 6
Comments in 7 days: 3
Events in 7 days: 91

Top labels

  • Priority: High (431)
  • Priority: Medium (336)
  • Priority: Low (161)
  • User`s Feedback (146)
  • Severity: High (127)
  • Severity: Medium (108)
  • query features phase II (100)
  • HELM (83)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Indigo is a universal cheminformatics toolkit that provides a library for molecular structure analysis and manipulation, along with specialized tools for chemistry workflows.

The toolkit addresses the need to work with chemical structures programmatically and visually across different platforms and databases. Indigo offers a core cheminformatics library written in C++ that handles molecular parsing, rendering, and analysis. It includes Bingo, a chemistry search engine that integrates with Oracle, Microsoft SQL Server, and PostgreSQL databases, as well as Bingo-Elastic for searching chemical structures in Elasticsearch. The library exposes its functionality through bindings for .NET, Java, Python, R, and WebAssembly, allowing developers to integrate cheminformatics capabilities into applications regardless of their technology stack.

Indigo suits projects requiring chemical structure handling, visualization, or database searching. The toolkit is particularly valuable for drug discovery workflows, combinatorial chemistry applications, and systems that need to compare or analyze molecular data. It includes specialized utilities such as Legio for combinatorial chemistry design, ChemDiff for visual comparison of molecular files, indigo-depict for rendering molecules and reactions, indigo-cano for generating canonical SMILES notation, and indigo-deco for R-group deconvolution. The multi-language binding support makes it accessible whether your project is built in Python, Java, .NET, or runs in the browser via WebAssembly.

The project maintains a modular structure with separate CMake configurations for each component, allowing independent or integrated builds. Development can occur directly on a machine or within a provided Docker dev container for VSCode, with the latter offering a containerized environment that simplifies setup across different operating systems. The codebase requires C++14 support and targets multiple platforms through its diverse binding ecosystem.