npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sentineldev/engine-darwin-x64

v0.2.0

Published

Frozen Sentinel analysis engine for darwin-x64

Readme

@sentineldev/engine-<os>-<cpu> — bundled Python analysis engine

These are the per-platform npm packages that let npm install -g sentineldev work with no separate pip install, no system Python. Each contains a PyInstaller-frozen (onedir) build of the Sentinel analysis engine (sentinel_worker.local_cli:main). They mirror how esbuild / @swc/core / turbo ship native binaries through npm optionalDependencies.

How the CLI picks one

sentineldev lists all five as optionalDependencies (see cli/package.json). npm installs only the package whose os/cpu fields match the host, so a mac arm64 box gets just @sentineldev/engine-darwin-arm64. At runtime cli/src/engine/localEngine.ts::resolveEngineCommand() resolves the installed one via require.resolve("@sentineldev/engine-<platform>-<arch>/bin/sentinel-local") and runs it directly. If none is installed it falls back to SENTINEL_ENGINE_BIN, then to python -m sentinel_worker.local_cli (source/dev).

Targets

| npm package | os | cpu | Runner | |------------------------------------|---------|---------|-------------------| | @sentineldev/engine-darwin-arm64 | darwin | arm64 | macos-14 | | @sentineldev/engine-darwin-x64 | darwin | x64 | macos-13 | | @sentineldev/engine-linux-x64 | linux | x64 | ubuntu-latest | | @sentineldev/engine-linux-arm64 | linux | arm64 | ubuntu-24.04-arm | | @sentineldev/engine-win32-x64 | win32 | x64 | windows-latest |

Package layout (built in CI, never committed)

@sentineldev/engine-darwin-arm64/
  package.json            # name, version, "os":["darwin"], "cpu":["arm64"]
  bin/
    sentinel-local        # PyInstaller launcher (sentinel-local.exe on win32)
    _internal/            # frozen CPython + deps + tree-sitter grammar .so/.dylib/.pyd
    sentinel_worker/prompts/*.txt
    alembic/versions/*.py

bin/sentinel-local is the onedir launcher; it must stay next to its _internal/ sibling (do not move it out on its own). package.json per target:

{
  "name": "@sentineldev/engine-darwin-arm64",
  "version": "0.2.0",
  "os": ["darwin"],
  "cpu": ["arm64"],
  "files": ["bin"]
}

Building locally

worker/pyinstaller/build.sh        # freezes into worker/pyinstaller/dist/sentinel-local/

Then copy worker/pyinstaller/dist/sentinel-local/ → the target package's bin/. CI does this across the matrix in .github/workflows/build-engine.yml.

Signing (CI-pending)

macOS builds must be codesigned + notarized and Windows builds Authenticode signed before publish, or Gatekeeper/SmartScreen will block the frozen binary. The workflow has these as commented TODO steps — no secrets are wired yet.