Grok Bot Austin GTM badge booth (Phomemo M110)

Austin GTM build-night case: guests or their Grok Bots claim badges that auto-print on a Phomemo M110 with procedural Grok Bot avatars.

View source ↗

Caution: review the findings below before installing.

CautionScan verdict · score 50/100
Coverage
full
Checks run
Rule-based pattern scan
Files checked
37
Findings
4
Scanned
2026-11-01

Badges are rule-based checks, not guarantees: Safe means our rules found no obvious threat in the code we could read. Review code before installing.

View source ↗
Botlens score · 8 factors
50/100

Each factor is 0, ½ or 1, computed only from catalog fields (scan result, coverage, findings, script files, commit/SHA, author, last seen, install link). A heuristic summary, not a guarantee.

Scan verdict0.5/1Caution
Code coverage1/1full
Rule findings0/17 matched
No executable scripts0/130 script file(s) of 37
Pinned source1/1commit/SHA-256 recorded
Named author0/1unknown
Recently seen1/1last seen 2026-10-30
Install path0.5/1source URL only

Scan details

Findings
  • reads environment variables (where API keys live) in app/api/claim/route.ts: "…akeExchange(badge); const pingUrl = process.env.BOOTH_PING_URL?.trim(); const pingS…"
  • uploads data to a remote server in app/api/claim/route.ts: "…if (pingUrl && pingSecret) { void fetch(pingUrl, { method: "POST", headers: { "Content…"
  • reads environment variables (where API keys live) in lib/auth.ts: "… (!token) return false; const admin = process.env.ADMIN_TOKEN?.trim() || boothToken(); …"
  • reads environment variables (where API keys live) in lib/config.ts: "…ction baseUrl(): string { const raw = process.env.NEXT_PUBLIC_BASE_URL?.trim() || "https:…"
Content SHA-256
f076bc6efbaaf4f7…
Commit
a8026b6fff
Files
.gitignore
README.md
next.config.ts
package-lock.json
package.json
postcss.config.mjs
+31

About

Author
mehh ↗
Listed on
github:RongleCat/awesome-grok-bot ↗
Category (approx.)
agentops
First seen
2026-10-30
Last seen
2026-10-30
URL
github.com ↗
Get the Botlens skill