generated: '2026-08-12'
method: searched
source: https://registry.npmjs.org — queried per package; docs at https://developer.ci-hub.com
note: >-
  CI HUB publishes two first-party npm packages under the @ci-hub scope, one per SDK. No client
  library exists for any other language: the Access SDK docs state plainly that "the HTTP API
  underneath is fully documented and remains the path for every other language". PyPI, RubyGems,
  Packagist, crates.io, NuGet, Maven Central and pkg.go.dev were all checked and carry nothing
  first-party. The integration-sdk's own homepage field points at developers.ci-hub.com, which
  is a second hostname for the same docs site — worth noting only because it shows the two
  packages were published from different states of the docs.
packages:
- language: typescript
  registry: npm
  name: '@ci-hub/access-sdk'
  url: https://www.npmjs.com/package/@ci-hub/access-sdk
  install: npm install @ci-hub/access-sdk
  official: true
  version: 0.2.0
  published: '2026-07-27'
  license: Apache-2.0
  repository: https://github.com/CI-HUB-GmbH/access-sdk
  homepage: https://developer.ci-hub.com
  release_count: 3
  wraps: ci-hub:access-sdk
  description: >-
    Official TypeScript/JavaScript client for the Access SDK HTTP API. Wraps every currently
    available endpoint behind typed methods, owns the token lifecycle via TokenManager, and
    resolves download URL placeholders. Core depends only on fetch (browsers, Office.js add-ins,
    Node 20+, Bun, Deno); the partner-JWT signer is server-only on the @ci-hub/access-sdk/node
    subpath.
  note: >-
    Request and response types in dist/index.d.ts are generated by openapi-typescript from the
    same OpenAPI document that renders the published reference, which is what openapi/
    ci-hub-access-openapi.yml is derived from. upload() and update() are declared with their
    final signatures but throw NotImplementedError (cihub-not-implemented) until the write
    engine ships.
- language: typescript
  registry: npm
  name: '@ci-hub/integration-sdk'
  url: https://www.npmjs.com/package/@ci-hub/integration-sdk
  install: npm install @ci-hub/integration-sdk
  official: true
  version: 0.2.1
  published: '2026-06-14'
  license: MIT
  repository: https://github.com/CI-HUB-GmbH/integration-sdk
  homepage: https://developers.ci-hub.com/integration/
  release_count: 7
  wraps: ci-hub:integration-sdk
  description: >-
    Official SDK for building a CI HUB integration — the vendor-side contract that translates a
    DAM/PIM/CMS/storage platform's own API into CI HUB's handler format via defineIntegration.
    Ships the integration-cli binary used to scaffold, run locally against a test UI, and submit
    an integration.
  note: >-
    The CLI is not installed globally; it is run through npx/pnpm exec/yarn/bunx. See
    cli/ci-hub-cli.yml for the command surface.
registries_checked:
- registry: npm
  result: 2 first-party packages found under the @ci-hub scope
- registry: npm
  query: ci-hub
  result: no such package (404)
- registry: npm
  query: '@ci-hub/sdk'
  result: no such package (404)
- registry: pypi
  result: no first-party CI HUB package
- registry: rubygems
  result: no first-party CI HUB package
- registry: packagist
  result: >-
    no first-party client library. CI HUB does maintain two public Pimcore PHP bundles on GitHub
    (SimpleRESTAdapterBundle, PimcoreCIHubAdapterBundle) but they are server-side Pimcore
    integrations, not clients for the Access SDK, and both were last pushed in 2022-2023.
- registry: crates.io
  result: no first-party CI HUB package
- registry: nuget
  result: no first-party CI HUB package
- registry: maven-central
  result: no first-party CI HUB package
- registry: pkg.go.dev
  result: no first-party CI HUB package
summary:
  package_count: 2
  official_count: 2
  languages:
  - typescript
  currency: >-
    Both packages are current relative to the API they wrap. @ci-hub/access-sdk 0.2.0 published
    2026-07-27 tracks the July 2026 Access SDK changes (provider parameters on DAM login, email
    outside the JWT) announced the same month, so the client is not lagging its API.
x-evidence:
  fetched: '2026-08-12'
  checks:
  - url: https://registry.npmjs.org/@ci-hub%2Faccess-sdk
    http_status: 200
  - url: https://registry.npmjs.org/@ci-hub%2Fintegration-sdk
    http_status: 200
  - url: https://registry.npmjs.org/ci-hub
    http_status: 404