Clear filters

18 of 154 bounties. Choose something you enjoy; check its prerequisites before claiming.

18open
18unassigned
2900points up for grabs
XS · 25 S · 50 M · 100 L · 200 XL · 400

community-portal (1)

M · 100 pts community-portal

#230 · Connect staged library uploads to the host scan pipeline

New uploads enter publication only after a known scan outcome for the exact version.

BackendPythonPurple teamInfrastructurePrivacyDependency needed

event-service (1)

M · 100 pts event-service

#257 · Document and verify one existing resource access matrix

API and security developers can make existing access expectations explicit.

Testing / QAAPI / MCPSecurityPurple teamPrivacyReady to start

qa-form (1)

S · 50 pts qa-form

#271 · Offer a concise evidence-first answer starter

The answer form already has free text, source URLs and an optional confidence slider. Offer a small optional outline that helps a member separate an observed result, cited explanation, limitations and a useful next step.

FrontendDocumentationUXResearchPurple teamCommunity / knowledge sharingReady to start

scoreboard (12)

XL · 400 pts scoreboard

#102 · RCE / command injection in any service

Any path that lets an attacker execute arbitrary code or shell commands on a worker, container, or host. Highest priority class.

API / MCPSecurityTechPurple teamReady to start
XL · 400 pts scoreboard

#104 · Authentication bypass / session-token forgery

Any way to act as another user without their credentials, OR to elevate privileges to admin without admin-level OIDC claims.

API / MCPSecurityTechPurple teamReady to start
XL · 400 pts scoreboard

#105 · Webhook signature bypass / scoreboard double-award

The scoreboard accepts awards via two paths: (1) GitLab MR webhook, (2) the bot API. Both rely on shared secrets / API keys. Any way to mint awards without the secret, or to bypass the unique idempotency index, qualifies.

API / MCPSecurityTechPurple teamReady to start
L · 200 pts scoreboard

#103 · SQL injection in any D1 / PostgreSQL query

Any query that interpolates user input as a string instead of using a parameterized placeholder. D1 must use `.bind()`; PostgreSQL on signal-bot must use parameterized clients.

API / MCPSecurityTechPurple teamReady to start
L · 200 pts scoreboard

#108 · SSRF (server-side request forgery) in any worker

Any worker endpoint that fetches a URL the client controls. The new `/contribute/claim` was designed defensively (no fetch of user URL) but other paths may not be.

API / MCPSecurityTechPurple teamReady to start
L · 200 pts scoreboard

#110 · IDOR / privilege escalation via predictable IDs

Any endpoint that returns or mutates data keyed on a user-supplied ID without verifying the requesting user owns that ID.

API / MCPSecurityTechPurple teamReady to start
M · 100 pts scoreboard

#107 · Cross-site scripting (XSS) in any rendered template

Any user-provided string rendered into HTML without `escapeHtml`, or any `innerHTML` / `dangerouslySetInnerHTML` with attacker-controlled content.

API / MCPSecurityTechPurple teamReady to start
M · 100 pts scoreboard

#109 · CSRF on any state-changing endpoint

Any POST endpoint that modifies state without checking session origin. Workers don't get CSRF protection by default; if the auth is just a session cookie + the endpoint has no Origin/Referer check or CSRF token, it's exploitable.

API / MCPSecurityTechPurple teamReady to start
M · 100 pts scoreboard

#111 · Idempotency abuse to double-award points

The award system relies on a unique index on `(source_service, source_id)`. Any way to bypass it qualifies.

API / MCPSecurityTechPurple teamReady to start
M · 100 pts scoreboard

#113 · Auto-disclose patched security findings after 30-day embargo

**Disclosure policy decision needed.** Scope an explicit maintainer-reviewed disclosure workflow for fixed findings. Elapsed time alone must not publish unresolved findings, private reports, credentials or member details. Follow the current DEVSECOPS disclosure standard; do not a…

API / MCPSecurityPurple teamPrivacyDecision needed
M · 100 pts scoreboard

#114 · Signal bot `!reportbug` command — DM intake for security findings

**Requalification needed:** a generic `!report-bug` / `!reportbug` intake already exists in current Signal code. Inventory the existing path and define the remaining security-specific private handling before adding code. Do not duplicate the command, expose sensitive reports in a…

API / MCPSecurityPurple teamCommunity / knowledge sharingDecision needed
S · 50 pts scoreboard

#256 · Build positive and negative controls for shared URL policy

Security-minded contributors can improve confidence in an existing shared boundary.

Testing / QASecurityTechPurple teamReady to start

task-exchange (2)

S · 50 pts task-exchange

#275 · Add manual task starters for research, writing and verification work

The task form offers a generic Checklist insertion and AI enhancement. Add deterministic opt-in starters for a source-check, a wiki correction and a synthetic lab verification task so non-coding contributions are scoped as clearly as code.

FrontendDocumentationUXResearchPurple teamCommunity / knowledge sharingReady to start
S · 50 pts task-exchange

#278 · Give task reviewers a practical source-quality review aid

Detailed reviews currently offer numeric quality/accuracy/communication/timeliness ratings and free-text feedback. Add concise reviewer guidance for knowledge work so acceptance means traceable sources and reproducible evidence, not plausible prose.

FrontendDocumentationUXResearchWarfare studiesPurple teamProfessional developmentReady to start

wiki (1)

L · 200 pts wiki

#72 · Wiki page: SOC Tooling Overview

SOC Tooling Overview: create or improve a practical, source-checked guide for the community.

DocumentationSecurityResearchPurple teamReady to start

How to claim a bounty

First time? Get set up

  1. Sign in to git.juntogroups.org with your IrregularChat SSO.
  2. Create a Personal Access Token (PAT) at Settings → Access Tokens with the write_repository scope. You'll use it as your password when cloning/pushing over HTTPS.
  3. Clone the repo: git clone https://git.juntogroups.org/irregulars/irregularchat-monorepo.git
  4. On your Scoreboard profile, set your GitLab username so merges auto-credit you, and link your Signal account (+50 pts on first link).

Claim a bounty

Use the Development board: Ready → In progress → In review → Closed. Move the issue as work advances; assignment also marks it in progress here.

  1. Pick an unclaimed issue and comment /assign me on GitLab.
  2. Branch off main, implement the feature against the acceptance criteria.
  3. Test it locally before opening the MR: after rebasing on main, run cp .dev.vars.example .dev.vars && pnpm dev from the app dir (→ localhost:8787) and verify against the acceptance criteria. SSO login works with no secret — full walkthrough: Local Development & SSO.
  4. Open a merge request with Closes #<iid> in the description.
  5. On merge to main, GitLab closes the referenced issue and the webhook awards points to the matched MR author. A merge that only mentions an issue does not complete its bounty. Check the Completed tab and bounty activity; use Missed award if credit needs review.

The card shows the bounty tier · merge_pr (+40) is awarded on top. Additional bonuses stack automatically:

  • +10 wiki_edit if the MR touches apps/wiki/src/content/docs/**
  • +50 first_contribution on your first ever merged PR (one-time)

Points land when your GitLab username (set on your profile) or commit email matches your Scoreboard account. For the full walkthrough see the Contributing guide, or recover a missed award at /contribute/claim.

↑ Top