2025-05-06 - 2026-05-06
Overview
2 Releases published by 1 user
Published
polymarket-browse/v0.0.3
Published
polymarket-browse/v0.0.2
7 Pull requests merged by 1 user
Merged
#28 Fix: Event happening exactly now shows LIVE instead of In 0m
Merged
#26 Add parallel fetching, caching, and max_total parameter
Merged
#24 Fix line lengths in browse.py
Merged
#23 Add type hints to browse.py
Merged
#22 Fix #14: Refactor print_browse/send_to_telegram into single pipeline
Merged
#20 Fix #5: HTML injection in Telegram messages
Merged
#19 Fix #4: Extract send() to module-level send_telegram_message() for testability
20 Issues closed from 1 user
Closed
#3 [SECURITY] polymarket-browse: Security Audit Tracking (2026-03-25)
Closed
#12 SKILL.md: Missing 1-indexed --detail argument clarification
Closed
#11 SKILL.md: Missing documentation (troubleshooting, examples, changelog, credits)
Closed
#8 [SECURITY] MEDIUM: No response size limits - potential memory exhaustion
Closed
#10 [SECURITY] LOW: No rate limiting on API calls
Closed
#6 [SECURITY] MEDIUM: Insufficient URL encoding on --search parameter
Closed
#7 [SECURITY] MEDIUM: --detail argument silently defaults when out of range
Closed
#9 [SECURITY] LOW: Bare except: clauses swallow security-relevant errors
Closed
#16 Timezone configuration issue
Closed
#25 [Analysis] API Efficiency Issues and Optimization Opportunities
Closed
#13 browse.py has long lines throughout (target max 120 chars)
Closed
#17 Create unit tests
Closed
#18 Add type hints to codebase
Closed
#27 [BUG] Event happening exactly now shows "In 0m" instead of "LIVE"
Closed
#14 browse.py print_browse() and send_to_telegram() too long
Closed
#15 browse.py has 3 duplicate time functions doing similar things
Closed
#5 [SECURITY] HIGH: HTML injection in Telegram messages
Closed
#4 [SECURITY] CRITICAL: Telegram bot token visible in process command line
Closed
#2 [SECURITY] HIGH: HTML injection in Telegram messages
Closed
#1 test
22 Issues created by 1 user
Opened
#1 test
Opened
#2 [SECURITY] HIGH: HTML injection in Telegram messages
Opened
#3 [SECURITY] polymarket-browse: Security Audit Tracking (2026-03-25)
Opened
#4 [SECURITY] CRITICAL: Telegram bot token visible in process command line
Opened
#5 [SECURITY] HIGH: HTML injection in Telegram messages
Opened
#6 [SECURITY] MEDIUM: Insufficient URL encoding on --search parameter
Opened
#7 [SECURITY] MEDIUM: --detail argument silently defaults when out of range
Opened
#8 [SECURITY] MEDIUM: No response size limits - potential memory exhaustion
Opened
#9 [SECURITY] LOW: Bare except: clauses swallow security-relevant errors
Opened
#10 [SECURITY] LOW: No rate limiting on API calls
Opened
#11 SKILL.md: Missing documentation (troubleshooting, examples, changelog, credits)
Opened
#12 SKILL.md: Missing 1-indexed --detail argument clarification
Opened
#13 browse.py has long lines throughout (target max 120 chars)
Opened
#14 browse.py print_browse() and send_to_telegram() too long
Opened
#15 browse.py has 3 duplicate time functions doing similar things
Opened
#16 Timezone configuration issue
Opened
#17 Create unit tests
Opened
#18 Add type hints to codebase
Opened
#25 [Analysis] API Efficiency Issues and Optimization Opportunities
Opened
#27 [BUG] Event happening exactly now shows "In 0m" instead of "LIVE"
Opened
#29 Add --starts-before filter for match events
Opened
#39 [Design Discussion] Redesign --detail to use event ID instead of list index