Downloads

Every package as a tarball, for installing without a registry: a @bitskiff/ name resolves nothing; npm install takes a URL as well as a name.

Install into a project directory—npm walks up to the nearest package.json—and make it ESM, which every example here is:

npm init -y
npm pkg set type=module

Every package here is Apache-2.0, and each tarball carries the text.

JavaScript

These builds talk to the dev service (https://api.dev.bitskiff.com); another environment's release carries its own address.

@bitskiff/host-node installs @bitskiff/host as well: the dependency is the URL of the host tarball on this page, and both land at the top level, one copy each.

The command-line tool installs globally, which is what puts bitskiff on your path.

Each URL above names its version and never changes: a new release goes up beside it, never over it. /downloads/latest/ carries the same file names without the version and moves to each new release, which is for trying things; an app that ships pins a version.

/downloads/dev/ carries a development build under the same file names: the working build between releases, replaced on every publish and never a release.

To check a tarball against the hash beside it: shasum -a 256 <file>, or Get-FileHash <file> -Algorithm SHA256 in PowerShell.

Every package here needs Node 22 or later.

The same list as JSON: manifest.json.

Samples

Code to copy and run on your own infrastructure. Unpack it with tar -xzf <file> and read its README.