Tesla Mod — Flipper Zero & ESP32. Nag killer, FSD region unlock, track mode, BMS dashboard, blind spot alert, high beam strobe, CAN capture, steering mode + more. Works via OBD-II or X179 connector.
C-Rank Grade: B (Solid) - 47/100
External PR Merge Rate: 33%
Response Time: -
First Timer Success: -
hypery11/flipper-tesla-fsd has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in hypery11/flipper-tesla-fsd respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 47.4 places hypery11/flipper-tesla-fsd in the B tier.
The external contributor pull request merge rate for hypery11/flipper-tesla-fsd is 33.3%, based on public PR activity from non-core contributors.
hypery11/flipper-tesla-fsd currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in hypery11/flipper-tesla-fsd. Reviews community pull requests with focus on project quality.
Discussions in hypery11/flipper-tesla-fsd focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/hypery11/flipper-tesla-fsd?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (42% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Summary Tracking issue for the nag killer failing on HW4 / 2026.14.6.x firmware. First report came in from a HW4 2026.14.6.6 user (via email) who can't get nag suppression to work. No confirmed nag-killer-working report exists on any 2026.14.x firmware yet, so this is an open problem, not a misconfiguration. Background The nag killer targets 0x370 EPAS3P_sysStatus (counter+1 echo, handsOnLevel spoof, organic torsion-bar torque). This is a different CAN ID from 0x3FD, so in principle it is not blocked by the 2026.14.x preflight enforcement that disables autosteer on 0x3FD injection (#18, #73). DAS-aware gating reads das_hands_on_state from 0x39B (HW4) / 0x399 (HW3) — byte 5 bits [5:2]. The echo only fires when DAS is actually demanding hands-on. v2.15 added an on-demand grip pulse (#70 / #83) but it is itself unverified on real 14.x hardware (pending @deftdawg's bench). Hypotheses (both need on-car data to confirm) 0x39B DAS_status layout moved on 14.6.x → das_hands_on_state is m
What feature Does esp firmwarw support m5stack atoms3 lite？ Why ？ Known CAN ID / signal name (if any) No response Where it fits in the roadmap No response Anything else No response
Context The English README has been updated extensively since v2.10 — new features, softened claims, corrected hardware docs, etc. The Chinese translations (README_zh-CN.md and README_zh-TW.md) are significantly behind and now contain outdated / incorrect information. A disclaimer was just added to both files (commit b338b8e) but the actual content still needs a full sync. Scope Translate the following sections that changed in the English README since the last translation sync: Ban Shield section rewritten (now marked as CAN-broadcast-layer mask, no confirmed ban-prevention) Force LHD marked as UI-only, slated for removal TLSSC Restore + bit38 recommended banned-car combo added AP-First mode section added Beta features table added 14.3 firmware enforcement warning Hardware section references to HARDWARE.md updated Support / donation section updated How to claim Comment "I'd like to take zh-CN" or "I'd like to take zh-TW" (or both). Native speakers strongly preferred — machine tra
Context @dr-apple (#38), @dahua910 (#38 / #66), and @deftdawg (PR #62 test drive) have all independently confirmed that on ESP32 builds, HW auto-detect misclassifies certain HW3 cars (Intel atom-based MCU especially). The workaround is a one-line patch in main.cpp: fsd_apply_hw_version(&g_state, TeslaHW_HW3); We want this exposed as a persistent user toggle in the web dashboard so users don't have to rebuild the firmware. Scope About 30 lines across 4 files: esp32/.firmware/fsd_handler.h — add bool force_hw3 to FSDState esp32/.firmware/main.cpp — in setup(), after prefs_load(&g_state), if g_state.force_hw3 is true, call fsd_apply_hw_version(&g_state, TeslaHW_HW3) esp32/.firmware/web_dashboard.cpp — add a checkbox "Force HW3" in the Settings section esp32/.firmware/prefs.cpp — save/load the new boolean Constraints Match existing toggle pattern (see force_fsd for reference). Existing user NVS data must not break — new boolean defaults to false. Test that toggling at runtime
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to hypery11/flipper-tesla-fsd, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of hypery11/flipper-tesla-fsd acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 33.3% were successfully merged into the primary branch.
hypery11/flipper-tesla-fsd has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 47.4 places hypery11/flipper-tesla-fsd in the Solid tier.
The external pull request merge rate is 33.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, hypery11/flipper-tesla-fsd currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for hypery11/flipper-tesla-fsd are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.