Open Source Elixir Software Development Software - Page 3

live_svelte bridges Phoenix LiveView with Svelte components, letting you blend server-driven UIs and client-side interactivity in a single application. It mounts Svelte components from HEEx templates and wires props and events through a small interop layer, so data flows cleanly between LiveView assigns and Svelte state. The integration supports dispatching client events back to LiveView and pushing updates down to the component without writing custom glue for every case. This makes it straightforward to adopt Svelte for isolated, highly interactive widgets—charts, editors, complex form controls—without abandoning LiveView’s real-time model. The project aims to keep build tooling minimal and predictable, so teams can continue using familiar Phoenix asset pipelines. By enabling “islands” of Svelte within LiveView pages, live_svelte offers a pragmatic path to richer UX while preserving Elixir’s server-centric simplicity.

Maru is a DSL for building HTTP/REST APIs in Elixir that emphasizes concise routing, parameter validation, and versioning. Inspired by Ruby’s Grape, it lets you describe endpoints declaratively—paths, verbs, and nested scopes—while composing reusable middleware via Plug. Strong parameter parsing and validators help keep controllers clean by moving input checking and coercion into the route layer. Built-in support for namespacing and API versioning simplifies rolling changes or maintaining multiple client generations side by side. Error handling, helpers, and content negotiation are wired into the DSL, so common cross-cutting concerns are consistent across endpoints. Because Maru sits on Plug and Cowboy, it retains Elixir’s performance and concurrency while making API development fast and readable.

An Elixir library for the Discord API. Nostrum supports clean REST API implementation and rate-limiting, and automatic, configurable maintenance of local caches of Discord data, with extensive query support and cache swapping functionality.

Pusher server implementation is compatible with Pusher client libraries. Open Pusher implementation compatible with Pusher libraries. It's designed to be used as a single registered app with id, secret, and key defined on start. Poxa is a standalone elixir server implementation of the Pusher protocol. Docker images are automatically built by Docker Hub. They are available at Docker Hub. One can generate it using: docker build -t local/poxa. Poxa uses gproc extensively to register websocket connections as channels. So, when a client subscribes for channel 'example-channel', the websocket connection (which is a elixir process) is "tagged" as {pusher, example-channel}. When a pusher event is triggered on the 'example-channel', every websocket matching the tag receives the event.

Sobelow is a security-focused static analysis tool for the Phoenix framework. For security researchers, it is a useful tool for getting a quick view of points-of-interest. For project maintainers, it can be used to prevent the introduction of a number of common vulnerabilities. Potential vulnerabilities are flagged in different colors according to confidence in their insecurity. High confidence is red, medium confidence is yellow, and low confidence is green. A finding is typically marked "low confidence" if it looks like a function could be used insecurely, but it cannot reliably be determined if the function accepts user-supplied input. That is to say, if a finding is marked green, it may be critically insecure, but it will require greater manual validation. This project is in constant development, and additional vulnerabilities will be flagged as time goes on. If you encounter a bug, or would like to request additional features or security checks, please open an issue!

Standard Webhooks is a community-driven specification and set of open-source tools designed to make webhooks consistent, secure, and interoperable across providers. The project defines strict guidelines covering aspects like signature formats, headers, timestamps, replay protection, and forward compatibility. It includes reference implementations for signature verification and signing across multiple languages such as Python, JavaScript/TypeScript, Go, Rust, Ruby, PHP, C#, Java, and Elixir, along with additional community SDKs. The initiative is guided by a technical steering committee with members from companies like Zapier, Twilio, Mux, ngrok, Supabase, Svix, and Kong. Standard Webhooks matters because it eliminates the fragmentation of webhook implementations, reducing consumer effort and enabling seamless verification in apps or even directly in API gateways. By unifying best practices, it improves developer experience, enhances security, and enables new ecosystem tools.

Surface is a component-based UI library for Phoenix LiveView that brings a declarative, template-driven approach to building interactive interfaces. Inspired by frameworks like React, it introduces components with typed properties, slots, and macros to simplify complex UIs. Developers can create reusable, encapsulated components that integrate seamlessly with LiveView’s server-rendered real-time model. Surface emphasizes readability, making templates feel closer to HTML while retaining Elixir’s functional power. It also provides form helpers, event bindings, and a growing ecosystem of ready-to-use UI components. By combining the productivity of declarative components with LiveView’s real-time updates, Surface enables rich, interactive apps without requiring a separate frontend framework like React or Vue.

This is community style guide for the Elixir programming language. Please feel free to make pull requests and suggestions, and be a part of Elixir's vibrant community. If you're looking for other projects to contribute to please see the Hex package manager site. Elixir v1.6 introduced a Code Formatter and Mix format task. The formatter should be preferred for all new projects and source code. The rules in this section are applied automatically by the code formatter, but are provided here as examples of the preferred style. Use Unix-style line endings (*BSD/Solaris/Linux/OSX users are covered by default, Windows users have to be extra careful). Use spaces around operators, after commas, colons and semicolons. Do not put spaces around matched pairs like brackets, parentheses, etc. Whitespace might be (mostly) irrelevant to the Elixir runtime, but its proper use is the key to writing easily readable code.

Timex is a rich, comprehensive Date/Time library for Elixir projects, with full timezone support via the :tzdata package. If you need to manipulate dates, times, datetimes, timestamps, etc., then Timex is for you! It is very easy to use Timex types in place of default Erlang types, as well as Ecto types via the timex_ecto package. If you are coming from an earlier version of Timex, it is recommended that you evaluate whether or not the functionality provided by the standard library Calendar API is sufficient for your needs, as you may be able to avoid the dependency entirely. Timex now delegates to the standard library where possible, and provides backward compatibility to Elixir 1.8 for APIs which are used. This is to avoid duplicating effort, and to ease the maintenance of this library in the future. Take a look at the documentation to see what APIs are available and how to use them.