		{
		"name": "llmscout-cli",
		"version": "0.3.0",
		"version": "0.3.4",
		"description": "Zero-dependency, cross-platform LLM/GEO/AEO checker CLI — 21 technical-SEO and generative-engine-optimization checks, no headless browser, no Python interpreter required.",
		@@ -35,2 +35,5 @@ "keywords": [
		"author": "Rudrendu Paul",
		"contributors": [
		"Sourav Nandy"
		],
		"type": "module",
		@@ -51,3 +54,3 @@ "bin": {
		"scripts": {
		"build": "tsc -p tsconfig.json",
		"build": "tsc -p tsconfig.json && chmod +x dist/cli.js",
		"typecheck": "tsc --noEmit",
		@@ -54,0 +57,0 @@ "test": "vitest run",

+2

-2

README.md

		@@ -346,3 +346,3 @@ <div align="center">

		It exists to replace the install flow of an existing project, [`AgriciDaniel/claude-seo`](https://github.com/AgriciDaniel/claude-seo), for one specific class of problem. That project is a Claude Code SEO/GEO skill that carries out its checks by shelling out to Python scripts (Playwright-based rendering, `pip`-installed dependencies) from skill instructions. That external-toolchain-plus-path-resolution chain is the root cause behind a recurring pattern of install/Windows/path bugs filed against it, including three still-open issues: [#137](https://github.com/AgriciDaniel/claude-seo/issues/137) (a fresh `/plugin` install provisions neither the Python dependencies nor Playwright Chromium), [#138](https://github.com/AgriciDaniel/claude-seo/issues/138) (skill instructions hardcode `python3`, which does not exist on a stock Windows install), and [#139](https://github.com/AgriciDaniel/claude-seo/issues/139) (skills call `scripts/*.py` through a relative path that does not resolve when the scripts live under the plugin root). The same class of pain shows up independently in `zubair-trabzada/geo-seo-claude`, another actively used Claude Code GEO skill (issues [#69](https://github.com/zubair-trabzada/geo-seo-claude/issues/69), [#21](https://github.com/zubair-trabzada/geo-seo-claude/issues/21), [#3](https://github.com/zubair-trabzada/geo-seo-claude/pull/3)) -- the failure mode is architectural, not specific to one project.
		It exists to replace the install flow of an existing project, [`AgriciDaniel/claude-seo`](https://github.com/AgriciDaniel/claude-seo), for one specific class of problem. That project is a Claude Code SEO/GEO skill that carries out its checks by shelling out to Python scripts (Playwright-based rendering, `pip`-installed dependencies) from skill instructions. That external-toolchain-plus-path-resolution chain is the root cause behind a recurring pattern of install/Windows/path bugs filed against it, including three issues (since closed, but each documenting the architectural failure mode this project exists to avoid): [#137](https://github.com/AgriciDaniel/claude-seo/issues/137) (a fresh `/plugin` install provisions neither the Python dependencies nor Playwright Chromium), [#138](https://github.com/AgriciDaniel/claude-seo/issues/138) (skill instructions hardcode `python3`, which does not exist on a stock Windows install), and [#139](https://github.com/AgriciDaniel/claude-seo/issues/139) (skills call `scripts/*.py` through a relative path that does not resolve when the scripts live under the plugin root). The same class of pain shows up independently in `zubair-trabzada/geo-seo-claude`, another actively used Claude Code GEO skill (issues [#69](https://github.com/zubair-trabzada/geo-seo-claude/issues/69), [#21](https://github.com/zubair-trabzada/geo-seo-claude/issues/21), [#3](https://github.com/zubair-trabzada/geo-seo-claude/pull/3)) -- the failure mode is architectural, not specific to one project.

		@@ -353,3 +353,3 @@ LLMScout is not a fork of either project. It shares no code with them, has a different name, and reimplements the equivalent checks from scratch. The design choice that matters is what it does not do: because the checks run inside the host process rather than by launching an external interpreter and a headless browser, the entire failure class behind those bugs does not exist here. There is no interpreter to provision, no `pip install` to run beyond the package itself, no browser binary to download, and no relative script path to resolve, so a fresh install behaves the same on every platform. The direct cost of that choice is that the content-extraction check is a static-HTML heuristic and cannot evaluate content that only appears after client-side JavaScript renders. The check documents this limitation in its own output.

		LLMScout is at v0.3, freshly renamed from its original name, LLMScout. Both distributions are being republished under the new package name (`llmscout-cli` on both npm and PyPI) -- see [Install](#install) for both paths, and the badges above for live version status.
		LLMScout is at v0.3, freshly renamed from its original name, SeoFleet. Both distributions are being republished under the new package name (`llmscout-cli` on both npm and PyPI) -- see [Install](#install) for both paths, and the badges above for live version status.

		@@ -356,0 +356,0 @@ ## FAQ

llmscout-cli - npm Package Compare versions

Improved metrics