SlopScore
00 crowd

tasker

Tasker is a production-minded project and task management system for focused execution.
Open repo on GitHubgithub.com/OsamaAlmaani/tasker
TypeScript · ★ 18 · 0 forks · Unlicense · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other
listed 59 minutes ago by OsamaAlmaani · last checked 59 minutes ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-09-29: Tasker is a production-minded project and task management system for focused execution.; its own README says "Built With Codex 🤫 This project was built end-to-end by GPT-5". 18 stars; Unlicense license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as OsamaAlmaani. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
Tasker is a production-minded project and task management system for focused execution.
created
2026-03-01 · pushed 12 hours ago · 68 commits · 1 contributor
languages
TypeScript 87%CSS 12%JavaScript 1%
paperwork
licensereadme 42% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 59 minutes ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
cssjavascripttypescript
license (detected)
unlicense

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: Tasker is a production-minded project and task management system for focused execution.; its own README says "Built With Codex 🤫 This project was built end-to-end by GPT-5". It carries the Unlicense license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

Tasker

Tasker is a production-minded project and task management system for focused execution.

Built With Codex 🤫

This project was built end-to-end by GPT-5.3-Codex, covering architecture, backend modeling, authorization, frontend implementation, and iterative product refinement.

Product Overview

  • Project-based workspaces with scoped membership and permissions.
  • Four task views: structured list, drag-and-drop Kanban by status, a month/week calendar with compact overflow, and a Gantt timeline with a resizable task grid, day/week/month scales, Today/Fit controls, and status/progress bars. Both scheduling views support start/due dates, inclusive ranges, drag-to-reschedule, and resizing from either edge, including single-date tasks.
  • Fast task operations: status, priority, assignee, start date, due date, labels, and search/filtering.
  • Parent tasks with one-level sub-task support, progress rollups, and nested list/Kanban presentation.
  • Unified task timeline combining comments and system activity in chronological order.
  • In-app inbox plus assignment email notifications.
  • Admin controls for user role management and account activation state.

Key Capabilities

  • Real-time synced data layer for projects, tasks, comments, members, and activity.
  • Role-based access with strict server-side authorization checks.
  • Project-specific task numbering and soft-delete behavior.
  • Member management with invite, revoke, and add-existing-user flows.
  • Persistent project view preferences and filters in URL state.
  • Async notification email delivery through Convex actions and SMTP env config.

Roles and Access Model

  • admin

  • Full system access across all projects and users.

  • member

  • Write access to projects they created or were added to.

  • viewer

  • Read-only access to projects they were added to.

All read/write enforcement happens on the server in Convex permission helpers.

Data Model

Core tables in /convex/schema.ts:

  • users
  • projects
  • projectMembers
  • projectInvites
  • projectCounters
  • issues
  • comments
  • activities

Architecture Notes

  • Auth is Clerk-based, with Convex identity mapped to internal users records.
  • User bootstrap/sync is handled through users.ensureCurrentUser.
  • Invite acceptance is auto-processed when a signed-in user email matches pending invites.
  • Project activity and task activity are recorded for audit-friendly history.

Repository Structure

  • /src/routes - all route screens and page-level logic.
  • /src/features/tasker - domain UI, auth guards, and shared feature modules.
  • /src/components/ui - shared design system primitives and dialogs.
  • /convex - schema, queries, mutations, actions, and auth/permission helpers.

Scripts

pnpm dev
pnpm build
pnpm check
pnpm test

License

This project is licensed under the Unlicense. See /LICENSE.

Local Setup (Required)

Use Node.js 25.x and pnpm 11.x. Deployment uses nixpacks.toml with pnpm 11 and a frozen lockfile.

  1. Install dependencies.
pnpm install
  1. Configure client env vars in .env.local.
CONVEX_DEPLOYMENT=...
VITE_CONVEX_URL=...
VITE_CLERK_PUBLISHABLE_KEY=...
VITE_CONVEX_SITE_URL=...
VITE_CLERK_JWT_TEMPLATE=convex
  1. Configure Clerk authentication prerequisites.
  • Create a Clerk JWT template named convex (used by Convex auth).
  • Enable email sign-in in Clerk, because project invite delivery and acceptance rely on email identity.
  1. Configure Convex server env vars (required for invite actions and SMTP notifications).
pnpm dlx convex env set CLERK_SECRET_KEY sk_...
pnpm dlx convex env set APP_BASE_URL https://tasker.yourcompany.com
pnpm dlx convex env set SMTP_HOST smtp.sendgrid.net
pnpm dlx convex env set SMTP_PORT 587
pnpm dlx convex env set SMTP_SECURE false
pnpm dlx convex env set SMTP_USER apikey
pnpm dlx convex env set SMTP_PASS your-sendgrid-smtp-password
pnpm dlx convex env set SMTP_FROM_EMAIL tasker@yourcompany.com
pnpm dlx convex env set SMTP_FROM_NAME Tasker

Notes:

  • APP_BASE_URL must be the public app origin used in email links and invite redirects, for example https://tasker.yourcompany.com.
  • SMTP_HOST, SMTP_PORT, SMTP_SECURE, SMTP_USER, and SMTP_PASS are server-side SMTP transport settings for assignment notification emails.
  • SMTP_USER is typically apikey for SendGrid SMTP.
  • SMTP_PASS should be your SendGrid SMTP password / API key value.
  • SMTP_FROM_EMAIL and SMTP_FROM_NAME control the visible sender on assignment emails.
  • These values stay in Convex server env only. Do not put them in .env.local.

Optional:

pnpm dlx convex env set CLERK_API_URL https://api.clerk.com/v1
  1. Verify Convex auth provider values for your Clerk instance in /convex/auth.config.ts.
  • domain and issuer must match your Clerk account domain.
  • applicationID should match the JWT template/application id (convex in this setup).
  • SMTP notification delivery is configured only through Convex server env vars; no SMTP settings are exposed in the app UI.
  1. Start development services.
pnpm dlx convex dev
pnpm dev
  1. Open http://localhost:3000, sign in, and optionally seed demo data from /settings.

Read the rest on GitHub

Scan report · 2026-09-29
  • ✓ Prohibited terms or links
  • ✓ Repository eligibility
  • ✓ slopscore.md paperwork
  • ✓ Content policy
  • ✓ Risk review

0 comments

log in to comment.

report this listing — log in to report