GitHub Bounties💵 paid workby tristanworkscored by google/gemini-2.5-flash

SecureBananaLabs/bug-bounty: @freelanceflow/db package should expose an importable workspace entrypoint

Visit project ↗Discussion ↗

💵 Funded work— see “Deliver it” below for how to respond.

Opportunity

AI-buildable

Traction

Creativity

The take

effort: ~weekend

This is a bounty to fix a package entrypoint issue in a TypeScript monorepo. The `@freelanceflow/db` package needs its `package.json` configured correctly with `main`, `types`, and `exports` fields to be importable within its workspace. A lightweight test is also required to prove the fix.

Demand & gap

Painkillerdemand 79

Demand

Will. to pay

Gap

Buyer

Developers

The gap in what exists: The gap is for a developer willing to execute a specific, well-defined technical task for a direct payment, filling a need for immediate code delivery.
Wedge to win: The wedge is to deliver a precise, high-quality solution quickly for a defined bounty, demonstrating technical competence for future contract work.
Reputation value (worth doing free for proof) — 75/100: Successfully completing a GitHub bounty on a public repository is a concrete, verifiable proof-of-work that can be showcased for future freelance or contract opportunities.
Likely monetization: bounty (one-off payment)

Deliver it

A starter prompt for Claude Code, what you'll need, and how to reach them.

You are an expert TypeScript developer. The task is to fix a package entrypoint issue for the `@freelanceflow/db` package within the `SecureBananaLabs/bug-bounty` monorepo (specifically issue #2775). Fork the repository. Navigate to `packages/db`. Edit `package.json` to include `main`, `types`, and `exports` fields, ensuring they point to the correct build outputs (e.g., `dist/index.js`, `dist/index.d.ts`). Assume `src/index.ts` is the source file. If a build script is missing to compile `src/index.ts` to `dist/`, create a simple `tsc` command or similar in the `package.json`'s `scripts` section. Finally, add a lightweight test (e.g., a new `test.ts` file that attempts to import `@freelanceflow/db`) to confirm the package is correctly exposed and importable within the monorepo workspace. The build/verify gate is a passing test and a properly configured `package.json` that allows other workspace packages to import `@freelanceflow/db` without errors. Focus solely on the `db` package and its entrypoint. The target environment is Node.js within a TypeScript monorepo.

Prerequisites — cost & what to learn

GitHub accountFree · Free

How you'd build it

1Fork the `SecureBananaLabs/bug-bounty` repository.
2Locate the `packages/db/package.json` file.
3Add `main`, `types`, and `exports` fields to `package.json`, pointing to `dist/index.js` and `dist/index.d.ts` (assuming a build step that compiles `src/index.ts`).
4Implement a minimal build script (e.g., using `tsc`) if not already present, to compile `src/index.ts` to `dist/index.js` and `dist/index.d.ts`.
5Create a simple test file within the package or a new test package in the monorepo that imports `@freelanceflow/db` and asserts successful import.
6Open a pull request to the original repository with the fix and test.

Risks & moats

Understanding the existing monorepo build setup and its implications for package resolution.
Ensuring the fix is compatible with the intended consumption pattern (workspace vs. external npm install).
Potential for other unforeseen package resolution issues within a complex monorepo.
The bounty issuer might have specific conventions or tooling that need to be followed.

Market it to your portfolio

fit 40

Forge KitMCP Kit

For developers interested in monorepo best practices and automated build processes, this bounty demonstrates practical skills in package management, which is relevant to users of Forge Kit and MCP Kit.

Original context

Bounty (amount on the issue). Parent bounty: #743 ## Bug The `packages/db` workspace contains `src/index.ts`, but `packages/db/package.json` does not declare `main`, `types`, or `exports`. Consumers importing `@freelanceflow/db` from the workspace have no reliable package entrypoint, so Node package resolution looks for a missing root `index.js`. ## Expected - `@freelanceflow/db` exposes a valid JavaScript entrypoint for workspace consumers. - Package metadata includes explicit `main`, `types`, and `exports` fields. - A lightweight test proves the package can be imported through the workspace package name. ## Scope Keep the fix limited to the DB package entrypoint and a focused import test.