awslabs/llrt

LLRT (Low Latency Runtime) is an experimental, lightweight JavaScript runtime designed to address the growing demand for fast and efficient Serverless...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 43 minutes ago
Added to GitGenius on September 7th, 2026
Created on September 20th, 2023
Open Issues & Pull Requests: 41 (+0)
GitHub issues: Enabled
Number of forks: 394
Total Stargazers: 8,803 (+0)
Total Subscribers: 48 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 28.6 hours
Mean response time: 15.7 days
90th percentile: 15.3 days
Tracked items: 182

How this project is maintained

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 28
New in 7 days: 0
Closed in 7 days: 2
Avg open age: 618 days
Stale 30+ days: 25
Stale 90+ days: 25

Recent activity

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

Top labels

  • bug (34)
  • enhancement (28)
  • help wanted (8)
  • rust (2)
  • wontfix (2)
  • dependencies (1)
  • documentation (1)
  • javascript (1)

Detailed Description

LLRT is a lightweight JavaScript runtime designed for serverless applications that prioritizes fast startup and low resource consumption on AWS Lambda.

LLRT addresses the performance demands of serverless workloads by providing significantly faster cold starts and lower overall execution costs compared to traditional JavaScript runtimes. Built in Rust and powered by the QuickJS JavaScript engine, it achieves efficient memory usage and rapid initialization. The runtime supports ES2023 JavaScript features while maintaining a minimal footprint suitable for resource-constrained Lambda environments.

Developers should adopt LLRT for Lambda functions where startup latency and cost efficiency are critical priorities, particularly for workloads with frequent cold starts or tight memory budgets. The tool is not a drop-in replacement for Node.js; code must be tested for compatibility, and dependencies should be bundled for a browser platform with AWS SDK packages marked as external. LLRT can be deployed via custom runtime, Lambda layer, container image, AWS SAM, or AWS CDK constructs. The project explicitly warns that LLRT remains experimental and subject to change, intended primarily for evaluation purposes rather than production use without careful consideration.

The project maintains a structured testing approach with unit tests for isolated component validation, end-to-end tests for AWS SDK integration verification, and web platform tests for standards compliance. Development activity shows active engagement with compatibility concerns, as evidenced by the detailed compatibility matrix and API documentation provided to guide adoption decisions.