Community Bounties
Submit a merge request that closes one of these issues to earn points on merge — bounties stack on the standard +40 merge_pr award. New to the repo? See the Contributing guide or the step-by-step below.
Open includes work in progress and tasks waiting on prerequisites. App counts show the matching issues, not just work available to claim. Ready to start · In progress · In review.
Some bounties are visible to members only — sign in to see them.
Last checked with GitLab: . Status comes from GitLab using a 5-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.
15 of 154 bounties. Choose something you enjoy; check its prerequisites before claiming.
event-service (1)
#257 · Document and verify one existing resource access matrix
API and security developers can make existing access expectations explicit.
qa-form (1)
#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.
scoreboard (10)
#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.
#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.
#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.
#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.
#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.
#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.
#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.
#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.
#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.
#256 · Build positive and negative controls for shared URL policy
Security-minded contributors can improve confidence in an existing shared boundary.
task-exchange (2)
#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.
#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.
wiki (1)
#72 · Wiki page: SOC Tooling Overview
SOC Tooling Overview: create or improve a practical, source-checked guide for the community.
How to claim a bounty
First time? Get set up
- Sign in to git.juntogroups.org with your IrregularChat SSO.
- Create a Personal Access Token (PAT) at Settings → Access Tokens with the
write_repositoryscope. You'll use it as your password when cloning/pushing over HTTPS. - Clone the repo:
git clone https://git.juntogroups.org/irregulars/irregularchat-monorepo.git - 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.
- Pick an unclaimed issue and comment
/assign meon GitLab. - Branch off
main, implement the feature against the acceptance criteria. - Test it locally before opening the MR: after rebasing on
main, runcp .dev.vars.example .dev.vars && pnpm devfrom the app dir (→localhost:8787) and verify against the acceptance criteria. SSO login works with no secret — full walkthrough: Local Development & SSO. - Open a merge request with Closes #<iid> in the description.
- 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_editif the MR touchesapps/wiki/src/content/docs/**+50 first_contributionon 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.