Block hallucinated and slopsquatted npm and PyPI dependencies in pull requests.

Coding agents invent package names. Attackers register the ones that repeat. This action runs pkgtruth against every manifest in the target directory — package.json, requirements*.txt, pyproject.toml — on every pull request, posts a sticky comment with the evidence, and fails the check when something must not be installed.

name: Dependency gate
on:
  pull_request:
    paths:
      - '**/package.json'
      - '**/requirements*.txt'
      - '**/pyproject.toml'

permissions:
  contents: read
  pull-requests: write   # for the sticky comment; drop it and set comment: false if you only want the check

jobs:
  pkgtruth:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: hxckya/pkgtruth-action@v1

Live examples it blocks today: crossenv (purged, ~1,400 installs/week), supabase-js (purged — a model dropped the scope from @supabase/supabase-js), types-node; on PyPI, sklearn (~320,000 installs/week that belong to scikit-learn) and pytorch (a decoy whose only content says to install torch). The weekly list is in SLOPSQUATS.md.

blocking, total, report (path to the JSON).

It reads registry metadata only — it does not analyze package source, so a legitimate-looking package carrying a payload still passes. It is not a replacement for npm audit, Dependabot, or Socket; those answer "is this trusted code vulnerable?". This answers the earlier question: should this package be here at all?

A legitimate package that gets flagged is a bug. Please open an issue — that is the report this project most wants.

MIT © hxckya