Contribute

The index is only as strong as its receipts.

NoThanks is a community evidence project. You can add a product, challenge a score with better sources, or help tighten the methodology. Everything is reviewed through a pull request.

Repository See the PR steps

Recommended first step

Start with the research CLI

Enter a product you own. The CLI fetches official pages, detects signals for the four dimensions, and writes a draft entity with receipts to data/intel/drafts/ for your review. 

npm run research -- "Product Name"
npm run research -- --name "Product Name" --url <product-url>
How research drafts become entities

Ways to help

Pick a path

Add an entity

Create a JSON record with identity, a four-dimension scorecard, and receipts that a reviewer can verify.

Challenge a receipt

Found a broken link, a misread policy, or a better primary source? Open a PR that replaces or removes the claim.

Improve the method

Propose clearer dimension definitions, better bands, or new validation checks for the pipeline.

Pull request steps

From finding to merged evidence

The full guide lives in CONTRIBUTING.md in the repository. The short version:

Local commands 

npm ci
npm run validate:data
npm run check:urls -- --all
npm run build
  1. 1

    Fork and branch

    Fork the repository and create a focused branch. One entity or one logical change per PR keeps review fast.

  2. 2

    Add or edit the JSON

    Create data/entities/<slug>.json or edit an existing file. Set the slug to match the filename in lowercase kebab-case.

  3. 3

    Attach receipts

    Give each claim a live source, an archive snapshot where possible, a date, and a short snippet. Prefer primary sources.

  4. 4

    Run local checks

    Run npm run validate:data, npm run check:urls, and npm run build. Fix anything the validator flags before opening the PR.

  5. 5

    Open the PR

    Describe what changed, cite the sources, and note the validation steps you ran. CI will re-run the checks.

Evidence standards

What makes a receipt acceptable

Receipts are claims with sources. A reviewer should be able to confirm or refute each one without inside access to the product.

Full evidence requirements

Pre-PR checklist

  • Slug is lowercase kebab-case and matches the filename.
  • All four dimensions are present with a score, summary, and receipts array.
  • Every receipt has a non-empty, specific claim.
  • Sources are http(s) URLs and, where possible, archived.
  • Summaries distinguish observation from inference.
  • All entries are real products with primary-source evidence. No mock or demo content.
  • Language is neutral: factual, no hyperbole or advocacy slogans.

Ready to add the next entry?

Fork the repository, drop a JSON file into data/entities/, and open a PR. CI will validate the schema, URLs, and build.

Open the repository Read the methodology