erlang/otp

Erlang/OTP

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 4th, 2026
Created on November 16th, 2009
Open Issues & Pull Requests: 587 (+0)
GitHub issues: Enabled
Number of forks: 3,287
Total Stargazers: 12,348 (+0)
Total Subscribers: 545 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.1 hours
Mean response time: 14.9 days
90th percentile: 6.7 days
Tracked items: 765

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "not a bug" is answered fastest, typically in about an hour, while "enhancement" waits about 2 days. 51% of tracked open issues have had no activity in three months. Only 7% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 168
New in 7 days: 10
Closed in 7 days: 13
Avg open age: 573 days
Stale 30+ days: 141
Stale 90+ days: 126

Recent activity

Opened in 7 days: 10
Closed in 7 days: 11
Comments in 7 days: 9
Events in 7 days: 48

Top labels

  • bug (545)
  • team:VM (467)
  • team:PS (234)
  • enhancement (123)
  • help wanted (57)
  • stalled (31)
  • not a bug (29)
  • priority:low (27)

Detailed Description

Erlang/OTP is a programming language and runtime system for building massively scalable soft real-time systems with high availability requirements.

Erlang addresses the challenge of writing distributed, fault-tolerant systems by providing a language designed around lightweight processes and message passing. The runtime uses preemptive scheduling to manage thousands or millions of concurrent processes efficiently. OTP extends this foundation with a collection of libraries, ready-to-use components, and established design principles that guide developers in structuring reliable applications. The approach emphasizes "let it crash" semantics, where supervisor processes automatically restart failed components, enabling systems to recover from errors without manual intervention.

Erlang/OTP suits teams building telecommunications infrastructure, messaging systems, real-time monitoring platforms, or any application where availability and concurrency matter more than raw single-threaded performance. The learning curve is steep for developers accustomed to imperative languages, as Erlang requires thinking in terms of processes and pattern matching rather than shared mutable state. Organizations should commit to learning both the language and OTP's architectural patterns to realize its benefits; it is not a drop-in replacement for general-purpose languages but rather a specialized tool for specific problem domains.

The project maintains an active contribution process with a formal contribution guide and a help-wanted issue list for community involvement. Security vulnerabilities are handled through a dedicated disclosure process rather than public channels. The codebase accepts bug fixes and improvements from external contributors following established development procedures.