Jenkins CLI releases

Current version 0.0.42. Each version below is listed with the date HOL first saw it in the registry and what the catalog reported for it: supported runtimes, what it ships, its Trust Score and scan result.

Versions

  1. 0.0.42

    First seen by HOL

    What changed

    • Trust Score 60 → 78
    • Scan result Findings to review closely → Findings to review
    • Scan findings 5 → 9
    • New finding areas: best-practices and manifest-validation
    • Cleared finding areas: operational-security, publishability and skill-security
    Runtimes
    Claude Code, Codex
    Ships
    1 skill, 0 MCP servers, 0 apps
    Trust Score
    78 / 100
    Scan result
    Findings to review, 9 findings
    Attestation
    No signed release attestation published
    Source commit
    d383e0326893

  2. 0.0.39

    First seen by HOL · registry updated

    First version HOL recorded for this plugin, so there is nothing earlier to compare.

    Runtimes
    Claude Code, Codex
    Ships
    1 skill, 0 MCP servers, 0 apps
    Trust Score
    60 / 100
    Scan result
    Findings to review closely, 5 findings
    Attestation
    No signed release attestation published
    Source commit
    5f75464322cc

Release integrity

What each channel served for Jenkins CLI the last time HOL checked. A digest is the start of the build's SHA-256 or, for a source repository, the commit's git tree hash. Different values mean different content; they do not say which one is right.

Channels serving Jenkins CLI
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)0.0.42c5aef954670ccommit d383e0326893

No integrity events recorded.

How HOL records release integrity

How this is recorded

HOL checks the registry once a day, so a version replaced within a day may not appear, and versions published before 24 October 2026 are not listed. The facts are what the registry reported, not a signed statement from the author. A checked release is different: the author's release workflow scanned it, checked it with the Plugin Kit and signed the result with a GitHub attestation. It does not mean the plugin is free of vulnerabilities. See how the Trust Score is computed or go back to Jenkins CLI.