slopsentry 0.1.0__tar.gz

slopsentry-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+.venv/
+__pycache__/
+*.py[cod]
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+dist/
+build/
+.DS_Store

slopsentry-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Rajeshr-developer
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

slopsentry-0.1.0/PKG-INFO

@@ -0,0 +1,235 @@
+Metadata-Version: 2.5
+Name: slopsentry
+Version: 0.1.0
+Summary: Check packages for slopsquatting before they are installed.
+Project-URL: Homepage, https://github.com/Rajeshr-developer/slopsentry
+Project-URL: Repository, https://github.com/Rajeshr-developer/slopsentry
+Project-URL: Issues, https://github.com/Rajeshr-developer/slopsentry/issues
+Author-email: Rajeshr-developer <rajeshr.developer@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: claude-code,pypi,security,slopsquatting,supply-chain,typosquatting
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Build Tools
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.27
+Requires-Dist: packaging>=24
+Requires-Dist: rich>=13
+Requires-Dist: typer>=0.12
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# SlopSentry
+
+SlopSentry checks packages for **slopsquatting** before you install them: AI-hallucinated
+package names and malicious lookalikes that attackers register to catch them.
+
+<!-- TODO: demo GIF of the Claude Code hook blocking a hallucinated package -->
+<!-- ![SlopSentry blocking a hallucinated package in Claude Code](docs/demo.gif) -->
+
+> **Alpha (0.1.0):** only Python package installs from PyPI are checked. npm and other
+> ecosystems aren't supported yet.
+
+## Install
+
+SlopSentry needs Python 3.10 or newer. Install it as a standalone tool with
+[pipx](https://pipx.pypa.io/):
+
+```sh
+pipx install slopsentry
+```
+
+or run it without installing, using [uv](https://docs.astral.sh/uv/):
+
+```sh
+uvx slopsentry check requests
+```
+
+`pip install slopsentry` works too.
+
+For development:
+
+```sh
+python3 -m venv .venv
+.venv/bin/pip install -e ".[dev]"
+```
+
+## Usage
+
+```sh
+slopsentry check requests
+```
+
+`check` runs every check, adds up the risk points, and gives a verdict:
+
+| Check     | Flags                                                 | Points |
+| --------- | ----------------------------------------------------- | ------ |
+| exists    | package not found on PyPI                             | 100    |
+| age       | first release under 90 days ago, or no released files | 40     |
+| age       | two or fewer releases                                 | 20     |
+| age       | no homepage or repository link                        | 20     |
+| lookalike | resembles a popular package (see below)               | 50     |
+| lookalike | resembles one, but the age check passes cleanly       | 15     |
+
+| Verdict | Total points | Exit code |
+| ------- | ------------ | --------- |
+| PASS    | under 30     | 0         |
+| WARN    | 30 to 69     | 0         |
+| BLOCK   | 70 or more   | 1         |
+
+If PyPI can't be reached, the package can't be verified: the verdict is at least WARN and
+the exit code 0, or ERROR with exit code 2 under `--strict`. Empty or invalid input is an
+ERROR with exit code 2. Thresholds live in `slopsentry/scoring.py`.
+
+Without `--explain`, `check` prints one summary line plus the reasons for a WARN or
+BLOCK. With `--explain` it prints a table of every check's status, detail and points:
+
+```sh
+slopsentry check --explain requests
+```
+
+### Lookalike check
+
+The lookalike check compares the name with the 5,000 most-downloaded PyPI packages,
+bundled in `slopsentry/data/top_pypi.json`. Popular packages are never flagged, so
+`requests` passes even though it's close to other names. A name is flagged if:
+
+- it differs from a popular name only by separators (`django-rest-framework` vs
+  `djangorestframework`),
+- it adds or removes `py-`, `python-`, `-py`, `-python` or `-lib` (`python-requests`,
+  `pandas-py`), or
+- it's within Damerau-Levenshtein distance 1 of a popular name, or 2 for names longer
+  than 10 characters (`reqeusts`, `numpyy`).
+
+Two guards cut false positives on legitimate packages:
+
+1. **Short names:** names under 5 characters get no edit-distance matching, since almost
+   every short name is one edit from another (`sax`/`six`, `od`/`id`).
+2. **Package families:** a distance-2 match is ignored when the names differ in exactly
+   one whole `-` segment, such as `mypy-boto3-emr` and `mypy-boto3-ec2`.
+
+The reason names the package it resembles, e.g. "looks like requests". If the package is
+established (the age check passes cleanly), the match adds only 15 points and reads
+"looks like requests (established package)": shown in `--explain`, but not enough to warn
+by itself. A new or thin lookalike adds 50, so one that is also brand new blocks.
+
+To refresh the bundled list (it needs the network, or a downloaded copy of the dataset):
+
+```sh
+.venv/bin/python scripts/update_top_packages.py
+```
+
+`PACKAGE` can be a full requirement: `requests==2.31.0` and `requests[socks]` are
+checked as `requests`. Invalid input is rejected before any request is made.
+
+Names are normalised per PEP 503, so `Requests` and `typing_extensions` match
+`requests` and `typing-extensions`.
+
+Use `--strict` to treat an unreachable registry as a failure:
+
+```sh
+slopsentry check --strict requests
+```
+
+## Claude Code hook
+
+`slopsentry hook` is a Claude Code `PreToolUse` hook. It reads the hook event on stdin,
+finds install commands in Bash tool calls, scores each package, and answers on stdout:
+
+| Worst verdict | Decision                                         |
+| ------------- | ------------------------------------------------ |
+| BLOCK         | `deny`, with the package, score and reasons      |
+| WARN          | `ask`, so you confirm before it runs             |
+| PASS          | allowed silently                                 |
+
+It recognises `pip install` (also `pip3`, `python -m pip`, `python3 -m pip`), `uv add`,
+`uv pip install` and `poetry add`, including in chained commands (`&&`, `||`, `;`, `|`)
+and after `sudo`, `env` or `VAR=value` prefixes. Flags, local paths, URLs, `-e` and `-r`
+arguments are skipped. Commands that use a custom index (`--index-url`, `-i`,
+`--extra-index-url`, `-f`/`--find-links`, uv's `--index`/`--default-index`, poetry's
+`--source`) aren't checked, since their packages may not be on PyPI. In 0.1.0 only
+Python installs are checked; `npm install`, `yarn add` and other ecosystems pass through
+unchecked.
+
+The hook fails open: it always exits 0. Commands it can't parse, registry errors (5 second
+timeout) and its own crashes all allow the command. Crashes are appended with a timestamp
+to `~/.slopsentry/hook.log`; add `--debug` to also print them to stderr.
+
+### Setting up the hook
+
+1. Install SlopSentry so `slopsentry` is on your `PATH`:
+
+   ```sh
+   pipx install slopsentry
+   slopsentry --help
+   ```
+
+2. Add the hook to `.claude/settings.json` in a project, or to `~/.claude/settings.json`
+   to cover every project:
+
+   ```json
+   {
+     "hooks": {
+       "PreToolUse": [
+         {
+           "matcher": "Bash",
+           "hooks": [
+             {
+               "type": "command",
+               "command": "slopsentry hook || true",
+               "timeout": 30
+             }
+           ]
+         }
+       ]
+     }
+   }
+   ```
+
+   `|| true` keeps Claude Code working if `slopsentry` isn't installed on a machine
+   where the settings file is shared.
+
+3. Restart Claude Code, then check it in `/hooks`. Asking Claude to run
+   `pip install reqeusts` should be blocked.
+
+If you use uv and don't want to install anything, use `"command": "uvx slopsentry hook || true"`
+instead. The first run downloads SlopSentry, so it's slower.
+
+When working on SlopSentry itself, point the hook at your checkout instead:
+`"\"$CLAUDE_PROJECT_DIR\"/.venv/bin/slopsentry hook || true"`.
+
+### Known gaps
+
+The hook reads the command text; it doesn't run a shell. These installs get past it:
+
+- **`bash -c "pip install x"`** (and `sh -c`, `eval`): the install is inside a string
+  argument that isn't parsed.
+- **`$(...)` and backtick subshells**, e.g. `pip install $(cat pkgs.txt)`: the package
+  names only exist once the shell runs.
+- **`xargs`**, e.g. `cat pkgs.txt | xargs pip install`: the names arrive on stdin.
+- **`-r requirements.txt`**: requirement files aren't read, so their packages aren't
+  checked.
+- **`--extra-index-url` dependency confusion**: commands with an extra index are skipped
+  entirely. pip picks the highest version across all indexes, so an attacker can publish
+  your private package's name on PyPI with a higher version, and it wins.
+
+## Data attribution
+
+`slopsentry/data/top_pypi.json` is derived from
+[Top PyPI Packages](https://hugovk.dev/top-pypi-packages/) by Hugo van Kemenade and
+contributors ([DOI 10.5281/zenodo.23082845](https://doi.org/10.5281/zenodo.23082845)),
+release 2026.10.1, licensed under
+[CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Changes: kept the top 5,000
+names in download order, normalised them per PEP 503, and removed the download counts.

slopsentry-0.1.0/README.md

@@ -0,0 +1,202 @@
+# SlopSentry
+
+SlopSentry checks packages for **slopsquatting** before you install them: AI-hallucinated
+package names and malicious lookalikes that attackers register to catch them.
+
+<!-- TODO: demo GIF of the Claude Code hook blocking a hallucinated package -->
+<!-- ![SlopSentry blocking a hallucinated package in Claude Code](docs/demo.gif) -->
+
+> **Alpha (0.1.0):** only Python package installs from PyPI are checked. npm and other
+> ecosystems aren't supported yet.
+
+## Install
+
+SlopSentry needs Python 3.10 or newer. Install it as a standalone tool with
+[pipx](https://pipx.pypa.io/):
+
+```sh
+pipx install slopsentry
+```
+
+or run it without installing, using [uv](https://docs.astral.sh/uv/):
+
+```sh
+uvx slopsentry check requests
+```
+
+`pip install slopsentry` works too.
+
+For development:
+
+```sh
+python3 -m venv .venv
+.venv/bin/pip install -e ".[dev]"
+```
+
+## Usage
+
+```sh
+slopsentry check requests
+```
+
+`check` runs every check, adds up the risk points, and gives a verdict:
+
+| Check     | Flags                                                 | Points |
+| --------- | ----------------------------------------------------- | ------ |
+| exists    | package not found on PyPI                             | 100    |
+| age       | first release under 90 days ago, or no released files | 40     |
+| age       | two or fewer releases                                 | 20     |
+| age       | no homepage or repository link                        | 20     |
+| lookalike | resembles a popular package (see below)               | 50     |
+| lookalike | resembles one, but the age check passes cleanly       | 15     |
+
+| Verdict | Total points | Exit code |
+| ------- | ------------ | --------- |
+| PASS    | under 30     | 0         |
+| WARN    | 30 to 69     | 0         |
+| BLOCK   | 70 or more   | 1         |
+
+If PyPI can't be reached, the package can't be verified: the verdict is at least WARN and
+the exit code 0, or ERROR with exit code 2 under `--strict`. Empty or invalid input is an
+ERROR with exit code 2. Thresholds live in `slopsentry/scoring.py`.
+
+Without `--explain`, `check` prints one summary line plus the reasons for a WARN or
+BLOCK. With `--explain` it prints a table of every check's status, detail and points:
+
+```sh
+slopsentry check --explain requests
+```
+
+### Lookalike check
+
+The lookalike check compares the name with the 5,000 most-downloaded PyPI packages,
+bundled in `slopsentry/data/top_pypi.json`. Popular packages are never flagged, so
+`requests` passes even though it's close to other names. A name is flagged if:
+
+- it differs from a popular name only by separators (`django-rest-framework` vs
+  `djangorestframework`),
+- it adds or removes `py-`, `python-`, `-py`, `-python` or `-lib` (`python-requests`,
+  `pandas-py`), or
+- it's within Damerau-Levenshtein distance 1 of a popular name, or 2 for names longer
+  than 10 characters (`reqeusts`, `numpyy`).
+
+Two guards cut false positives on legitimate packages:
+
+1. **Short names:** names under 5 characters get no edit-distance matching, since almost
+   every short name is one edit from another (`sax`/`six`, `od`/`id`).
+2. **Package families:** a distance-2 match is ignored when the names differ in exactly
+   one whole `-` segment, such as `mypy-boto3-emr` and `mypy-boto3-ec2`.
+
+The reason names the package it resembles, e.g. "looks like requests". If the package is
+established (the age check passes cleanly), the match adds only 15 points and reads
+"looks like requests (established package)": shown in `--explain`, but not enough to warn
+by itself. A new or thin lookalike adds 50, so one that is also brand new blocks.
+
+To refresh the bundled list (it needs the network, or a downloaded copy of the dataset):
+
+```sh
+.venv/bin/python scripts/update_top_packages.py
+```
+
+`PACKAGE` can be a full requirement: `requests==2.31.0` and `requests[socks]` are
+checked as `requests`. Invalid input is rejected before any request is made.
+
+Names are normalised per PEP 503, so `Requests` and `typing_extensions` match
+`requests` and `typing-extensions`.
+
+Use `--strict` to treat an unreachable registry as a failure:
+
+```sh
+slopsentry check --strict requests
+```
+
+## Claude Code hook
+
+`slopsentry hook` is a Claude Code `PreToolUse` hook. It reads the hook event on stdin,
+finds install commands in Bash tool calls, scores each package, and answers on stdout:
+
+| Worst verdict | Decision                                         |
+| ------------- | ------------------------------------------------ |
+| BLOCK         | `deny`, with the package, score and reasons      |
+| WARN          | `ask`, so you confirm before it runs             |
+| PASS          | allowed silently                                 |
+
+It recognises `pip install` (also `pip3`, `python -m pip`, `python3 -m pip`), `uv add`,
+`uv pip install` and `poetry add`, including in chained commands (`&&`, `||`, `;`, `|`)
+and after `sudo`, `env` or `VAR=value` prefixes. Flags, local paths, URLs, `-e` and `-r`
+arguments are skipped. Commands that use a custom index (`--index-url`, `-i`,
+`--extra-index-url`, `-f`/`--find-links`, uv's `--index`/`--default-index`, poetry's
+`--source`) aren't checked, since their packages may not be on PyPI. In 0.1.0 only
+Python installs are checked; `npm install`, `yarn add` and other ecosystems pass through
+unchecked.
+
+The hook fails open: it always exits 0. Commands it can't parse, registry errors (5 second
+timeout) and its own crashes all allow the command. Crashes are appended with a timestamp
+to `~/.slopsentry/hook.log`; add `--debug` to also print them to stderr.
+
+### Setting up the hook
+
+1. Install SlopSentry so `slopsentry` is on your `PATH`:
+
+   ```sh
+   pipx install slopsentry
+   slopsentry --help
+   ```
+
+2. Add the hook to `.claude/settings.json` in a project, or to `~/.claude/settings.json`
+   to cover every project:
+
+   ```json
+   {
+     "hooks": {
+       "PreToolUse": [
+         {
+           "matcher": "Bash",
+           "hooks": [
+             {
+               "type": "command",
+               "command": "slopsentry hook || true",
+               "timeout": 30
+             }
+           ]
+         }
+       ]
+     }
+   }
+   ```
+
+   `|| true` keeps Claude Code working if `slopsentry` isn't installed on a machine
+   where the settings file is shared.
+
+3. Restart Claude Code, then check it in `/hooks`. Asking Claude to run
+   `pip install reqeusts` should be blocked.
+
+If you use uv and don't want to install anything, use `"command": "uvx slopsentry hook || true"`
+instead. The first run downloads SlopSentry, so it's slower.
+
+When working on SlopSentry itself, point the hook at your checkout instead:
+`"\"$CLAUDE_PROJECT_DIR\"/.venv/bin/slopsentry hook || true"`.
+
+### Known gaps
+
+The hook reads the command text; it doesn't run a shell. These installs get past it:
+
+- **`bash -c "pip install x"`** (and `sh -c`, `eval`): the install is inside a string
+  argument that isn't parsed.
+- **`$(...)` and backtick subshells**, e.g. `pip install $(cat pkgs.txt)`: the package
+  names only exist once the shell runs.
+- **`xargs`**, e.g. `cat pkgs.txt | xargs pip install`: the names arrive on stdin.
+- **`-r requirements.txt`**: requirement files aren't read, so their packages aren't
+  checked.
+- **`--extra-index-url` dependency confusion**: commands with an extra index are skipped
+  entirely. pip picks the highest version across all indexes, so an attacker can publish
+  your private package's name on PyPI with a higher version, and it wins.
+
+## Data attribution
+
+`slopsentry/data/top_pypi.json` is derived from
+[Top PyPI Packages](https://hugovk.dev/top-pypi-packages/) by Hugo van Kemenade and
+contributors ([DOI 10.5281/zenodo.23082845](https://doi.org/10.5281/zenodo.23082845)),
+release 2026.10.1, licensed under
+[CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Changes: kept the top 5,000
+names in download order, normalised them per PEP 503, and removed the download counts.

slopsentry-0.1.0/RELEASING.md

@@ -0,0 +1,25 @@
+# Releasing
+
+1. **Bump the version in both places, together:**
+   - `pyproject.toml` → `[project] version`
+   - `npm/package.json` → `version`
+
+   They must match. The npm wrapper runs `uvx slopsentry@<its own version>`, so an npm
+   release whose version isn't on PyPI fails for every user.
+2. Run `pytest` and `ruff check`, and confirm CI is green on `main`.
+3. Build and check locally: `python -m build` and `twine check --strict dist/*`.
+4. Publish to TestPyPI: run the **Publish** workflow manually (Actions → Publish → Run
+   workflow, or `gh workflow run publish.yml`). Then install it into a fresh venv:
+
+   ```sh
+   pip install -i https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ slopsentry==X.Y.Z
+   slopsentry check requests
+   ```
+
+5. Tag and push: `git tag vX.Y.Z && git push origin vX.Y.Z`. The Publish workflow checks
+   the tag matches `pyproject.toml` and publishes to PyPI.
+6. Once the version is live on PyPI, publish the npm wrapper: `cd npm && npm publish`.
+   Check it with `npx slopsentry@X.Y.Z check requests`.
+
+Trusted Publishing is configured on pypi.org and test.pypi.org for this repo, workflow
+`publish.yml`, with environments `pypi` and `testpypi`.

slopsentry-0.1.0/npm/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Rajeshr-developer
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

slopsentry-0.1.0/npm/README.md

@@ -0,0 +1,54 @@
+# slopsentry (npm wrapper)
+
+This package is a thin wrapper around [SlopSentry](https://github.com/Rajeshr-developer/slopsentry),
+a Python CLI that checks packages for **slopsquatting** (AI-hallucinated package names and
+malicious lookalikes) before they're installed.
+
+It contains no checking logic of its own. The `slopsentry` command runs
+`uvx slopsentry@<version>` and passes every argument, stdin, stdout and the exit code
+straight through, so it behaves exactly like the Python tool.
+
+The Python version is pinned to this package's version: `slopsentry@0.1.0` on npm always
+runs `slopsentry==0.1.0` from PyPI, never whatever uv happens to have cached.
+
+> **Alpha (0.1.0):** SlopSentry only checks Python package installs from PyPI. It doesn't
+> check npm packages yet, despite being installable from npm.
+
+## Requirements
+
+- Node.js 18 or newer
+- [uv](https://docs.astral.sh/uv/getting-started/installation/), which provides `uvx`.
+  uv downloads Python and SlopSentry on first run, so the first call is slower.
+
+If `uvx` isn't on your `PATH`, the wrapper prints install instructions and exits with
+code 127.
+
+## Usage
+
+```sh
+npx slopsentry check requests
+npx slopsentry check --explain reqeusts
+```
+
+or install it globally:
+
+```sh
+npm install -g slopsentry
+slopsentry check requests
+```
+
+As a Claude Code `PreToolUse` hook, use `"command": "npx -y slopsentry hook || true"`.
+See the [main README](https://github.com/Rajeshr-developer/slopsentry#claude-code-hook)
+for the full setup and what the hook checks.
+
+## Prefer the Python package
+
+If you have Python, installing it directly avoids the Node and uv layers:
+
+```sh
+pipx install slopsentry
+```
+
+## License
+
+MIT

slopsentry-0.1.0/npm/bin/slopsentry.js

@@ -0,0 +1,44 @@
+#!/usr/bin/env node
+// Thin wrapper: runs the Python SlopSentry CLI through uvx, passing every argument through.
+
+"use strict";
+
+const { spawn } = require("node:child_process");
+const { version } = require("../package.json");
+
+// Pinned to the npm package version, so each npm release runs the matching PyPI release.
+const pkg = `slopsentry@${version}`;
+
+const child = spawn("uvx", [pkg, ...process.argv.slice(2)], { stdio: "inherit" });
+
+child.on("error", (err) => {
+  if (err.code === "ENOENT") {
+    console.error(
+      [
+        "slopsentry: uv is not installed (the `uvx` command wasn't found on PATH).",
+        "",
+        "This npm package is a wrapper that runs the Python tool with uv. Install uv:",
+        "  macOS / Linux:  curl -LsSf https://astral.sh/uv/install.sh | sh",
+        '  Windows:        powershell -c "irm https://astral.sh/uv/install.ps1 | iex"',
+        "  or see https://docs.astral.sh/uv/getting-started/installation/",
+        "",
+        "Or install SlopSentry directly with: pipx install slopsentry",
+      ].join("\n"),
+    );
+    process.exit(127);
+  }
+  console.error(`slopsentry: failed to run uvx: ${err.message}`);
+  process.exit(1);
+});
+
+for (const signal of ["SIGINT", "SIGTERM"]) {
+  process.on(signal, () => child.kill(signal));
+}
+
+child.on("exit", (code, signal) => {
+  if (signal) {
+    process.kill(process.pid, signal);
+  } else {
+    process.exit(code ?? 1);
+  }
+});

slopsentry-0.1.0/npm/package.json

@@ -0,0 +1,33 @@
+{
+  "name": "slopsentry",
+  "version": "0.1.0",
+  "description": "Check packages for slopsquatting before they are installed. npm wrapper for the Python SlopSentry CLI (runs it with uvx).",
+  "keywords": [
+    "security",
+    "supply-chain",
+    "slopsquatting",
+    "typosquatting",
+    "claude-code"
+  ],
+  "homepage": "https://github.com/Rajeshr-developer/slopsentry",
+  "bugs": {
+    "url": "https://github.com/Rajeshr-developer/slopsentry/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Rajeshr-developer/slopsentry.git",
+    "directory": "npm"
+  },
+  "license": "MIT",
+  "author": "Rajeshr-developer <rajeshr.developer@gmail.com>",
+  "bin": {
+    "slopsentry": "bin/slopsentry.js"
+  },
+  "files": [
+    "bin/",
+    "LICENSE"
+  ],
+  "engines": {
+    "node": ">=18"
+  }
+}