Repo brief: pojala/electrino

Generated by RepoPilot · document generated 2026-09-13 · concise human review Evidence snapshot · analyzed 2026-09-13T10:47:02.778Z · commit 0bf75954b564

Verdict

Mixed — Stale — last commit 3y ago

• 7 active contributors
• Distributed ownership (top contributor 44% of recent commits)
• MIT licensed
• Tests present

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Electrino is a lightweight desktop application runtime that uses the system's native web browser engine (WebKit on macOS, EdgeHTML on Windows) to run web-based apps, achieving a 115 MB reduction compared to Electron (167 kB vs 115 MB for Hello World). It implements a minimal Electron-compatible API surface (app, BrowserWindow, ipcMain, Tray, nativeImage) written in Objective-C for macOS and C# for Windows, enabling developers to ship small, platform-native desktop apps without bundling a full Chromium engine. Platform-specific monolithic structure: Electrino/macOS/ contains all Objective-C source files (ENOJSBrowserWindow.m, ENOJSIPCMain.m, etc.) implementing the API bridge to macOS…

Start here

Open these first:

• Electrino/macOS/Electrino/ENOJavaScriptApp.m — Core macOS runtime that bootstraps the JavaScript app environment and bridges native APIs to JavaScript
• Electrino/macOS/Electrino/AppDelegate.m — macOS application entry point that initializes the Electrino runtime and manages app lifecycle
• Electrino/macOS/Electrino/ENOJSApp.m — JavaScript-exposed app API module providing fundamental application control (quit, version, etc.)
• Electrino/macOS/Electrino/ENOJSIPCMain.m — Inter-process communication main module enabling message passing between JavaScript frontend and native backend
• Electrino/macOS/Electrino/ENOJSBrowserWindow.m — BrowserWindow implementation for macOS that manages native windows hosting web content

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/pojala/electrino.git
cd electrino/Electrino/macOS
open Electrino.xcodeproj

Then build via Xcode (macOS development requires Xcode 10+). For Windows, a separate Visual Studio setup would be needed (not shown in files). Test the example app at Electrino/test-app/ after building the runtime.

Daily commands:

macOS: Open Electrino/macOS/Electrino.xcodeproj in Xcode and press Cmd+R to build and run. The test apps (test-app/main.js, test-tray/main.js) serve as entry points—they load HTML via WebView and communicate with native…

…shortened for this brief.

Key cautions & unknowns

• Stale — last commit 3y ago
• No explicit build instructions or environment setup documentation visible—Xcode version requirements and macOS deployment target are locked in the .pbxproj file, not documented. The Objective-C code assumes developers…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.