# Install jsign with Homebrew, chocolatey, Nix, scoop

Tool for signing Windows executable files, installers and scripts. Version 7.5 via Homebrew; verified 2026-07-16. Also installable with nix: nix profile install nixpkgs#jsign.

## Install

```sh
sudo av install brew:jsign
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install jsign
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#jsign
```

  Evidence: nixpkgs package indexes: pkgs/by-name/js/jsign/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

### Windows

- Chocolatey (92%):

```sh
choco install jsign
```

  Evidence: Chocolatey community package catalog: jsign from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='10.102','registrychangesview'

- Scoop (92%):

```sh
scoop install main/jsign
```

  Evidence: Scoop official bucket manifest trees: bucket/jsign.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:jsign
- **Package manager:** Homebrew
- **Version:** 7.5
- **Source summary:** Tool for signing Windows executable files, installers and scripts
- **Homepage:** <https://ebourg.github.io/jsign/>
- **Repository:** <https://github.com/ebourg/jsign>
- **Last updated:** 2026-07-16T12:18:17Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- jsign (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 7.5
## Project history and usage

Jsign is a Java implementation of Microsoft Authenticode signing for Windows executables, installers, packages, scripts, and related file formats. Its niche is cross-platform code signing: Linux and macOS build machines can sign Windows artifacts without depending on Microsoft's `signtool` on Windows.

### Project history

The project presents itself as a platform-independent alternative to native Windows signing tools and Mono development tools. The upstream README emphasizes signing executable wrappers and installers produced by NSIS, msitools, install4j, exe4j, and launch4j, then expands into build-system tasks and a Java library.

Jsign's release history shows steady expansion from Authenticode file signing into modern signing operations. Version 4.1 in May 2022 added SSL.com eSigner integration and improved key/password handling; 5.0 in June 2023 integrated AWS KMS; 6.0 in January 2024 added APPX/MSIX and Dynamics 365 package signing; 7.0 in January 2025 added Azure Trusted Signing, Oracle Cloud, GaraSign, HashiCorp Vault Transit, Keyfactor SignServer, NuGet package signing, signature extraction/removal, and verbosity controls.

### Adoption history

Jsign gained practical adoption among teams that build Windows deliverables outside Windows, or that need hardware-token and cloud-KMS signing in CI. Vendor documentation from code-signing providers documents Jsign workflows, reflecting its use as an interoperable third-party signing client rather than only an upstream developer utility.

### How it is used

Common usage is to run the `jsign` CLI with a keystore, alias, password or external signing service, and one or more files to sign or timestamp. The same functionality is exposed through Maven, Gradle, Ant, GitHub Actions, and Java APIs for build pipelines that need repeatable signing steps.

### Why package nerds care

Jsign matters to package people because it turns Authenticode signing into a portable build dependency. That is especially useful for reproducible or cross-platform packaging systems where Windows artifacts are produced on non-Windows infrastructure and private keys live in hardware tokens, PKCS#11 modules, or cloud KMS services.

### Timeline

- 2022: Version 4.1 adds SSL.com eSigner support and improves password and certificate handling.
- 2023: Version 5.0 integrates AWS KMS and improves hardware-token support.
- 2024: Version 6.0 adds APPX/MSIX signing and a JCA provider.
- 2025: Version 7.0 adds multiple cloud signing services, NuGet package signing, and signature-management commands.
- 2025: Versions 7.1 through 7.4 add SignPath, EFI multiple signatures, CryptoCertum support, and further cloud/token fixes.

### Related projects

- Jsign is related to Microsoft's `signtool`, Mono's Authenticode tooling, `osslsigncode`, Java `jarsigner` workflows through its JCA provider, and installer/package generators such as NSIS, MSI tooling, install4j, exe4j, launch4j, APPX/MSIX, and NuGet.

### Sources

- <https://docs.digicert.com/en/software-trust-manager/client-tools/signing-tools/third-party-signing-tool-integrations/jsign.html>
- <https://ebourg.github.io/jsign>
- <https://github.com/ebourg/jsign>
- <https://github.com/ebourg/jsign/blob/master/README.md>
- <https://github.com/ebourg/jsign/releases>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals

## Other Package-Manager Records

- Nix - jsign: normalized package name match | nixpkgs package indexes: pkgs/by-name/js/jsign/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Chocolatey - jsign: normalized package name match | Chocolatey community package catalog: jsign from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='10.102','registrychangesview'
- Scoop - main/jsign: normalized package name match | Scoop official bucket manifest trees: bucket/jsign.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/jsign.yml](https://github.com/mxcl/pkgdb/blob/main/combined/jsign.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph