Not just specs

Issues & Camp Impact

Safety warnings, delivery problems, app-store gaps, team-process history, and first-hand reports are tracked as sourced records.

Reset
1262 matching issue record(s)

image provenance upgrade · repository license and exact raster source · licensed original repository render applied

The Ekoparty 2025 visual uses the repository's GPL-3.0 `2D_PCB1_2025-10-20.png` upstream raster render.

The South American entry now has a rights-cleared official upstream render with source URL, license, attribution, and processing notes while avoiding generated or placeholder imagery.

Source note: Ekoparty_Badge_2025 repository image file, LICENSE, and badge.gallery image policy.

image provenance upgrade · repository render and MIT license · licensed official render applied

The BornHack 2026 visual now uses an optimized WebP derived from the official `imgs/badge-front.png` Cyber Ægg front render in the MIT-licensed Ranzbak/bornhack2026-hardware Codeberg repository.

The public badge page, image archive, and API point at a licensed upstream repository render with source URL, MIT license basis, attribution, and processing notes while avoiding generated, placeholder, social, or uncleared imagery. The render is a pre-event prototype illustration, not a shipped-product photograph, and the record keeps that distinction explicit.

Source note: Ranzbak/bornhack2026-hardware Codeberg repository imgs/badge-front.png, MIT LICENSE, and badge.gallery image policy.

image reuse boundary · local image policy and source review · left image-free

NodeWatch, NearForm, Flickr, Cloudinary, Hackster, and article media were not copied because this pass did not establish a complete reusable image license, attribution, source URL, and processing-provenance chain for a specific badge photo or official upstream raster.

The NodeConf EU 2019 page remains source-backed and image-free instead of publishing an unclear or synthetic watch image.

Source note: badge.gallery image policy and NodeWatch/NearForm media-source review.

image-license boundary · repository license plus image policy · documented

The repository includes Apache-2.0 licensing for the published source tree, but that alone is not used here as proof that any particular documentary badge photo is reusable with full attribution and processing provenance.

The catalogue records the repository license while leaving the visual slot empty until a specific image can be cleared under the project image rules.

Source note: 2018-banglet LICENSE and badge.gallery image policy.

image-rights boundary · local project policy · needs licensed original replacement

No local AND!XOR DC28 image is published because this pass did not pair a specific physical badge photo or official upstream full-board raster with complete reusable image rights, attribution, source URL, and processing notes.

The record remains image-free rather than copying Hackaday.io media, social posts, repository-adjacent screenshots, article images, or generated artwork.

Source note: badge.gallery image policy, AND!XOR DC28 Hackaday.io media, and public repository image-source review.

image-rights boundary · local project policy · needs licensed original replacement

The first-hand post and coverage pages include badge photos or media, but this pass did not recover a badge photo or official render with complete reusable image license, attribution, source URL, and processing provenance.

The entry remains source-backed and image-free rather than copying blog, SparkFun, Hackaday, or event media without explicit reuse permission.

Source note: badge.gallery image policy, Datko write-up media, SparkFun repost media, and Hackaday coverage media.

image-rights boundary · local project policy · needs licensed original replacement

Cisco and official archive pages contain event or badge-related media, but this pass did not recover a badge photo or official render with complete reusable image license, attribution, source URL, and processing provenance.

The entry remains source-backed and image-free rather than copying Cisco blog, archive, or event media without explicit reuse permission.

Source note: badge.gallery image policy, Cisco badge write-up media, and SAINTCON 2015 archive media.

image-rights boundary · local project policy · needs licensed original replacement

The ReadTheDocs badge documentation includes finished-example and assembly photos, but no recovered source pairs those images with a reusable image license, explicit permission basis, attribution, and processing notes for publication.

The entry remains source-backed and image-free rather than copying documentation photos or archive media without complete provenance.

Source note: badge.gallery image policy and SAINTCON 2016 badge documentation media.

image-rights boundary · local project policy · needs licensed original replacement

The official badge page and manual contain badge-related images, but no recovered source pairs those images with a reusable image license, explicit permission basis, attribution, and processing notes for publication.

The entry remains image-free rather than copying official-page photos, manual screenshots, GitLab Pages media, or social images without complete provenance.

Source note: badge.gallery image policy, SAINTCON 2017 badge page, and SAINTCON 2017 GitLab Pages manual.

image-rights boundary · local project policy · needs licensed original replacement

The DC540 post and recovered archive/media trail do not provide a complete reusable image license, attribution, source URL, and processing provenance for badge photos or page imagery.

The record remains source-backed and image-free rather than copying first-hand blog or archive images without explicit reuse permission.

Source note: DC540 first-hand badge write-up, SAINTCON 2020 archive media, and badge.gallery image policy.

image-rights boundary · local project policy · needs licensed original replacement

Hackaday and Handorf publish real badge photos and build images, but this pass did not recover complete reusable image rights, attribution, source URL, and processing notes for local catalogue publication.

The record remains source-backed and image-free rather than copying article or build-guide media without a clear reuse basis.

Source note: badge.gallery image policy, Hackaday field-report media, Hackaday workshop media, and Handorf build-guide photos.

image-rights boundary · local project policy · needs licensed original replacement

No local Hackfest 2019 badge image is published because this pass did not pair any specific badge photo or official raster with reusable image rights, attribution, source URL, and processing notes.

The entry remains image-free rather than copying event media, Flickr photos, screenshots, social images, or generated placeholder art.

Source note: badge.gallery image policy, Hackfest history photo links, Hackfest 2019 schedule, and Hackfest CTF source trail.

image-rights boundary · local project policy · needs licensed original replacement

No local BSides Vancouver 2019 Badge image is published because this pass did not pair a specific original badge photo or official raster with reusable image rights, attribution, source URL, and processing notes.

The entry remains image-free rather than copying event media, maker photos, social images, screenshots, or generated placeholder art.

Source note: badge.gallery image policy and BSides Vancouver 2019 source trail.

image-rights boundary · local project policy · needs licensed original replacement

The official CHV page, IOActive build posts, and GitHub repositories include useful badge-related imagery, but this pass did not recover a specific badge photo or full-board render paired with reusable image rights, attribution, and processing provenance for publication.

The record remains image-free rather than copying event-page images, blog photos, repository images, social previews, screenshots, generated art, or approximate badge artwork.

Source note: badge.gallery image policy, Car Hacking Village DEF CON 32 page, IOActive key-fob badge posts, and public CHV repositories.

image-rights boundary · local project policy · needs licensed original replacement

The build post includes useful assembled-badge images and video, but this pass did not recover an explicit reusable image license, attribution basis, and processing provenance for catalogue publication.

The record remains image-free rather than copying blog photos, OpenGraph images, videos, screenshots, repository diagrams, generated art, or approximate badge artwork.

Source note: badge.gallery image policy and CynicalSignals BadgeBuddy writeup.

image-rights boundary · local project policy · needs licensed original replacement

The Hackster project includes real badge images and build-media context, but this pass did not recover an explicit reusable image license, permission basis, attribution requirement, and processing provenance for local catalogue publication.

The record remains image-free rather than copying Hackster project media, screenshots, OpenGraph images, generated art, or approximate badge artwork.

Source note: badge.gallery image policy and Hackster project page.

kit-completion caveat · primary source · documented

The base badge worked as a spectrum analyzer, while full Ubertooth-capable behavior required a larger hacking kit and additional firmware installation on both microcontrollers.

The catalogue separates shipped badge behavior from optional kit upgrades and does not imply that every attendee badge was fully populated as an Ubertooth.

Source note: Great Scott Gadgets ToorCon 13 badge page and Project Ubertooth source tree.

license and media caveat · source-limited audit · needs deeper license audit

This pass did not identify a clear project-wide license on the Hackaday.io Remoticon.2 files that would support local reuse of project photos, renders, or artwork as catalogue images.

The project is cited for artifact facts and fabrication context, but image and artwork reuse is withheld pending explicit license or permission evidence.

Source note: Remoticon 2 badge Hackaday.io project, files page, Hackaday article media, OSH Park previews, and badge.gallery image policy.

license boundary · repository files · documented

The PCB repository includes CC BY-SA 3.0 licensing, while the firmware file carries a permissive source-header notice and the repositories do not provide a single unified image/documentation rights statement for publishable badge media.

The record cites code and hardware sources but does not reuse repository artwork or social/event imagery as a hero image.

Source note: pdxbadgers/pcb-2015 COPYING.TXT and pdxbadgers/fw-2015 badger.ino.

license gap · repository inspection · no license file

The punk-security repository carries no LICENSE file, no license header in firmware.ino, and no license badge in the GitHub sidebar, so the firmware is treated as all-rights-reserved rather than redistributable.

The catalogue records the verified hardware and challenge surface without claiming redistribution rights over the firmware or any derivative.

Source note: punk-security/bsides-leeds-2026-badge repository file tree and firmware.ino.

license scope caveat · GitHub API, repository README, and license files · documented

GitHub detects GPL-3.0 for the repository, while the README and LICENSE_HARDWARE.md state that hardware documentation is under CERN Open Hardware Licence v1.2 and that Electronic Cats and BugCON trademarks are not granted for PCB sales.

The catalogue can cite GPL software and CERN-OHL hardware documentation while avoiding assumptions that firmware, photos, logos, screenshots, KiCad renders, trademarks, or other media all share one reuse scope.

Source note: ElectronicCats/Badge-BugCON2023 README, LICENSE, LICENSE_HARDWARE.md, and GitHub API metadata.

license scope caveat · primary repository · documented

The repository README states the hardware is released under CERN Open Hardware Licence v1.2, while the license text itself says software and firmware are outside that license unless explicitly expressed.

The compendium can cite the open-hardware release while avoiding assumptions that all firmware, screenshots, photos, or repository media share the same reuse terms.

Source note: BugCON 2024 repository README and LICENSE_HARDWARE.md.

license scope caveat · GitHub API, repository tree, and README · documented with caution

GitHub reports no detected top-level license for `ElectronicCats/badge-bugcon-2025`, and the README says to consult license files without exposing a simple whole-repository license for hardware, firmware, photos, diagrams, or artwork.

The catalogue can cite the open-hardware claim and public source while avoiding assumptions that firmware, SDK material, readme images, KiCad renders, logos, or event graphics are reusable publication assets.

Source note: ElectronicCats/badge-bugcon-2025 repository metadata, README, and badge.gallery image policy.

license scope caveat · repository README and license files · documented

The repository is GitHub-detected as GPL-3.0 and the README separately states the hardware is released under CERN Open Hardware Licence v1.2. This record treats software, firmware, hardware documentation, and the selected hardware-tree raster according to their documented scopes rather than assuming one license covers every asset.

The catalogue can cite and publish the selected hardware render while keeping firmware/source licensing and event trademarks separate from the hardware-documentation reuse basis.

Source note: ElectronicCats/Badge-bsides-cdmx-2025 README, LICENSE, LICENSE_HARDWARE, and GitHub API metadata.

license scope caveat · repository README and store page · documented with caution

The README says firmware is GNU AGPL v3.0 and hardware is CERN Open Hardware Licence v1.2, but this pass does not treat product photos, screenshots, GitHub attachments, logos, trademarks, or store media as reusable image assets.

The catalogue can cite the source and hardware release while keeping image publication and trademark reuse separate from code and hardware licensing.

Source note: HackGDL 2025 badge README, Electronic Cats product page, and badge.gallery image policy.

license-file caveat · GitHub API and repository README · documented with caution

The README says hardware is released under CERN Open Hardware Licence v1.2 and says to consult a LICENSE_HARDWARE file, but this pass found no top-level `LICENSE_HARDWARE.md` through the GitHub contents API and GitHub reports no detected repository license.

The catalogue can cite the README's open-hardware claim and public source while avoiding assumptions that firmware, photos, readme images, logos, KiCad renders, or other repository media are reusable publication assets.

Source note: ElectronicCats/Badge-BugCON-2022 README, repository metadata, GitHub contents API 404 for LICENSE_HARDWARE.md, and badge.gallery image policy.

license-scope caveat · repository metadata and README review · needs explicit license clarification

GitHub reports the repository license as MIT, while the README says the hardware is released under CERN Open Hardware Licence v1.2; the source pass did not recover the referenced LICENSE_HARDWARE file.

The catalogue links repository images, diagrams, and hardware files as evidence but does not copy media or collapse the software, hardware, documentation, and artwork license boundaries.

Source note: ElectronicCats/badge-44con-2025 GitHub metadata and README.

lineage and revision caveat · official article plus project notes · documented

Hackaday says the Berlin badge was re-skinned and included a couple hardware tweaks, but stayed 100% compatible with the 2022 Supercon badge.

The catalogue records the Berlin artifact as an event-specific revision while avoiding unsupported claims about exact PCB changes until a Berlin-specific hardware archive is recovered.

Source note: Hackaday Berlin badge preview and v0j4 project notes.

lineage reuse · source-backed · documented

The Supercon II badge intentionally reused the core Hackaday Belgrade badge concept while changing visual design, integrating the accelerometer, exposing expansion pads, and updating the bootloader.

The compendium keeps the US Pasadena record separate while preserving the Serbian Belgrade design lineage and shared firmware roots.

Source note: Hackaday.io Supercon II project and Design And Hacking Drilldown article.

lineage-behavior caveat · retrospective source only · documented as lineage context

Later sponsor-pack material says past BSides Perth electronic badges displayed sponsor messages, schedules, and CTF challenges, but the recovered source does not identify which exact year carried each feature.

The 2018 entry cites this only as broader Perth lineage context and does not treat it as direct 2018 behavior proof.

Source note: BSides Perth 2021 sponsor-pack transcript.

lineage-boundary caveat · official schedule and repository titles · documented

The BSidesPDX 2018 schedule also lists The Making of the Banglet, and PDX Badgers has a separate Apache-2.0 `2018-banglet` repository for a DEFCON 26 / DC503 VIP wrist badge.

This record covers the BSidesPDX 2018 conference badge archive in `badge-2018`; the DC503 Banglet is modeled separately as its own DEF CON-adjacent party-badge lineage record.

Source note: BSidesPDX 2018 schedule, pdxbadgers/badge-2018, and pdxbadgers/2018-banglet.