This repository has been archived on 2026-11-17. You can view files and clone it, but cannot push or open issues or pull requests.
caelum0x 487e43129f fix(gitgram): fix broken messaging (Account/User id mismatch) + chat IDOR + SEO gap
Audited gitgram-ai end to end by actually running the backend against a
live Postgres instance (not just reading/trusting the existing Jest
suite, which mocks Prisma and therefore never hits real FK constraints
or real route wiring).

Critical, feature-breaking bug: Message.senderId/receiverId and
MessageReaction.userId are foreign keys into Account, but every
messaging controller function wrote/read req.userId (a User id) into
those columns directly. Verified live: every message send (1:1 DM and
group chat) failed with a Prisma foreign-key-constraint violation, and
group messages additionally violated the (until now) required
non-null receiverId column since group messages have no single
receiver. Messaging has never worked through this code path. Fixed by
resolving the caller's Account id once per request (matching the
`prisma.account.findFirst({ where: { userId } })` pattern already used
elsewhere in the codebase, e.g. followRequestController) and using it
consistently for every Message/MessageReaction read, write, and
ownership check, while keeping ChatMember/UserBlock/socket rooms on the
real User id they were already consistent with. Added a Prisma
migration making Message.receiverId nullable for group-only messages.
Verified against a live Postgres test database: registered 3 users,
created a group chat, sent and read 1:1 and group messages, reacted,
and marked conversations read -- all succeed now.

Cross-tenant IDOR (same bug class found on Scribase today): GET
/api/v1/messages/chats/:chatId had no membership check at all -- any
authenticated user could read any group chat's messages by chatId
alone (every sibling function in the same file -- getMessage,
reportMessage, assertMessageAccess -- already enforced membership, this
one endpoint was the outlier). Also hardened sendMessage so posting
into a chatId you don't belong to is rejected. Verified live: a
non-member now gets 403 on both reads and writes to a chat they're not
in; an actual member still gets 200.

Unrelated build blocker found while standing up the backend to test
this: gitgram/backend/tsconfig.json set `ignoreDeprecations: "6.0"`,
which the pinned typescript@^5.9.3 doesn't recognize -- `tsc`/`ts-node`
hard-error with TS5103 before compiling a single file. Backend could
not build or boot in dev mode at all. Fixed to "5.0".

SEO gap: gitgram/web (Next.js 14 app dir) had no robots.txt and no
sitemap anywhere, static or dynamic -- zero crawl directives, no
sitemap reference for search engines. Added app/robots.ts (disallows
authenticated-only surfaces, allows public ones) and app/sitemap.ts
(static public marketing/discovery routes).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-24 22:20:32 +03:00
..

Gitgram Web

Web version of Gitgram built with Next.js 14, TypeScript, and Tailwind CSS.

Getting Started

  1. Install dependencies:
npm install
  1. Set up environment variables:
cp .env.example .env
  1. Run the development server:
npm run dev
  1. Open http://localhost:3000 in your browser.

Features

  • Next.js 14 App Router
  • TypeScript
  • Tailwind CSS for styling
  • GitHub-inspired UI
  • Shared API client with mobile app
  • Authentication with JWT
  • Server-side rendering (SSR)
  • Static site generation (SSG)

Project Structure

web/
├── app/              # Next.js App Router pages
├── components/       # React components
├── services/         # API services
├── store/            # State management (Zustand)
└── lib/              # Utilities

Talent Graph proof route

/talent-network presents one API-backed route:

  1. Institution need from GET /v1/talent-graph/opportunities
  2. Evidence matches from GET /v1/talent-graph/opportunities/:id/matches
  3. Candidate-controlled Zen referral from GET /v1/talent-graph/referrals/mine
  4. Pilot delivery and audit history from GET /v1/talent-graph/pilots/mine
  5. Eligible public proof in the owner /collaborate dossier

Public pilot evidence requires a COMPLETED pilot, participant consent, and a public HTTP(S) deliverable. The client does not seed records. A zero count comes from the API; the screen renders request failures as an unavailable state with a retry action.

All Talent Graph writes now carry a retry-stable Idempotency-Key. Referral and pilot updates also send the revision read from the API, so concurrent decisions or edits fail with 409 instead of overwriting one another. Public profile and matching reads consume the dedicated TalentPublicProof projection rather than joining private opportunity/pilot records at request time. See the backend release runbook.

The owner dossier creates /collaborate?profile=<username> only when the account has a public username. Browser validation still needs two accounts for referral acceptance and institution completion, forced API failures for each resource, responsive anchor review, and public-link checks. The current hackathon cycle forbids build, test, lint, CI, migrations, and app-server runs.