npm package reports / command-exists

What ships in command-exists?

command-exists@1.2.9 ships a clean tarball: 12 files, nothing unexpected.

“check whether a command line command exists in the current environment”

1.2.9version
12files
13.2 KBunpacked
7.5Mweekly dl

Findings

✓ No source maps, environment files, credentials, internal docs or other unexpected files in the published tarball.

Keep it this way: check every release in CI

This report covers one published version. ReleaseShield runs on every publish. It scans the exact tarball (npm pack), wheel or Docker image your pipeline builds and fails the release before anything unexpected reaches the registry.

# .github/workflows/release.yml
- uses: my2ctyw8h6-hash/release-shield@v1
  with:
    fail-on: high
  env:
    RELEASESHIELD_TOKEN: ${{ secrets.RELEASESHIELD_TOKEN }}

See plans: from $19/mo Re-scan command-exists live

Maintainer? Show it in your README

The badge reflects the latest automated scan of the published tarball and refreshes on its own. ReleaseShield report for command-exists

[![ReleaseShield](https://release-shield-app.vercel.app/api/badge/npm/command-exists.svg)](https://release-shield-app.vercel.app/npm/command-exists?ref=badge)

Other package reports

chalk · @octokit/types · @inquirer/figures · progress · cli-truncate · fast-string-width · @inquirer/prompts · import-local · ansis · uglify-js · supports-hyperlinks · @inquirer/select

Automated heuristic scan of the public tarball for command-exists@1.2.9, run on 2026-11-19. Findings describe file contents and are not a judgment of the package's security or its maintainers; many are intentional. Maintainer and want this report removed or refreshed? Open an issue at github.com/my2ctyw8h6-hash/release-shield.