generated: '2026-08-15'
method: searched
source: >-
  https://hub.getdbt.com/api/v1/tuva-health/*.json + https://api.github.com/repos/tuva-health/*
  + https://pypi.org/pypi/*/json
note: >-
  Tuva ships warehouse-native dbt packages (installed via dbt Hub / packages.yml),
  a Python preprocessing utility, and two OCI container images for Tuva EMPI.
  There is no hosted HTTP API client library, so these ARE the first-party
  distributed artifacts. The PyPI package named "tuva" belongs to an unrelated
  vendor (tuva.ai) and is intentionally excluded; pypi.org has no fhir-inferno,
  fhir_inferno or tuva-empi package (all 404 on 2026-08-15).
  CURRENCY FINDING: the standalone data-mart packages on dbt Hub are stale -
  readmissions last shipped 0.1.9 on 2023-04-06 and tuva_chronic_conditions sits
  at 0.0.4 - because those marts are now bundled inside the_tuva_project, which
  is current. Consumers installing the standalone packages from dbt Hub get a
  three-year-old build.
packages:
  - language: sql
    ecosystem: dbt
    registry: dbt Hub
    name: tuva-health/the_tuva_project
    version: 0.18.0
    published: '2026-05-07'
    version_source: https://hub.getdbt.com/api/v1/tuva-health/the_tuva_project.json
    published_source: https://github.com/tuva-health/tuva-core/releases/tag/v0.18.0
    release_count: 134
    url: https://hub.getdbt.com/tuva-health/the_tuva_project/latest/
    install: |
      packages:
        - package: tuva-health/the_tuva_project
          version: 0.18.0
    source: https://github.com/tuva-health/tuva-core
    license: Apache-2.0
    official: true
  - language: sql
    ecosystem: dbt
    registry: dbt Hub
    name: tuva-health/readmissions
    version: 0.1.9
    published: '2023-04-06'
    version_source: https://hub.getdbt.com/api/v1/tuva-health/readmissions.json
    published_source: https://github.com/tuva-health/readmissions/releases/tag/0.1.9
    release_count: 10
    url: https://hub.getdbt.com/tuva-health/readmissions/latest/
    install: |
      packages:
        - package: tuva-health/readmissions
    source: https://github.com/tuva-health/readmissions
    license: Apache-2.0
    official: true
    note: >-
      Stale on dbt Hub since 2023-04-06. The readmissions mart ships inside
      the_tuva_project; prefer that.
  - language: sql
    ecosystem: dbt
    registry: dbt Hub
    name: tuva-health/tuva_chronic_conditions
    version: 0.0.4
    published: null
    version_source: https://hub.getdbt.com/api/v1/tuva-health/tuva_chronic_conditions.json
    release_count: 4
    url: https://hub.getdbt.com/tuva-health/tuva_chronic_conditions/latest/
    install: |
      packages:
        - package: tuva-health/tuva_chronic_conditions
    source: https://github.com/tuva-health/tuva_cms_chronic_conditions
    official: true
    note: >-
      published is null on purpose: dbt Hub publishes no release date and the
      backing repo (tuva_cms_chronic_conditions) carries no tags or releases to
      date it from. The predecessor repo cms_chronic_conditions last tagged 0.1.8
      on 2023-04-06. Checked, nothing to record - not unchecked.
  - language: python
    ecosystem: python
    registry: github
    name: fhir-inferno
    version: 0.1.0
    published: null
    version_source: https://github.com/tuva-health/FHIR_inferno/blob/main/pyproject.toml
    url: https://github.com/tuva-health/FHIR_inferno
    install: git clone https://github.com/tuva-health/FHIR_inferno
    source: https://github.com/tuva-health/FHIR_inferno
    license: MIT
    official: true
    note: >-
      Declares version 0.1.0 in pyproject.toml but is NOT published to PyPI
      (pypi.org/pypi/fhir-inferno/json returns 404) and the repo cuts no GitHub
      releases or tags, so there is no publication date to record - published is
      null by measurement, not by omission. Last commit to main 2025-10-23.
      Distribution is git clone only; consumers cannot pin a version.
  - language: docker
    ecosystem: oci
    registry: ghcr
    name: ghcr.io/tuva-health/tuva-empi-backend
    version: v0.1.0
    published: '2025-04-24'
    version_source: https://github.com/tuva-health/tuva_empi/releases
    url: https://github.com/tuva-health/tuva_empi/pkgs/container/tuva-empi-backend
    install: docker pull ghcr.io/tuva-health/tuva-empi-backend
    source: https://github.com/tuva-health/tuva_empi
    license: Apache-2.0
    official: true
    note: >-
      Serves the Tuva EMPI API on port 8000 and also carries the migrate,
      bootstrap and matching-service commands. Version tracks the tuva_empi
      repository, whose only tagged release is v0.1.0 (2025-04-24); the VERSION
      file on main reads 0.2.0-dev.
  - language: docker
    ecosystem: oci
    registry: ghcr
    name: ghcr.io/tuva-health/tuva-empi-frontend
    version: v0.1.0
    published: '2025-04-24'
    version_source: https://github.com/tuva-health/tuva_empi/releases
    url: https://github.com/tuva-health/tuva_empi/pkgs/container/tuva-empi-frontend
    install: docker pull ghcr.io/tuva-health/tuva-empi-frontend
    source: https://github.com/tuva-health/tuva_empi
    license: Apache-2.0
    official: true
    note: NextJS review UI, listening on port 3000. Takes no parameters.
registries_checked:
  - {registry: pypi, packages: [fhir-inferno, fhir_inferno, tuva-empi], result: 404 - none published}
  - {registry: npm, result: no first-party package found}
  - {registry: 'dbt Hub', result: 3 packages under the tuva-health namespace}
  - {registry: ghcr, result: 2 images under tuva-health}