Home / geo-tp / ESP32-Bit-Pirate
AI Slop Code RIsk Monitor

geo-tp/ESP32-Bit-Pirate

A Hardware Hacking Tool with Web-Based CLI That Speaks Every Protocol

5.2 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for geo-tp/ESP32-Bit-Pirate, a C++ project with 5,968 GitHub stars. SynthScan examined 203,976 lines of code across 861 source files, recording 831 pattern matches distributed across 12 syntactic categories. The legacy adjusted pattern signal is 5.2 (Moderate pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

5.2
Adjusted Signal
5.2
Raw Pattern Score
100%
Time Factor
2026-10-11
Last Push
6.0K
Stars
C++
Language
204.0K
Lines of Code
861
Files
831
Pattern Hits
2026-10-12
Scan Date
0.03
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 16.6/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 729 finding(s).

Hallucinated Dependency & Supply Chain Risk 4.3/100 · LOW

Are imports declared and package/API names verified? 30 finding(s).

Agent Over-Engineering Ratio 4.3/100 · LOW

Are wrappers, guards, and repeated structures necessary? 105 finding(s).

PR Review Velocity Impact 23.6/100 · LOW

Which changes need focused human review? 831 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 27MEDIUM 66LOW 738

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 831 distinct pattern matches across 12 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block688 hits · 683 pts
SeverityFileLineSnippetContext
LOWtest/test_main.cpp1#include <unity.h>COMMENT
LOWtest/test_main.cpp21#include "../src/Analyzers/I2cFrequencyAnalyzer.cpp"COMMENT
LOWtest/test_main.cpp41#include "../src/Controllers/HdUartController.cpp"COMMENT
LOWtest/test_main.cpp61#include "Transformers/test_TerminalCommandTransformer.cpp"COMMENT
LOWtest/test_main.cpp81#include "Analyzers/test_I2cFrequencyAnalyzer.cpp"COMMENT
LOWtest/test_main.cpp101#include "Shells/test_SpiFlashShell.cpp"COMMENT
LOWtest/Abstracts/test_ANetworkController.cpp1#include <unity.h>COMMENT
LOWtest/Controllers/test_EthernetController.cpp1#include <unity.h>COMMENT
LOWtest/Controllers/test_UartController.cpp1#include <unity.h>COMMENT
LOWtest/Controllers/test_SubGhzController.cpp1#include <unity.h>COMMENT
LOWtest/Controllers/test_WifiController.cpp1#include <unity.h>COMMENT
LOW.github/FUNDING.yml1github: [geo-tp]COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h61#include "ATtinySerialOut.hpp" // Available as Arduino library "ATtinySerialOut"COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h81#define TONE_PIN PIN_PA3COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h101#define LED_BUILTIN PIN_PA6 // use 2 instead of PIN_PA6 for TinyCore32COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h141COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h161#define TONE_PIN 4COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h201 ledcWriteTone(TONE_LEDC_CHANNEL, 0);COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h221#define APPLICATION_PIN PA2COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h241COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h261/*COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h281#define IR_RECEIVE_PIN 2COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h301//#define FEEDBACK_LED_IS_ACTIVE_LOW // The RX LED on the M0-Mini is active LOWCOMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h321#define _IR_TIMING_TEST_PIN 7COMMENT
LOW…les/SimpleReceiverForHashCodes/PinDefinitionsAndMore.h341#define STR(x) STR_HELPER(x)COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h61#include "ATtinySerialOut.hpp" // Available as Arduino library "ATtinySerialOut"COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h81#define TONE_PIN PIN_PA3COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h101#define LED_BUILTIN PIN_PA6 // use 2 instead of PIN_PA6 for TinyCore32COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h141COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h161#define TONE_PIN 4COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h201 ledcWriteTone(TONE_LEDC_CHANNEL, 0);COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h221#define APPLICATION_PIN PA2COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h241COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h261/*COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h281#define IR_RECEIVE_PIN 2COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h301//#define FEEDBACK_LED_IS_ACTIVE_LOW // The RX LED on the M0-Mini is active LOWCOMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h321#define _IR_TIMING_TEST_PIN 7COMMENT
LOWlib/IRremote/examples/UnitTest/PinDefinitionsAndMore.h341#define STR(x) STR_HELPER(x)COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h61#include "ATtinySerialOut.hpp" // Available as Arduino library "ATtinySerialOut"COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h81#define TONE_PIN PIN_PA3COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h101#define LED_BUILTIN PIN_PA6 // use 2 instead of PIN_PA6 for TinyCore32COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h141COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h161#define TONE_PIN 4COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h201 ledcWriteTone(TONE_LEDC_CHANNEL, 0);COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h221#define APPLICATION_PIN PA2COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h241COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h261/*COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h281#define IR_RECEIVE_PIN 2COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h301//#define FEEDBACK_LED_IS_ACTIVE_LOW // The RX LED on the M0-Mini is active LOWCOMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h321#define _IR_TIMING_TEST_PIN 7COMMENT
LOW…xamples/ReceiveAndSendHob2Hood/PinDefinitionsAndMore.h341#define STR(x) STR_HELPER(x)COMMENT
LOW…remote/examples/SendAndReceive/PinDefinitionsAndMore.h61#include "ATtinySerialOut.hpp" // Available as Arduino library "ATtinySerialOut"COMMENT
LOW…remote/examples/SendAndReceive/PinDefinitionsAndMore.h81#define TONE_PIN PIN_PA3COMMENT
LOW…remote/examples/SendAndReceive/PinDefinitionsAndMore.h101#define LED_BUILTIN PIN_PA6 // use 2 instead of PIN_PA6 for TinyCore32COMMENT
LOW…remote/examples/SendAndReceive/PinDefinitionsAndMore.h141COMMENT
LOW…remote/examples/SendAndReceive/PinDefinitionsAndMore.h161#define TONE_PIN 4COMMENT
LOW…remote/examples/SendAndReceive/PinDefinitionsAndMore.h201 ledcWriteTone(TONE_LEDC_CHANNEL, 0);COMMENT
LOW…remote/examples/SendAndReceive/PinDefinitionsAndMore.h221#define APPLICATION_PIN PA2COMMENT
LOW…remote/examples/SendAndReceive/PinDefinitionsAndMore.h241COMMENT
LOW…remote/examples/SendAndReceive/PinDefinitionsAndMore.h261/*COMMENT
628 more matches not shown…
Cross-Language Confusion25 hits · 172 pts
SeverityFileLineSnippetContext
HIGHtest/Adapters/test_sdr_tuning.py49 assert(channel >= 1 && channel <= 13 && second == 0);CODE
HIGHtest/Adapters/test_sdr_tuning.py61 assert(crystal == 0 && khz == 0);CODE
HIGHtest/Adapters/test_sdr_tuning.py72 assert(enabled == 1 && frequency == expected);CODE
HIGH⚡test/Adapters/test_sdr_tuning.py90 assert(frequency == mhz && radio.activeFrequency() == mhz);CODE
HIGH⚡test/Adapters/test_sdr_tuning.py97 assert(calls == sequence && rxEnabled && radio.retunePending);CODE
HIGH⚡test/Adapters/test_sdr_tuning.py102 assert(radio.MIN_CENTER_MHZ == 100 && radio.MAX_CENTER_MHZ == 6000);CODE
HIGH⚡test/Adapters/test_sdr_tuning.py124 assert(failed.status == SdrCaptureService::Status::Frequency && failed.error == ESP_FAIL);CODE
HIGH⚡test/Adapters/test_sdr_tuning.py125 assert(radio.activeFrequency() == 2485 && radio.wifiChannel() == 1);CODE
HIGH⚡test/Adapters/test_sdr_tuning.py126 assert(radio.retuneCount() == before && calls.empty());CODE
HIGH⚡test/Adapters/test_sdr_tuning.py129 assert(radio.wifiChannel() == 6 && calibrations > 0 && pllWrites > 0);CODE
HIGH⚡test/Adapters/test_sdr_tuning.py133 assert(failed.status == SdrCaptureService::Status::Frequency && failed.error == ESP_FAIL);CODE
HIGH⚡test/Adapters/test_sdr_tuning.py134 assert(radio.activeFrequency() == 2437 && radio.wifiChannel() == 6 && calls.empty());CODE
HIGHtest/Adapters/test_sdr_bandwidth_protocol.py80 assert(command.kind == CommandKind::Bandwidth && command.tuningValue == mhz);CODE
HIGHtest/Adapters/test_sdr_bandwidth_protocol.py84 assert(c.kind == CommandKind::Bandwidth && c.tuningValue == 0);CODE
HIGH⚡test/Adapters/test_sdr_bandwidth_protocol.py103 assert(out.size() == 40 && out[4] == 2 && out[5] == 2);CODE
HIGH⚡test/Adapters/test_sdr_bandwidth_protocol.py104 assert(u32(out.data() + 12) == 2437000000u && u32(out.data() + 16) == 80000000u);CODE
HIGH⚡test/Adapters/test_sdr_bandwidth_protocol.py107 assert(out.size() == 40 && out[4] == 2 && out[5] == 3 && u16(out.data() + 6) == 10);CODE
HIGH⚡test/Adapters/test_sdr_bandwidth_protocol.py108 assert(u16(out.data() + 32) == 65535 && out[34] == 255 && out[35] == 255);CODE
HIGH⚡test/Adapters/test_sdr_bandwidth_protocol.py109 assert(u32(out.data() + 28) == 0 && u32(out.data() + 36) == 0);CODE
HIGH⚡test/Adapters/test_sdr_bandwidth_protocol.py114 assert(center == 2438 && session.radio.bandwidthMHz() == 65 && out.empty());CODE
HIGH⚡test/Adapters/test_sdr_bandwidth_protocol.py118 assert(header[4] == 2 && u16(header + 32) == 65 && header[34] == 1 && header[35] == 1);CODE
HIGH⚡test/Adapters/test_sdr_bandwidth_protocol.py126 assert(!session.processStreamControl(center, 256) && session.radio.bandwidthMHz() == -1 && out.empty());CODE
HIGH⚡test/Adapters/test_sdr_bandwidth_protocol.py128 assert(!session.processStreamControl(center, 256) && session.radio.bandwidthMHz() == 0 && out.empty());CODE
HIGH⚡test/Adapters/test_sdr_bandwidth_protocol.py131 assert(out.size() == 40 && out[5] == 3 && u16(out.data() + 6) == 7);CODE
HIGHtest/Adapters/test_sdr_iq10_transport.py34 "-fsanitize=undefined,bounds", "-fno-sanitize-recover=all",CODE
Decorative Section Separators62 hits · 123 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/weekly-firmware-health.yml29 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml31 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml91 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml93 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml105 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml107 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml129 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml131 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml156 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml158 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml247 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml249 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml266 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml268 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml418 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml420 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml602 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml604 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml834 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml836 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml937 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml939 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml973 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml975 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1065 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1067 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1112 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1114 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1152 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1154 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1195 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1197 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1270 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1272 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1366 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1368 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1425 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1427 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1530 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1532 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1563 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1565 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1591 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1593 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1606 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1608 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1634 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1636 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1680 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1682 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1740 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1742 # --------------------------------------------------------COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1814 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1816 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1827 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1829 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1847 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1849 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1877 # ============================================================COMMENT
MEDIUM.github/workflows/weekly-firmware-health.yml1879 # ============================================================COMMENT
2 more matches not shown…
Hyper-Verbose Identifiers33 hits · 41 pts
SeverityFileLineSnippetContext
LOWtest/Adapters/sdr_cdc_waterfall.py95def estimate_usable_bandwidth(offsets_mhz, level_db, threshold_db,CODE
LOW⚡test/Adapters/test_sdr_cdc_client.py20 def test_split_response_and_late_usb_connection(self):CODE
LOW⚡test/Adapters/test_sdr_cdc_client.py27 def test_device_error_and_truncated_frame(self):CODE
LOW⚡test/Adapters/test_sdr_cdc_client.py33 def test_sample_ranges_and_fft_order(self):CODE
LOWtest/Adapters/test_sdr_cdc_client.py61 def test_firmware_capture_counters(self):CODE
LOWtest/Adapters/sdr_cdc_test.py78def validate_capture_counters(before, after, expected):CODE
LOWtest/Adapters/test_sdr_memory.py15 def test_boot_regions_and_ownership(self):CODE
LOWtest/Adapters/test_sdr_bandwidth.py66 def test_register_lifecycle_and_curve(self):STRING
LOWtest/Adapters/test_sdr_cdc_waterfall.py29 def test_usable_bandwidth_follows_baseline_edges(self):CODE
LOWtest/Adapters/test_sdr_cdc_waterfall.py43 def test_span_around_center_is_even_and_clamped(self):CODE
LOWtest/Adapters/test_sdr_cdc_waterfall.py54 def test_consumes_info_terminator_before_binary_mode(self):CODE
LOW⚡test/Adapters/test_sdr_cdc_waterfall.py74 def test_reads_iq_frame_and_exact_payload(self):CODE
LOW⚡test/Adapters/test_sdr_cdc_waterfall.py83 def test_reads_control_frame_without_payload(self):CODE
LOW⚡test/Adapters/test_sdr_cdc_waterfall.py91 def test_rejects_unknown_magic(self):CODE
LOW⚡test/Adapters/test_sdr_cdc_waterfall.py96 def test_rejects_old_version_and_unrequested_packing(self):CODE
LOWtest/Adapters/test_sdr_tuning.py15 def test_exact_frequency_transitions_and_driver_errors(self):CODE
LOWtest/Adapters/test_sdr_bandwidth_protocol.py27 def test_commands_stream_changes_and_frame_versions(self):CODE
LOWlib/IRremote/changelog.md32- Added convenience function isIRReceiverAttachedForTinyReceiver().CODE
LOWlib/IRremote/changelog.md81- Split ISR into ISR and function IRPinChangeInterruptHandler().CODE
LOWlib/IRremote/src/private/IRTimer.hpp1102// Undefine ISR, because we register/call the plain function IRReceiveTimerInterruptHandler()COMMENT
LOWlib/IRremote/src/private/IRTimer.hpp1408// Undefine ISR, because we register/call the plain function IRReceiveTimerInterruptHandler()COMMENT
LOWlib/IRremote/src/private/IRTimer.hpp1483// Undefine ISR, because we register/call the plain function IRReceiveTimerInterruptHandler()COMMENT
LOWlib/IRremote/src/private/IRTimer.hpp1624// Undefine ISR, because we call the plain function IRReceiveTimerInterruptHandler()COMMENT
LOWlib/IRremote/src/private/IRTimer.hpp1730// Undefine ISR, because we register/call the plain function IRReceiveTimerInterruptHandler()COMMENT
LOWlib/IRremote/src/private/IRTimer.hpp1787// Undefine ISR, because we register/call the plain function IRReceiveTimerInterruptHandler()COMMENT
LOWlib/IRremote/src/private/IRTimer.hpp1869// Undefine ISR, because we call the plain function IRReceiveTimerInterruptHandler()COMMENT
LOWlib/IRremote/src/private/IRTimer.hpp1931// Undefine ISR, because we register/call the plain function IRReceiveTimerInterruptHandler()COMMENT
LOWlib/IRremote/src/private/IRTimer.hpp1973// Undefine ISR, because we register/call the plain function IRReceiveTimerInterruptHandler()COMMENT
LOWlib/IRremote/src/private/IRTimer.hpp2003// Undefine ISR, because we register/call the plain function IRReceiveTimerInterruptHandler()COMMENT
LOWwebui/scripts.h558function extractPromptAndTypedPart(lineWithoutAnsi) {CODE
LOWwebui/scripts.h616function filterIncomingTerminalData(data) {CODE
LOWwebui/scripts.h863function saveGeminiApiKeyToStorage() {CODE
LOWwebui/scripts.h884function clearGeminiApiKeyFromStorage() {CODE
Excessive Try-Catch Wrapping9 hits · 9 pts
SeverityFileLineSnippetContext
LOWtest/Adapters/sdr_cdc_waterfall.py231 except Exception as error:CODE
MEDIUMtest/Adapters/sdr_cdc_waterfall.py166def run_stream(self, worker):CODE
LOWtest/Adapters/irtoy_tx_stress.py151 except Exception as exc:CODE
LOWtest/Adapters/irtoy_replay.py125 except Exception as exc:CODE
LOWtest/Adapters/irtoy_record_replay.py168 except Exception as exc:CODE
LOWtest/Adapters/irtoy_smoke_test.py80 except Exception as exc:CODE
LOWtest/Adapters/subghz_raw_cdc_adapter_test.py176 except Exception as exc:CODE
LOW.github/workflows/weekly-firmware-health.yml493 except Exception:CODE
LOW.github/workflows/weekly-firmware-health.yml534 except Exception:CODE
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHlib/RF24/RF24.cpp2216 // Else set level as requestedCOMMENT
Fake / Example Data4 hits · 6 pts
SeverityFileLineSnippetContext
LOW⚡src/Services/UartService.cpp331 byte** dummy_data = (byte**)malloc(sizeof(byte*) * totalBlocks);CODE
LOW⚡src/Services/UartService.cpp334 dummy_data[i] = nullptr;CODE
LOW⚡src/Services/UartService.cpp340 .data_arr = dummy_data,CODE
LOWsrc/Services/UartService.cpp351 free(dummy_data);CODE
Empty Error Handlers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHtest/Adapters/sdr_cdc_waterfall.py226except queue.Empty:CODE
Deep Nesting4 hits · 4 pts
SeverityFileLineSnippetContext
LOWtest/Adapters/sdr_cdc_waterfall.py166CODE
LOWtest/Adapters/sdr_cdc_test.py17CODE
LOWtest/Adapters/sdr_cdc_test.py100CODE
LOWtest/Adapters/test_sdr_memory.py15CODE
Self-Referential Comments2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/upstream-firmware-delivery.yml224 # Create a fresh history containing only the latest upstream builds.COMMENT
MEDIUM…/examples_uno_q/rf24_encoderadiodetails/python/main.py194 """This function is called repeatedly by the App framework."""STRING
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMlib/SX126x-Arduino/src/mac/region/RegionAU915.cpp407 // the node shall utilize 125KHz channels.COMMENT
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWtest/Adapters/sdr_cdc_waterfall.py296CODE