explaingit

appliedscientific/cardiosafe-benchmark

Analysis updated 2026-05-18

1PythonAudience · researcherComplexity · 3/5Setup · moderate

TLDR

A public dataset and model that predicts whether a drug compound might cause dangerous heart rhythm problems before it reaches a patient.

Mindmap

A visual breakdown will appear here once this repo is fully enriched.

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Screen a list of candidate drug compounds for ion channel blocking risk before costly late-stage testing.

USE CASE 2

Train or benchmark a cardiac safety prediction model using leakage-controlled data splits.

USE CASE 3

Predict blocker probability and potency for hERG, Nav1.5, Cav1.2, and IKs channels from a CSV of molecules.

What is it built with?

Python

How does it compare?

appliedscientific/cardiosafe-benchmarka-bissell/unleash-liteabhiinnovates/whatsapp-hr-assistant
Stars111
LanguagePythonPythonPython
Setup difficultymoderatehardhard
Complexity3/54/53/5
Audienceresearcherresearcherdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires downloading the dataset and label matrix separately from the inference code.

In plain English

CardioSafe is a publicly released dataset and AI model designed to help drug researchers predict whether a chemical compound might be harmful to the heart before it ever reaches a patient. The specific danger it addresses is a compound blocking ion channels, tiny protein gates in heart cells that control electrical signals. When these channels are disrupted, particularly ones named hERG, Nav1.5, Cav1.2, and IKs, the result can be dangerous irregular heart rhythms. Testing for this risk early in drug development can prevent costly late-stage failures. The repository contains three main things. First, a curated label matrix covering 334,444 compounds drawn from ChEMBL 36 and another public dataset, each labeled for whether it blocks one or more of those four ion channels. Second, pre-made data splits designed to prevent a subtle cheating problem called data leakage, where molecules that are very similar to training examples end up in the test set, making a model look better than it actually is. These Tanimoto-controlled splits (tan70 and tan60) use chemical similarity scores to ensure training and test compounds are sufficiently different from each other. Third, a reference deep-learning model with runnable inference code: you can pass in a CSV of molecule structures and get back predictions of blocker probability and potency for each channel. A CiPA (Cardiac in vitro Proarrhythmia Assay) regulatory framework is part of the context, this benchmark is built around the four ion channels that regulators consider most relevant for cardiac safety screening. The code is written in Python, and the full README is longer than what was provided.

Copy-paste prompts

Prompt 1
Show me how to run inference on a CSV of molecule structures using CardioSafe's reference model.
Prompt 2
Explain what data leakage means in CardioSafe's Tanimoto-controlled splits and why it matters.
Prompt 3
Help me understand which four ion channels CardioSafe screens for and why regulators care about them.
Prompt 4
Walk me through the structure of CardioSafe's label matrix covering 334,444 compounds.

Frequently asked questions

What is cardiosafe-benchmark?

A public dataset and model that predicts whether a drug compound might cause dangerous heart rhythm problems before it reaches a patient.

What language is cardiosafe-benchmark written in?

Mainly Python. The stack also includes Python.

How hard is cardiosafe-benchmark to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is cardiosafe-benchmark for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.