career-ops releases

Current version 1.40.0. 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. 1.40.0

    First seen by HOL

    No change to runtimes, contents, Trust Score or scan result since the previous version.

    Runtimes
    Claude Code, Codex, Cursor
    Ships
    11 skills, 0 MCP servers, 0 apps
    Trust Score
    89 / 100
    Scan result
    Findings to review, 17 findings
    Attestation
    No signed release attestation published
    Source commit
    605a1e61ee2b
  2. 1.39.0

    First seen by HOL

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

    Runtimes
    Claude Code, Codex, Cursor
    Ships
    11 skills, 0 MCP servers, 0 apps
    Trust Score
    89 / 100
    Scan result
    Findings to review, 17 findings
    Attestation
    No signed release attestation published
    Source commit
    0339acb4176f

Release integrity

What each channel served for career-ops 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 career-ops
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)1.40.024e2d97f8d3fcommit 8864d68c631b
  1. Version label reused · · history only

    The source changed under version label 1.40.0 (commit 38889534f4a8 to 8864d68c631b).

  2. Version label reused · · history only

    The source changed under version label 1.40.0 (commit 38889534f4a8 to 5286f2d1a694).

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 career-ops.