generated: '2026-08-04'
method: searched
source: public package-registry and GitHub-organization search
packages: []
result: none
note: >-
  FLYR publishes no first-party client libraries. Recorded so a later run does not re-walk the same
  registries. No `Packages` or `SDKs` pointer is wired in apis.yml — there is nothing to point at.
registries_checked:
- registry: npm
  result: none
  note: >-
    The npm package `flyr` exists but is unrelated — "a library for extracting the thermal data from FLIR
    thermograms" (bitbucket.org/nimmerwoner/flyr-rs). `@flyr/sdk` and `flyr-sdk` are both 404.
- registry: pypi
  result: none
  note: >-
    The PyPI package `flyr` is the same unrelated FLIR thermal-image parser by Arthur Nieuwland.
    `flyr-sdk` is 404.
- registry: maven-central
  result: none
- registry: nuget
  result: none
- registry: pkg.go.dev
  result: none
- registry: rubygems
  result: none
- registry: packagist
  result: none
- registry: crates.io
  result: none
github_organization:
  url: https://github.com/FlyrInc
  public_repos: 15
  first_party_repos:
  - name: homebrew-tools
    url: https://github.com/FlyrInc/homebrew-tools
    note: >-
      A Homebrew tap carrying a single formula for structurizr-site-generatr (an architecture-diagram
      site generator FLYR forked). Internal tooling, not an API client — no `CLI` artifact was written.
  - name: azure-script
    url: https://github.com/FlyrInc/azure-script
    note: Shell scripts for script URIs; internal infrastructure tooling.
  - name: flyr-blog-examples
    url: https://github.com/FlyrInc/flyr-blog-examples
    note: Sample code accompanying FLYR engineering blog posts.
  note: >-
    The remaining 12 repositories are forks of third-party projects (Apache Beam, Apache Airflow,
    sentry-python, alembic_utils, Multicorn, bigquery_fdw, python-json-logger, semantic-release,
    structurizr java, cypress-skip-test, terraform-provider-huaweicloudstack). None is an API SDK.