Issue dossier

The repository root publishes a BSD 2-Clause license credited to DavgaBeelog, while Beelog's current public site reserves its own rights. The reviewed archive and event pages do not pair a selected factual physical badge photo or upstream render with a complete source URL, image-specific reuse basis, attribution, and processing provenance. The BSD source/binary statement is not assumed to licence all photographs, renders, artwork, brands, or physical artifacts.

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

Back to issues index

source-license, media-rights, and branding scope boundary · repository license and public-site review · BSD source/binary license recorded; selected-image rights unresolved

The catalogue links the source archive and license but publishes no local badge image until an image-specific rights-cleared source is available.

Badge
MNSEC 2025 Electronic Badge Collection
Category
source-license, media-rights, and branding scope boundary
Severity
note
Confidence
repository license and public-site review
Status
BSD source/binary license recorded; selected-image rights unresolved
Timeframe
current catalogue build
Source note
MNSEC2025BADGE LICENSE, repository media tree, Beelog site, and badge.gallery image policy.

Evidence

Related Resources

manufacturer project record

Beelog MNCERT CC Electronic Badge Project

Beelog's official project page states that it designed, manufactured, and developed 418 electronic badges for MNCERT CC as a custom order, including hardware, firmware, and deployment-ready work. The page does not identify individual recipients, per-unit configuration, ticket entitlement, or image-reuse permission.

Badge: MNSEC 2025 Electronic Badge Collection

public badge source archive

MNSEC2025BADGE public source archive

The public repository identifies the MNSEC 2025 electronic-badge commission, says three badge types and 418 completed units, names MNCERT/CC and Beelog Tech, and links hardware, firmware, and supporting material. It is a project archive, not a recipient ledger or blanket licence for all media.

Badge: MNSEC 2025 Electronic Badge Collection

public firmware and example-code archive

MNSEC2025BADGE firmware directory

The public directory contains a firmware binary, a named sketch, and example source folders. It does not establish a reconciled final release, source-to-unit mapping, support lifecycle, or safe operating/reconfiguration instructions.

Badge: MNSEC 2025 Electronic Badge Collection

Source trail

Evidence Sources

Beelog Technologies · retrieved 2026-05-15

MNCERT CC Electronic Badge Project

Primary manufacturer project record stating that Beelog designed, manufactured, and developed 418 electronic badges for MNCERT CC as a custom order. It does not map those units to named event recipients or selected source-media rights.

Badge: MNSEC 2025 Electronic Badge Collection

DavgaBeelog / MNSEC2025BADGE · retrieved 2026-05-15

BSD 2-Clause License

Primary repository license text. It is scoped as the archive's BSD 2-Clause source/binary statement and is not treated as automatic permission for photographs, renders, badges, branding, or a locally published image.

Badge: MNSEC 2025 Electronic Badge Collection

helicopteresdc / Beelog Tech · retrieved 2026-05-15

MNSEC2025BADGE

Primary public badge archive identifying the MNSEC 2025 commission, MNCERT/CC customer context, Beelog Tech role, three badge types, and 418 completed units. Its design archive is not treated as proof of every final delivered configuration.

Badge: MNSEC 2025 Electronic Badge Collection

helicopteresdc / Beelog Tech · retrieved 2026-05-15

MNSEC2025BADGE Firmware

Primary public source for the preserved firmware binary, named sketch, and examples. It does not establish a complete released software inventory, operational configuration, or support policy.

Badge: MNSEC 2025 Electronic Badge Collection