` first; AI Slop Meter renders them with your Chrome or Edge, so the score is about what you actually see. They also get the `client-shell` finding: search engines see the same empty page unless you prerender. **2. The project folder.** Findings come with `file:line` in your source code. This is what your AI edits. ```bash cd my-app npx -y aislopmeter . --plan ``` **3. The built site.** For static sites, scan the files you will actually deploy. ```bash npm run build npx -y aislopmeter ./dist --open ``` **With your AI:** > My app is running at localhost:3000 and the code is in this folder. Scan both for AI slop, fix it in the code, and re-scan localhost after each step. Online checkers cannot reach `localhost`; this one can, because it runs on your machine. Nothing is uploaded. ## In the browser (bookmarklet) Scan the page you are looking at, with nothing installed. Create a bookmark and paste this as its address: ```text javascript:(()=>{const s=document.createElement('script');s.src='https://cdn.jsdelivr.net/npm/aislopmeter@0/dist/aislopmeter.browser.js';s.onload=()=>AISlopMeter.overlay();document.head.appendChild(s)})() ``` Click it on any page: a panel shows the score, the top findings and a copy-for-your-AI button for each. It checks one page at a time; for a whole site and `file:line`, use the CLI or MCP. Some sites block outside scripts (Content-Security-Policy); there the bookmarklet cannot run. ## Command line ```bash npx -y aislopmeter https://example.com # whole site, up to 30 pages npx -y aislopmeter https://example.com --pages all # up to 200 pages npx -y aislopmeter https://example.com --pages 1 # only this page npx -y aislopmeter ./my-app --plan --lang tr # project folder, plus the rescue plan in Turkish npx -y aislopmeter ./my-app --open # write the visual report and open it npx -y aislopmeter ./my-app --render never # HTML and CSS only, no browser npx -y aislopmeter ./my-app --json # raw result ``` Reports are written to `~/.aislopmeter/reports/` (`AISLOPMETER_REPORT_DIR` changes that). **Browser use.** With `--render auto` (the default) and Chrome, Edge or Chromium installed, pages are also measured in the browser through `playwright-core`, which downloads nothing. Set `AISLOPMETER_CHROME` to a browser path if it is not found, or `AISLOPMETER_BROWSER=off` to never start one. Folder scans skip `node_modules`, hidden folders and the primitives in `components/ui`. At the top of the scanned folder they also skip `dist`, `build`, `out`, `test`, `docs`, `examples` and repo documents such as README and CHANGELOG. Point AI Slop Meter at one of these directly to scan it, or use `--ignore path1,path2` to leave out more. ## Badge and GitHub Action Show your score in your README: ```bash npx -y aislopmeter . --badge aislopmeter.svg ``` ```markdown ![AI slop](aislopmeter.svg) ``` Check every pull request, with the report in the job summary: ```yaml - uses: actions/checkout@v4 - uses: omergocmen/aislopmeter@v0 with: target: . # or a preview URL fail-above: 40 # optional lang: en ``` The action also returns `score` and `band` as outputs. On the command line, `--fail-above 40` exits with code 1 above the limit. ## Configuration Put a `.aislopmeter.json` in your project (or the folder you run it from) to switch off a check that is wrong for you, or to set defaults: ```json { "disable": ["purple-gradient"], "keep": "The purple of our logo and the hero photo", "ignore": ["legacy"], "lang": "en", "pages": 30, "failAbove": 40 } ``` `disable` takes check ids from the report. `keep` is passed to the rescue plan as "do not touch". The report says which checks were turned off. `--no-config` ignores the file. ## How the score works Each finding adds points, and each category has a cap: | Category | Max | |---|---| | Substance | 30 | | Language | 22 | | Design | 28 | | Unfinished details | 15 | | Builder traces | 5 | Signs that a real business or person stands behind the page lower the score: a real address, named people, prices, legal details, links to independent reviews. A high score needs problems in several areas: with only one area the score is capped at 35, with two at 60. A purple brand colour alone is never heavy slop. For sites, the score is half the average page (home page counted twice, legal and sign-in pages left out) and half the worst page. | Score | Band | |---|---| | 0–19 | clean | | 20–39 | trace amounts | | 40–59 | noticeable | | 60–79 | heavy | | 80–100 | pure slop | Why rules and not an AI judge? In the largest study so far, LLMs asked "is this slop?" agreed with human editors at κ ≈ 0. Density and relevance predicted the human verdict best. So AI Slop Meter measures with explainable rules and uses your AI only to fix things ([details](docs/CRITERIA.md)). ## What it is not - **Not an AI-authorship detector.** A page made entirely with AI can score clean, and a hand-written page can score high. - **Not a ranking oracle.** The checks follow Google's helpful-content and spam guidance, but the score is not a search ranking. - **The Turkish lists are young.** They come from Turkish sources and known English tells; calibration help is welcome. - **Calibrated on 34 real sites so far.** Pages built with AI tools scored a median of 25, hand-made pages about 12, and no hand-made page reached 20 ([how and which sites](docs/CALIBRATION.md)). ## Privacy Everything runs locally. - **URL scans:** only pages of the site you point it at, following `robots.txt`, up to the page limit. - **Folder scans:** files are only read, never changed. - **Reports:** written only to your own computer, in `~/.aislopmeter/reports/`. - **No telemetry.** Your AI client sees the report text, as it does with any tool output. ## Contributing See [CONTRIBUTING.md](CONTRIBUTING.md): how to add a check, how calibration works, and how to report a wrong score. False alarms on real hand-made sites and Turkish word lists help the most. ## License MIT