@orchlane/the-configurator
v0.1.0
Published
Migrate Check Point security configurations to Palo Alto Networks (Panorama or standalone PAN-OS). Single-binary migration engine, CLI, and local web UI — runs entirely inside your environment.
Maintainers
Readme
@orchlane/the-configurator
Migrate Check Point security configurations to Palo Alto Networks (Panorama or standalone PAN-OS). Single-binary migration engine, CLI, and local web UI — runs entirely inside your own environment. No SaaS dependency, no data leaves your network unless you explicitly opt an LLM call into it.
Install / run
npx @orchlane/the-configurator@latest setupsetup runs a first-run health check (workspace, TLS cert, loopback bind,
credential storage, LLM availability) and writes your local configuration.
Re-run it any time — it's safe and idempotent.
Or install it on PATH:
npm install -g @orchlane/the-configurator
the-configurator setupQuick start
the-configurator plan # interactive wizard → a migration plan
the-configurator run # execute the plan
the-configurator ui # local web UI (dashboard, review queue, reports)
the-configurator doctor # re-run the health checks without writing anything
the-configurator --help # full command listSupported platforms
| OS | Architecture |
|---|---|
| macOS | Apple Silicon (arm64), Intel (x64) |
| Windows | x64, arm64 |
npm install fetches only the one prebuilt binary that matches your machine
(os/cpu in package.json make npm skip the other three) — about 20-25 MB,
not four times that.
No other platform is supported yet. On an unsupported platform, or if the
matching platform package didn't install (--omit=optional and similar), the
CLI prints exactly which platform it detected and how to fix it, rather than
failing silently.
Why this install path
- No
postinstallscript, no download at install time. The binary ships inside the npm tarball itself, sonpm ci --ignore-scriptsand locked-down proxies both work — nothing reaches out to GitHub afternpm install. - Registry integrity, not a hand-rolled checksum. The binary is covered by
npm's own
integrityhash in your lockfile. - No Gatekeeper prompt on macOS. Binaries installed this way carry no
quarantine attribute, unlike a browser-downloaded
.dmg.
Other ways to get it
- Windows, via Scoop:
scoop bucket add orchlane https://github.com/orchlane/scoop-bucket && scoop install the-configurator - macOS, double-clickable app: download the
.dmgfrom GitHub Releases - Air-gapped / no npm: download the
.tar.gz/.ziparchive from GitHub Releases and verify it against the release'schecksums.txt
Package layout
This package (@orchlane/the-configurator) is a thin launcher: it has no
dependencies of its own and contains no binary. At install time npm also
installs whichever one of these four matches your machine:
@orchlane/the-configurator-darwin-arm64@orchlane/the-configurator-darwin-x64@orchlane/the-configurator-win32-x64@orchlane/the-configurator-win32-arm64
You should never need to depend on a platform package directly.
License
See LICENSE.
