denoland/rusty_v8

Rust bindings for the V8 JavaScript engine

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 17th, 2026
Created on October 31st, 2019
Open Issues & Pull Requests: 57 (+0)
GitHub issues: Enabled
Number of forks: 418
Total Stargazers: 3,945 (+0)
Total Subscribers: 46 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.2 hours
Mean response time: 214.1 days
90th percentile: 667.6 days
Tracked items: 114

Most active contributors

Sign in to see contributor activity.

How this project is maintained

91% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 23
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 421 days
Stale 30+ days: 18
Stale 90+ days: 11

Recent activity

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

Top labels

  • enhancement (10)
  • bug (7)
  • documentation (2)
  • good first issue (2)
  • help wanted (1)

Most active issues this week

Detailed Description

Rusty V8 is a Rust binding library that provides high-fidelity access to the V8 JavaScript engine's C++ API.

The project solves the problem of integrating V8 into Rust applications while maintaining performance and security. Rather than relying on pre-built binaries that obscure their contents and complicate upgrades, Rusty V8 builds V8 from source during the cargo build process. The binding preserves the original V8 API structure closely, avoiding additional call overhead that plagued earlier attempts. To manage V8's substantial compilation time and size constraints, the project offers a practical compromise: binary downloads are the default for faster builds, while source compilation remains available for development and CI workflows.

Developers should choose this binding if they need to embed JavaScript execution in Rust with minimal performance overhead and full control over V8's configuration. It suits projects that require staying current with V8 releases, since the versioning scheme aligns with Chrome's four-week release cycle. The tool is particularly valuable for teams concerned about supply chain security, as the ability to build from source eliminates reliance on opaque binary artifacts. Projects with strict performance requirements or those needing custom V8 configurations will benefit from the source-building capability, while most users can rely on prebuilt binaries for faster iteration.

The project maintains active development with regular major version releases synchronized to Chrome's schedule. The CI pipeline consistently builds from source to catch integration issues early. The maintainers provide flexibility through environment variables that allow users to switch between prebuilt and source builds, force debug or release linking, and redirect binary downloads to custom mirrors, indicating responsiveness to diverse deployment scenarios.