Issue dossier

The source tree includes a firmware sketch and external development references, but reviewed sources do not establish a tagged final release, signed binary, source-to-unit mapping, build lockfile, deployment inventory, update policy, recovery process, support lifecycle, or safe end-user operating, calibration, or reconfiguration procedure. No flashing, configuration, or connection directions are reproduced here.

A linkable camp-impact record with badge context, severity, evidence confidence, and source notes.

Back to issues index

firmware release and operating-procedure boundary · public repository review · firmware sketch published; final deployment/support record unrecovered

The catalogue links source evidence without presenting it as a supported, reproducible, current, or safe modification workflow.

Badge
CyberNorth CyberFest 2025 Compass Badge
Category
firmware release and operating-procedure boundary
Severity
note
Confidence
public repository review
Status
firmware sketch published; final deployment/support record unrecovered
Timeframe
current catalogue build
Source note
cyberfest-2025-badge repository and firmware sketch.

Evidence

Related Resources

Source trail

Evidence Sources

CyberNorth · retrieved 2026-05-15

CyberFest 2025

Primary official CyberNorth page for the 2025 month-long CyberFest cybersecurity festival, October 7 Community Conference, and named Punk Security sponsor context. It does not document the badge's technical details or allocation.

Badge: CyberNorth CyberFest 2025 Compass Badge

Punk Security / GitHub · retrieved 2026-05-15

cyberfest-2025-badge

Primary maker archive for the CyberNorth CyberFest 2025 Compass Badge, its conference-distribution statement, ATtiny412/button/CR2032/5050-NeoPixel/LIS2MDLTR parts statement, source files, and compass-feature account. It does not establish a final production run, named recipient ledger, universal final-unit parity, or selected image licence.

Badge: CyberNorth CyberFest 2025 Compass Badge