generated: '2026-09-13'
method: searched
source: >-
  npm registry search, PyPI, RubyGems and crates.io lookups on 2026-09-13, plus a full listing of the
  HPSF GitHub organization (https://github.com/hpsfoundation, 6 public repositories) and a read of
  hpsf.io for any SDK or client-library page.
name: HPSF packages and SDKs
package_count: 0
packages: []
description: >-
  HPSF publishes no client library, no SDK and no CLI for its own API surface, in any language. This is
  the expected shape: HPSF is a foundation, its API is a read-only events feed generated by a WordPress
  plugin, and there is nothing to wrap. Its six public repositories are governance and web content -
  the charter, the TAC, the website, the logos, a benchmarking working group and an org profile - and
  none of them is a package.
evidence:
- url: https://registry.npmjs.org/-/v1/search?text=hpsf&size=5
  status: 200
  note: 'Zero results ("total": 0).'
- url: https://pypi.org/pypi/hpsf/json
  status: 404
- url: https://rubygems.org/api/v1/gems/hpsf.json
  status: 404
- url: https://crates.io/api/v1/crates?q=hpsf&per_page=3
  status: 200
  note: Zero results.
- url: https://api.github.com/orgs/hpsfoundation/repos
  status: 200
  note: >-
    6 repositories - hpsf.io (website), foundation (charter), tac, hpsf-logos, .github,
    Benchmarking-WG. No package manifest in any of them.
- url: https://github.com/hpsf
  status: 200
  note: >-
    An empty placeholder organization with 0 public repositories, no name and no description. It is NOT
    the HPSF GitHub org; this record previously pointed GitHubOrg at it. The real org is hpsfoundation.
member_project_packages:
  note: >-
    Deliberately NOT recorded as HPSF packages. HPSF hosts Spack, Kokkos, Apptainer, E4S, HPX,
    Charliecloud, Chapel, Viskores, Flux Framework and Wi4MPI, and several of those do publish software
    to registries - but they publish it under their own organizations and their own release processes,
    not HPSF's. Attributing a member project's distribution to the foundation would be a
    misattribution of exactly the kind this pipeline exists to avoid. Each is a candidate for its own
    catalog record instead.
notes:
- >-
  Recorded as an explicit zero rather than omitted. No SDKs pointer is emitted in apis.yml, because
  there is no first-party client library to point at.