Automic VaultAutomic Vault

brew

jsign mit Homebrew, Nix, scoop installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für jsign in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install jsign

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#jsign

nixpkgs package indexes · pkgs/by-name/js/jsign/package.nix · Quelle: api.github.com

Windows

Scoopverifiziert · 92%
scoop install main/jsign

Scoop official bucket manifest trees · bucket/jsign.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Tool for signing Windows executable files, installers and scripts

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
jsigncliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version7.5
Manager aktualisiert2026-07-16
lokale DatenOK
Upstreamaktuell
neueste erkannte Version7.5

https://github.com/ebourg/jsign

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:jsign
Version7.5
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/jsign
Homepagehttps://ebourg.github.io/jsign/
Repositoryhttps://github.com/ebourg/jsign
Upstream-Dokumentationhttps://ebourg.github.io/jsign
LizenzApache-2.0
Quellarchivhttps://github.com/ebourg/jsign/archive/refs/tags/7.5.tar.gz
Zuletzt aktualisiert2026-07-16T12:18:17Z
Pulseupdated
Abhängigkeitenopenjdk@21
Build-Abhängigkeitenmaven
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namejsign
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

jsign

nix profile install nixpkgs#jsign
  • normalized package name match
  • Abgeglichen nach: Jsign
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/js/jsign/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Scoop95%

main/jsign

scoop install main/jsign
  • normalized package name match
  • Abgeglichen nach: Jsign
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/jsign.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment