lamda

firerpa/lamda

Android Full-Stack Device Control Platform: WebRTC/H.264 remote desktop, UI/OCR/image-matching automation, one-click MITM, built-in Frida, proxy/VPN/frp/P2P networking, MCP/Agent, 160+ APIs, designed for multi-device clusters and engineered deployments.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
15 Nov 2026
4 days ago
Ship score
73/100
How it is calculated →
Stars, last 7 weeks
no history yet
No weekly sample has been taken for this repository yet.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repository facts

Stars
8.8K
Forks
1.2K
Open issues
48
Watchers
78
Primary language
Python
Created
10 Jul 2022
Owner
firerpa · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 141 startups in the directory ship primarily in Python.

Topics

#adb#agents#ai#ai-agents#android#appium#automation#dynamic-analysis#frida#magisk#mcp#mcp-server#mobile-security#remote-control#reverse-engineering#security#uiautomation#uiautomator2#xposed

How Jev classified this project

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 19 Nov 2026 — os_startup 96%, self-hostable 67%, hosted offering 61%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 19 Nov 2026, found by the weekly discovery job at confidence 0.95. Answered by jev-1.14.0. How the classification works →

Add the status badge to your README

OSSEAN ship status: shipping — last push 15 Nov 2026This is the badge for firerpa/lamda, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/firerpa/lamda.svg)](https://ossean.com/firerpa/lamda)

Updates daily, from the last push GitHub saw.

The badge links to this profile, even after a GitHub rename. GitHub caches README images, so the badge can take a little longer to update there.