JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 11
  • Score
    100M100P100Q60394F
  • License MIT

Security gate for npm, yarn and pnpm: verifies lockfile integrity and tarball hashes before installation

Package Exports

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (sentinel-check) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    sentinel-check

    Thin npm wrapper for the sentinel CLI published from the sentinel-npm repository.

    Use npx --yes sentinel-check ... for one-shot runs with no manual binary setup.

    Sentinel supports lockfile verification for npm, Yarn, and pnpm with automatic manager detection.


    Quick start

    Run directly with npx

    # audit only
    npx --yes sentinel-check check
    
    # validate lockfile then install dependencies
    npx --yes sentinel-check ci
    
    # install one package with verification
    npx --yes sentinel-check install lodash@4.17.21

    Install once in the project and call sentinel from npm scripts:

    npm install -D sentinel-check
    {
      "scripts": {
        "sentinel:check": "sentinel check",
        "sentinel:ci": "sentinel ci"
      }
    }
    npm run sentinel:check
    npm run sentinel:ci

    Need package install with verification? Run it directly:

    npx --yes sentinel-check install lodash@4.17.21

    CI usage

    GitHub Actions:

    - name: Verify dependency integrity
      run: npx --yes sentinel-check ci

    If the workflow needs Sentinel to initialize the lockfile first:

    - name: Initialize lockfile and verify dependency integrity
      run: npx --yes sentinel-check ci --init-lockfile

    Notes

    1. The wrapper downloads the matching Sentinel release binary on first use.
    2. Downloaded binaries are cached locally.
    3. Integrity is verified using release checksums before execution.
    4. If you see dependency cycles detected, Sentinel found circular dependency chains in the lockfile graph. Verification continues and cycles are reported as a warning. You'll still see the integrity status of all packages. For a safe first recovery step, remove node_modules and rerun npx --yes sentinel-check ci. If lockfile recovery is needed, remove the lockfile and rerun npx --yes sentinel-check ci --init-lockfile so Sentinel regenerates it in the guarded flow.

    More documentation


    Useful environment variables

    Variable Description
    SENTINEL_BIN Use an existing local sentinel binary
    SENTINEL_VERSION Pin a specific Sentinel version
    SENTINEL_SKIP_DOWNLOAD=1 Disable automatic binary download

    See the main README for full CLI usage and binary installation options.