This repository contains the Momentum firmware for a multi-protocol wireless device (Flipper Zero). It implements a modular embedded operating system with hardware abstraction layer (HAL) for STM32 microcontrollers, supporting NFC, Sub-GHz, infrared, iButton, GPIO, Bluetooth, and USB protocols. The firmware features a scene-based UI framework, service-oriented architecture (power, storage, GUI, notification), plugin system for extensibility, and JavaScript scripting capability. Key architectural patterns include resource management via furi_record, event-driven communication using Furi's kernel primitives, and consistent GUI module design. The codebase demonstrates strong embedded systems craftsmanship with clear separation of concerns, reusable components, and active maintenance.
This repository is a curated dataset of NFC tag dumps (`.nfc` files) from Toniebox audio figures, organized by language (English, French, German) and character series. The primary purpose is to enable emulation of Tonie figures on Flipper Zero devices using the official firmware's SLIX-L chip support. The dataset includes over 850 dumps, each containing the full memory image of an ISO15693 SLIX tag (UID, data content, passwords). Supporting scripts provide validation (`validate_files.sh`), automated directory listing generation (`build_directories.sh`), and a GUI tool (`figures_name_tool.pyw`) that uses upstream metadata from `tonies-json` to help contributors correctly place new dumps. The repository is part of the Toniebox reverse-engineering ecosystem and relies on community contributions. While the codebase is minimal, the data is well-structured and validated through CI pipelines, making it a reliable resource for Flipper Zero users.
This repository is a comprehensive reverse-engineering project for PixMob LED wristbands, focusing on both infrared (IR) and radio frequency (RF) control protocols. The primary data assets are raw signal captures from live events (Coldplay, NBA games, Disney experiences) stored in Flipper Zero .ir and .sub formats, along with EEPROM dumps and hardware PCB photos. The research has produced a curated database of over 500 effect definitions (colors, fades, blinks) in Python and JavaScript, conversion utilities for translating raw captures to bit sequences and Arduino serial commands, and tools for brute-forcing unknown codes. While the repo includes functional application code (Arduino sketches, web interface, Python demos), its dominant character is data research: the code exists to document and exploit the protocol, not to serve as a standalone application. The project is well-organized with clear directory structure, pinned Python dependencies, and extensive documentation of the discovery process.
This repository is a community-driven collection of DuckyScript payloads designed for USB Rubber Ducky, Flipper Zero, and other HID attack devices. It primarily functions as a playbook for penetration testers and red teamers, offering ready-to-inject scripts that automate keystroke injection attacks. The codebase is organized into a flat file tree by platform (Windows, Linux, macOS, mobile) and category (credentials, remote_access, destructive, prank, exfiltration, recon, execution, etc.). Each payload is a self-contained DuckyScript file, often embedding PowerShell, Bash, or Python one-liners that are typed and executed on the target machine. The repository includes hundreds of payloads covering credential theft (e.g., browser password dumping, WiFi key extraction), remote access (reverse shells, persistence via systemd, scheduled tasks), destructive actions (fork bombs, zip bombs, file corruption), exfiltration (webhook, Dropbox, email), and pranks (RickRolls, fake updates, desktop trolling). The architecture is not a traditional application but a script library; the 'code' is primarily configuration/scripting rather than compiled software. Maintenance is active, with monthly snapshot tags and contributions, though many payloads suffer from hardcoded URLs and dependencies on specific OS versions, leading to moderate technical drift. The repository does not contain data pipelines, notebooks, or ML models.
RogueMaster/awesome-flipperzero-withModules is a Flipper Zero resource distribution hub rather than a conventional runnable application. Its dominant content is a curated awesome-list plus a massive asset dump: the README links to hundreds of community resources (BadUSB payloads, Sub-GHz databases, NFC tools, custom firmware), while the repository itself stores custom firmware update bundles, ESP32 flasher images, WAV files, a few firmware-level C source variants, and tens of thousands of dolphin animation frame binaries organized into themed packs (Anime, Pokemon, Logos, CHERRY, 420, etc.). The only real code is a set of near-identical Flipper animation-manager C files, a small NFC hex-to-binary shell script, and Python dependency helpers for animation tooling. There is no server, API, library interface, CLI application, or build pipeline. Architecturally this is a flat asset repository with no deduplication, no tests, no dependency management, and no validation. Identical .bm bitmap frames and meta.txt animation manifests are copied across many theme directories, causing enormous repository bloat and synchronization drift. The Flipper animation format itself is consistent and well-defined (Flipper Animation v1 metadata, 128x64 monochrome frames, manifest entries with level/butthurt ranges and weights), making the asset schema the most reusable aspect for Flipper modders. However, the codebase surrounding it is weak: no automation, inconsistent metadata edge cases, WIP/uncompiled animation directories mixed into the tree, and high link-rot risk across the curated README. For engineers, this repository is best treated as a catalog of Flipper Zero content and a source of example animation packaging, not as a software system to integrate or extend. It is actively maintained in the sense that new assets and firmware builds are pushed, but engineering quality is below average for a code repository. It would need an asset pipeline, checksumming, deduplication, and manifest validation before it could be considered well-crafted.