[PAID BOUNTY - $960] Attachment Summarizer Service

[warpspeedopen-source]

Bounty Overview

Build a Node.js attachment summarizer service that consumes email attachment events from AWS SQS, downloads attachments from Google Cloud Storage, extracts content from supported file types, and generates natural-language summaries using a self-hosted open-source LLM.

This bounty is part of the warpSpeed OPEN developer bounty programme.

Reward

$960

Difficulty

Expert

Main Skills

• Node.js
• TypeScript
• Prisma
• AWS SQS
• Google Cloud Storage
• Docker
• Ollama / Open-source LLMs

High-Level Scope

The selected developer will build a service that:

• Consumes attachment events from SQS
• Downloads attachments from GCS
• Handles common attachment types such as PDFs, Word documents, spreadsheets, text files, HTML, and images
• Generates short factual summaries using a locally hosted LLM
• Includes error handling, logging, Docker setup, and tests

Full technical requirements, submission rules, and acceptance criteria are available on the official bounty page.

View Full Bounty Details & Sign Up

To see the full bounty specification and apply, visit:

https://warpspeedopen.org/bounties

How to Claim

1. Open the bounty page.
2. Sign up as a developer.
3. Review the full bounty details and rules.
4. Return to this GitHub issue and comment:

“I have signed up and would like to claim this bounty.”

A maintainer must confirm before work begins.

Important Rules

• Do not start work until a maintainer confirms your claim.
• Maximum 3 submission attempts.
• Payment is made only after the pull request is approved and merged.
• Code must be original or properly licensed.
• The full bounty page is the source of truth for technical requirements and deadlines.

[acdunbrack]

I have signed up and would like to claim this bounty.

[MyTH-zyxeon]

Hi warpSpeed OPEN team — I’ve read the rules here and on the bounty overview.

Before I sign up on https://warpspeedopen.org/bounties and post the exact claim phrase (“I have signed up and would like to claim this bounty.”), could you confirm a couple of implementation details so I don’t start in the wrong direction?

1. Runtime + hosting expectation: should this service be deployed as a standalone container (e.g. ECS/Cloud Run/K8s) that polls SQS, or is there an existing warpSpeed runtime/conventions it must plug into?
2. GCS auth: should the service assume a single service account for GCS downloads (JSON key / Workload Identity), and is the bucket+path encoded in the SQS message?
3. Event schema: can you point to (or paste) the exact SQS message JSON schema for “email attachment events” (fields like bucket, objectKey, mimeType, messageId, tenant, etc.)?
4. LLM contract: should summaries be produced via Ollama’s HTTP API (local), and do you want a strict JSON output schema (e.g. {title, bullets, pii_redactions}) or plain text?
5. File types: for images, is OCR required (e.g. Tesseract) or only caption-style summaries?

If you confirm the above, I’ll sign up + claim immediately, then implement with:

• SQS consumer with idempotency + DLQ handling
• GCS downloader with streaming to local temp + size limits
• Extractors per file type (PDF/docx/xlsx/txt/html/images)
• Summarization prompt + unit tests (golden samples)
• Dockerfile + minimal ops docs

Thanks — happy to align the scope tightly to the official bounty page requirements.

[apoorva-01]

I have signed up and would like to claim this bounty.

[nguyenthekr92-byte]

I have signed up and would like to claim this bounty.

[acdunbrack]

I have signed up and would like to claim this bounty.

[ItsOtherMauridian]

I have signed up and would like to claim this bounty.