firecracker-microvm/firecracker

Secure and fast microVMs for serverless computing.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 5 minutes ago
Added to GitGenius on April 12th, 2026
Created on October 19th, 2017
Open Issues & Pull Requests: 113 (+0)
Number of forks: 2,581
Total Stargazers: 36,268 (+0)
Total Subscribers: 351 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.7 days
Mean response time: 240.7 days
90th percentile: 1099.1 days
Tracked items: 218

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. Work labelled "Roadmap: Tracked" is answered fastest, typically in under an hour, while "Type: Fix" waits about 23 months. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 46
New in 7 days: 1
Closed in 7 days: 2
Avg open age: 822 days
Stale 30+ days: 37
Stale 90+ days: 30

Recent activity

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

Top labels

  • Status: Parked (71)
  • Priority: Low (70)
  • Type: Enhancement (39)
  • Status: WIP (38)
  • Good first issue (36)
  • Roadmap: Tracked (26)
  • Status: Awaiting author (22)
  • Type: Bug (19)

Detailed Description

Firecracker is a virtual machine monitor that creates and manages lightweight virtual machines for serverless computing and multi-tenant container workloads.

Firecracker addresses the need for secure, fast execution of functions and containers with minimal overhead by implementing a minimalist virtual machine monitor built on the Linux Kernel Virtual Machine. It strips away unnecessary devices and guest-facing functionality to reduce memory footprint, attack surface, startup time, and improve hardware utilization. The tool combines hardware virtualization's security and isolation properties with the speed and flexibility of containers, enabling secure multi-tenant execution models.

Firecracker suits organizations running serverless platforms, function-as-a-service systems, or dense container workloads where security isolation and resource efficiency matter. It works well for teams that can configure and manage a Linux host operating system appropriately for multi-tenant scenarios. The tool has been integrated into container runtimes including Kata Containers and Flintlock, making it suitable for projects that need a runtime foundation rather than a standalone virtualization layer.

The project receives most of its issue reports from outside users rather than the core team, reflecting a substantial base of production adopters. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker is dominated by parked items, low-priority tasks, and work-in-progress items, suggesting a measured pace of development focused on stability and incremental improvements rather than rapid feature expansion.