sindresorhus/execa

Process execution for humans

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 8th, 2026
Created on December 5th, 2015
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 264
Total Stargazers: 7,603 (+0)
Total Subscribers: 43 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.2 hours
Mean response time: 80.3 days
90th percentile: 211.8 days
Tracked items: 55

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 8% of issues opened in the past year have been closed. Three people close 95% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 433 days
Stale 30+ days: 0
Stale 90+ days: 0

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 (2)
  • help wanted (2)
  • bug (1)

Detailed Description

Execa is a process execution library for Node.js that provides a human-friendly interface for running commands programmatically.

The tool solves the problem of executing external processes from Node.js code in a way that is safer and more convenient than using the native child_process module directly. It is optimized for programmatic usage rather than shell scripting, handling the complexities of spawning processes, managing streams, and capturing output in a way that integrates naturally with JavaScript code.

Execa suits any Node.js project that needs to run external commands, whether for build tools, CLI applications, automation scripts, or system integration tasks. It is particularly valuable when you need reliable error handling, output capture, and process management without the quirks and security concerns of shell-based execution. Developers should choose it over direct child_process usage when they want a more ergonomic API and better defaults for common scenarios.

The project maintains steady activity with regular updates and bug fixes. Development is responsive to issues and pull requests, indicating active maintenance. The codebase receives ongoing refinement and improvements to its core functionality and documentation.