Thank you for helping keep TheTechStack accurate. Corrections are decided by evidence quality, not seniority or vendor preference.
- Edit the relevant
records/<company>.json. - Every change needs evidence: add or update the
evidencearray — URL, source type, a short quote, access date. PRs that change facts without sources will be asked for them. - Pick the honest confidence label:
confirmed— the company said it publicly (or you work there and say so in the PR — we'll verify)inferred— strong technical evidence (job post, repo, fingerprint)reported— credible third party
- If a tool was replaced, don't delete it — set
status: "previous"and add the replacement as a new entry withreplacedset. Migrations are data, not noise. - Run
npm install && npm run validatebefore opening the PR. - Company employees may describe their relationship in the PR, but should not post a private work email, employee ID, or other sensitive proof publicly.
If you do not want to edit JSON, use the stack correction issue form. A maintainer can turn an evidence-backed issue into a pull request.
Only a maintainer may change verified_by_company to true. Employment or company
authority can be verified privately when needed; verification evidence is not committed
to this repository.
The automated path from an approved public correction to the private site build is still being completed. A merged correction is accepted into the public record, but it should not be described as live on the site until a maintainer confirms the site update.