evcxr/evcxr

Evcxr is a Rust evaluation context that enables interactive code execution through multiple interfaces.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 43 minutes ago
Added to GitGenius on September 10th, 2026
Created on September 25th, 2018
Open Issues & Pull Requests: 123 (+0)
GitHub issues: Enabled
Number of forks: 245
Total Stargazers: 6,483 (+0)
Total Subscribers: 50 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 hours
Mean response time: 18.2 hours
90th percentile: 35.9 hours
Tracked items: 42

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 14% of issues opened in the past year have been closed. Three people close 70% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 23
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 810 days
Stale 30+ days: 21
Stale 90+ days: 20

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Evcxr is a Rust evaluation context that enables interactive code execution through multiple interfaces.

The project addresses the need for interactive Rust development by providing an evaluation engine that can execute Rust code dynamically. Rather than requiring compilation and execution cycles typical of standard Rust workflows, evcxr interprets and runs code in an interactive session, allowing developers to test ideas, explore libraries, and debug code without leaving their environment.

The project offers two primary interfaces: a Jupyter kernel for browser-based notebooks and a command-line REPL. The Jupyter kernel is positioned as the recommended entry point, providing a notebook experience in a web browser rather than a terminal interface. The underlying evcxr library provides the common evaluation machinery and can be integrated into other tools. An additional runtime crate supplies functions and traits for libraries to interact with the evaluation context. Developers should choose this tool if they value interactive exploration of Rust code, particularly those familiar with Jupyter notebooks or seeking a more exploratory development style than traditional Rust compilation workflows support.

Development activity shows consistent engagement with the codebase through regular commits addressing both features and maintenance. The project maintains active issue tracking and responds to user reports. Pull requests are reviewed and merged regularly, indicating ongoing stewardship. Documentation is provided through README files for each component and an interactive tour notebook demonstrating capabilities. The maintainers have structured the project into modular crates, suggesting attention to code organization and reusability across different interfaces.