generated: '2026-08-25'
method: searched
source: >-
  https://pypi.org/pypi/mindfoundry-optaas-client/json ; https://api.github.com/orgs/MindFoundry ;
  registry probes of npm, RubyGems, crates.io, NuGet and Maven Central
note: >-
  One first-party package survives on a public registry: the OPTaaS Python client, published by
  Mind Foundry Ltd (optaas@mindfoundry.ai). It is an SDK for a service that is no longer running —
  the OPTaaS hosts named in its own documentation (optaas.mindfoundry.ai, demo.optimize.mindfoundry.ai)
  are NXDOMAIN, the marketing page https://mindfoundry.ai/optaas 404s, and the MindFoundry GitHub
  organisation now reports public_repos: 0 with both optaas-python-client and optaas-r-client
  returning 404. The package remains installable and is recorded here as published-but-abandoned.
packages:
- name: mindfoundry-optaas-client
  registry: pypi
  url: https://pypi.org/project/mindfoundry-optaas-client/
  language: python
  official: true
  official_evidence: >-
    PyPI author "Mind Foundry Ltd" <optaas@mindfoundry.ai>; project Homepage
    https://mindfoundry.ai/optaas
  license: MIT License
  summary: 'Mind Foundry Optimization as a Service: Python Client'
  version: 1.4.4
  published: '2024-01-26'
  release_count: 22
  first_release: '2018-07-23'
  status: abandoned
  status_note: >-
    Latest release 1.4.4 (2024-01-26). The API it wraps is retired: the OPTaaS server hosts
    resolve NXDOMAIN as of 2026-08-25, so the client cannot be pointed at a live endpoint.
- name: optaas-r-client
  registry: github
  url: https://github.com/MindFoundry/optaas-r-client
  language: r
  official: true
  official_evidence: >-
    Referenced as "Mind Foundry OPTaaS R Client" under the MindFoundry GitHub organisation and on
    rdrr.io (version 1.3.5); never published to CRAN.
  version: null
  published: null
  status: removed
  status_note: >-
    Repository returns HTTP 404 as of 2026-08-25 and the MindFoundry organisation reports
    public_repos: 0. Version and date recorded as null because no registry or repository
    metadata endpoint answers — checked, nothing to record.
registries_checked:
- registry: pypi
  result: 1 first-party package (mindfoundry-optaas-client)
- registry: npm
  result: no first-party package (optaas, mindfoundry, @mindfoundry/* all 404)
- registry: rubygems
  result: none
- registry: crates.io
  result: none
- registry: nuget
  result: none
- registry: maven-central
  result: none
- registry: cran
  result: none (R client was GitHub-only)
pointer_note: >-
  apis.yml carries a `Packages` pointer at this file but deliberately does NOT carry the
  `SDKs` pointer the sdk_count check reads. Mind Foundry publishes no API for an SDK to
  wrap: the one registry-published client targets the retired OPTaaS service. Emitting
  `SDKs` would credit a developer-experience surface that does not exist.
summary:
  package_count: 2
  official_count: 2
  live_count: 0
  registry_published_count: 1