chakra-core/chakracore

ChakraCore is an open source Javascript engine with a C API.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 7th, 2026
Created on January 5th, 2016
Open Issues & Pull Requests: 615 (+0)
GitHub issues: Enabled
Number of forks: 1,221
Total Stargazers: 9,256 (+0)
Total Subscribers: 416 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

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: 857 days
Stale 30+ days: 22
Stale 90+ days: 18

Recent activity

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

Top labels

  • Bug (14)
  • Build Break (4)
  • good first issue (4)
  • Codebase Quality (3)
  • help wanted (3)
  • Build Bug (2)
  • APIs (1)
  • By Design (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

ChakraCore is a JavaScript engine with a C API that you can embed in C and C++ projects to add JavaScript support.

ChakraCore solves the problem of integrating JavaScript execution into native applications by providing a runtime that can be compiled and linked into C-compatible projects. The engine exposes a C API called JSRT that allows developers to execute JavaScript code, manage objects, and interact with the host environment from native code. It supports x64 processors on Linux, macOS, and Windows, with x86 and ARM support currently limited to Windows.

The tool suits embedded use cases and applications that need lightweight JavaScript execution without external dependencies. If you are building a native application that requires scripting capabilities or dynamic code execution, ChakraCore provides a self-contained solution. The project is community-maintained following Microsoft's transition away from it in the Edge browser, so it is positioned for long-term use in embedded scenarios rather than as a general-purpose JavaScript runtime.

Development activity shows that the project maintains a community-driven approach with open channels for contribution and discussion. The repository includes comprehensive documentation covering architecture, embedding quickstarts, and API references to support integration work. The project explicitly invites interested parties to participate and has established planning documents for future releases targeting embedded use cases.