Repository navigation
Open
Labels
securityPull requests that address a security vulnerabilityPull requests that address a security vulnerabilitystatus: blockedWaits for the issues in its Blocked by sectionWaits for the issues in its Blocked by sectiontrack: operationsTests, CI, staging, security and launchTests, CI, staging, security and launchv3PromiseTracker v3PromiseTracker v3
Milestone
Description
Type: AFK. Can be built and merged without a decision.
Owner: kelvinkipruto. Order: 11 of 12 for this owner, after #655 and before #661. Track: operations. Build order: #672
Part of PromiseTracker v3, version 1. Specification: docs/spec/promisetracker-v3-system-specification.md. Section numbers below refer to it.
What to build
A full pass over security and privacy before launch, including the checks that only make sense
once every feature exists.
Start here
- Read first: all of section 13, and rule 5 in section 15 of the specification. Decisions D41 and D46.
- Code goes in: tests in
tests/intandtests/unit. Retention jobs inplugins/core/src. Security headers inapps/site/next.config.ts. - Already there: every feature issue is merged by now. Search the code for
overrideAccess: trueto build the list the last criterion asks for. - From v2:
tests/int/ssrf.int.spec.ts,fileSignature.int.spec.ts,requestGuards.int.spec.ts,securityHeaders.int.spec.ts,privilegedAccess.int.spec.ts,publicApiAccess.int.spec.tsandpublicRoutes.int.spec.ts. Read a v2 file withgit show v2-final:<path>. - Migration: No.
- How to work:
AGENTS.md, section "Working on an issue".
Acceptance criteria
- v2's security tests carry over and pass: SSRF, file signatures, request guards, security
headers, privileged access, public API access, public routes - A test asserts that no API response anywhere includes created-by, changed-by or version
fields - The browser security policy forbids framing everywhere
- Logs never contain keys, tokens, passwords, email addresses or network addresses, checked
by a test that scans log output - Payload's MCP plugin is enabled behind its built-in OAuth sign-in, limited to the user's
own permissions, and never reachable without signing in - Retention jobs from section 13.9: raw AI responses after 90 days, rejected submissions after
180 days, the search log after 12 months, failed jobs after 7 days - Every server-side call that bypasses access rules is listed and justified in this issue
- Analytics stays on the
noneadapter in version 1. Google Analytics is added after the
production launch (D41) - A test proves a guest receives no internal field anywhere: authorship, who verified a
claim, AI confidence, processing details and plugin fields (section 13.1, D46)
Blocked by
- V1-16: plugin-ai: candidate claims and review #654, owned by koechkevin
- V1-17: plugin-check: verification in Meedan Check #655, owned by kelvinkipruto
- V1-18: Search, place first #656, owned by koechkevin
- V1-19: Homepage, themes, articles and editorial picks #657, owned by koechkevin
- V1-20: Citizen submissions, captcha and newsletter #658, owned by koechkevin
- V1-21: Share images, structured data and discoverability #659, owned by koechkevin
- V1-28: API description, cache headers and transport tests #669, owned by koechkevin
Unblocks
- V1-23: Launch readiness #661, owned by kelvinkipruto
Metadata
Metadata
Assignees
Labels
securityPull requests that address a security vulnerabilityPull requests that address a security vulnerabilitystatus: blockedWaits for the issues in its Blocked by sectionWaits for the issues in its Blocked by sectiontrack: operationsTests, CI, staging, security and launchTests, CI, staging, security and launchv3PromiseTracker v3PromiseTracker v3
Activity