feat: add a Go SDK alongside the Python and Node.js ports (#119)

* feat: add a Go SDK alongside the Python and Node.js ports

The port carries the same features as the other two, with the surface
shaped for Go: a context on every request, errors instead of exceptions,
Options instead of keyword arguments, and a zero value that means the
default the other ports declare in their signatures.

Two pieces have no counterpart in the sibling ports, because their HTTP
clients provide them:

- a cookie jar that honours the scope FR24 sets, so a cookie stored by
  www. is not replayed to cdn./api./data-live., and a single cookie can
  be dropped to shed load-balancer stickiness without losing the login
- content decoding owned by the package (gzip, deflate, brotli), which
  is what makes the size budget enforceable before a body expands

Parity is enforced rather than promised: ports_test.go reads the Python
source and fails when the country list, the zones, the tracker config,
the flight attributes or the client methods drift apart.

* ci: run, release and label the Go port

The offline suite gates pull requests and the live FR24 suite runs with
retries, mirroring the Python and Node.js workflows. gofmt, go vet and
staticcheck stand in for flake8/mypy and eslint/tsd, and a consumer
module is built against the package so a broken public surface fails
the build.

Releases need no registry upload: for Go the tag is the release. Since
the module lives in a subdirectory, the toolchain only sees tags
carrying that prefix, so publish.yml now pushes go/vX.Y.Z alongside the
release tag, and the version check covers all three ports.

The labeler tells the Go tests apart from the package itself, which
matters because Go keeps them in the same directory where python/ and
nodejs/ keep a sibling tests/ folder.

* docs: list Go across the project docs

The per-package READMEs now describe only their own port, and the
project-wide pages list all three. The issue templates asked for a
"Python Version", which was already wrong for Node.js.

* docs: trim the Go readme to the shape of its siblings

The package readme now carries what the Python and Node.js ones do —
install, basic usage, documentation link — and nothing else. The deeper
material it held (entity constructors, client options, error handling,
TLS impersonation, the differences table) moves to docs/go.md, where the
equivalent Python and Node.js pages already live.

* docs: carry the Go badges in every readme

Each readme leads with its own workflow badge and then repeats the
project-wide block, so the Go one was missing Pypi, Npm, Downloads and
Frequency, and the other three were missing the Go reference and version.

The project-wide pages listed only some of the workflow badges: the root
readme had no Node.js one and the documentation home had neither Node.js
nor Go.

* docs: add a Node version badge and group the license with the workflows

Each registry badge now sits next to the version it needs — Pypi with
Python, Npm with Node, the Go reference with Go — and the license moves
up beside the workflow badges.

The Node floor is the engines.node of nodejs/package.json.

* fix: harden the edges a public surface exposes

Eight findings from the review on the pull request, each reproduced
before it was changed:

- CheckInfo reported an unknown field only when Go's randomised map
  iteration put it before a criterion that fails: 26 of 200 runs on the
  same input. Every criterion is now validated before any is evaluated.
- GetFlightDetails and GetHistoryData take a pointer, so nil is valid at
  compile time and panicked instead of returning an error.
- A body with data spliced after the JSON was accepted, where the Python
  and Node.js parsers reject it: Decode reads the first value only.
- Network failures did not wrap ErrFlightRadar, contradicting the
  taxonomy documented on that sentinel. They now wrap both it and the
  transport's own cause, which the retry policy still reads.
- A negative Client.Timeout skipped the deadline entirely instead of
  falling back to the default the field documents.
- New() panicked when the process had replaced http.DefaultTransport,
  which mocking libraries legitimately do.
- SleepFor panicked on the largest Jitter a Duration can hold, and could
  wrap round when adding it to the delay.
- Missing aircraft images stayed nil where the other ports default to an
  empty list, which changes both a CheckInfo comparison and the JSON.

* fix: retry a body lost mid-download, and widen two value readers

A connection dropped partway through a response was classified as
permanent, because the body is read after Do returns and so carries no
*url.Error of its own: against a server that promises 5000 bytes and
hangs up after 6, a policy asking for three attempts made one. The
Python port retries the same failure, where curl_cffi reads the body
inside the call. The read failure is now wrapped the way the transport
wraps its own.

Two readers were narrower than they read: nativeNumber covered every
numeric kind except float64, so a defined type over float64 was refused
where one over int64 worked, and getString ignored json.Number, which
this package itself produces when it decodes with UseNumber.

* fix: send every in-scope cookie, and never sleep on a bad delay

The jar collapsed same-named cookies to one, so a request to /data/...
carried the root token where FR24 had scoped a different value to that
path. RFC 6265 5.4 asks for every match, longest path first and oldest
first among equal paths, which is also what the cookie jar behind the
Python port does. get() still answers with the newest re-issue: it says
which token is current, not what to put on the wire.

A negative BaseDelay reached the overflow guard added with the last
round of fixes and came back as the longest sleep a Duration can hold —
292 years before the first retry. The zero BaseDelay that turns into NaN
once the doubling overflows landed in the same place.

* test: fold two duplicated bounds tests into the parity one

GetBounds was asserted twice with the same call and different constants,
and the "box surrounds the point" test was subsumed by the one comparing
all four values against the numbers the Python suite pins.

Its two assertions moved into the survivor rather than being dropped:
they are what catches an expected-value fixture updated the wrong way.
Reordering the fields and "fixing" the fixture to match leaves the exact
comparison passing and fails on the shape.

* fix: keep the feed's order, and close four gaps the taxonomy left open

GetFlights walked a Go map, whose iteration order is randomised, so the
same feed answered in a different order on every call where the Python
and Node.js ports keep the order FR24 sent. The keys are now read from
the body itself.

Four smaller ones, each reproduced first:

- a body of "null" unmarshalled into a nil map with no error, so every
  key read as missing instead of the caller seeing the failure
- Content-Type was matched case-sensitively, though a media type is not
- Content-Encoding split across header fields decoded only its first
  layer and left the body compressed
- cancellation during the retry backoff returned the bare context error,
  outside the taxonomy every other failure path follows

A negative flightLimit, page or limit is no longer rewritten as the
default: only zero selects it, and anything else goes to FR24 as given,
which is what the sibling ports do.

The workflow now also runs when python/FlightRadarAPI changes, since
ports_test.go reads those files to detect drift and could not see a
change that never triggered it.

* fix: make an unset field mean the default, not an empty request

SetFlightTrackerConfig copied the struct it was given without looking at
it. Go's zero value is the empty string where the Python dataclass
carries a default, so a literal {Limit: "10"} sent the feed
adsb=&air=&estimated=&faa=… — while the very same empty value was
rejected when it arrived through the values map. Unset fields now take
the default and every field is validated, so the two paths agree.

RetryPolicy read a zero MaxDelay as "no cap at all", which let a struct
literal climb to a four-minute sleep where the Python constructor caps
at thirty seconds. Zero now means the default the other ports declare,
for BaseDelay as well, so &RetryPolicy{MaxAttempts: 5} backs off exactly
like NewRetryPolicy(5). A zero Jitter still means none: a deterministic
test wants to be able to ask for that.

A cookie with Domain=localhost sent from localhost was discarded by the
guard against a bare TLD, though RFC 6265 5.3.5 allows a domain that is
the host itself.

* chore: derive the accept-encoding header and pin the CI tools

The header was written out while its comment claimed it came from the
decoder table, so dropping a decoder would have left the client asking
for an encoding it can no longer read — and the body would come back
compressed, parsed as garbage rather than failing. It is now built from
the table, with the order kept apart as the one part that is a choice.

staticcheck and govulncheck ran as @latest inside a required CI step,
the only tools in these workflows not pinned, so an upstream release
could turn the build red on a tree nobody touched. Both are pinned in
the Makefile, which the workflow now calls instead of repeating the
command.

Two comments had drifted from their code: the one on matching still
described the one-cookie-per-name behaviour removed in 56c4fdf, and
GetAirlineLogo carried an unreachable 5xx branch that read as though a
server error fell through to the alternative URL.

Author: JeanExtreme002

.github/ISSUE_TEMPLATE/bug_report.md

@@ -26,7 +26,9 @@ If applicable, add screenshots to help explain your problem.
 
 **System (please complete the following information):**
  - OS: [e.g. Windows]
- - Python Version [e.g. 1.10]
+ - SDK: [Python, Node.js or Go]
+ - Language version: [e.g. Python 3.12, Node.js 22, Go 1.26]
+ - FlightRadarAPI version: [e.g. 1.6.0]
 
 **Additional context**
 Add any other context about the problem here.

.github/ISSUE_TEMPLATE/questioning.md

@@ -29,7 +29,9 @@ If applicable, add screenshots to help explain your problem.
 If applicable, please complete the following information:
 
 1. OS: [e.g. Windows]
-2. Python Version [e.g. 1.10]
+2. SDK: [Python, Node.js or Go]
+3. Language version: [e.g. Python 3.12, Node.js 22, Go 1.26]
+4. FlightRadarAPI version: [e.g. 1.6.0]
 
 **Additional context**
 Add any other context about the problem here.

.github/dependabot.yml

@@ -23,6 +23,15 @@ updates:
       - "deps"
       - "security"
 
+  - package-ecosystem: "gomod"
+    directory: "/go"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 0
+    labels:
+      - "deps"
+      - "security"
+
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:

.github/workflows/go-package.yml

@@ -0,0 +1,91 @@
+name: Go Package
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'go/**'
+      # ports_test.go reads these to keep the three SDKs aligned, so a change
+      # there has to run this workflow or the drift goes unnoticed.
+      - 'python/FlightRadarAPI/**'
+      - '.github/workflows/go-package.yml'
+  pull_request:
+    paths:
+      - 'go/**'
+      - 'python/FlightRadarAPI/**'
+      - '.github/workflows/go-package.yml'
+  schedule:
+    - cron: '0 0 */7 * *'
+  workflow_dispatch:
+
+defaults:
+  run:
+    working-directory: ./go
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        go-version: ['1.25.x', '1.26.x']
+    steps:
+      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262  # v4
+      - name: Set up Go ${{ matrix.go-version }}
+        uses: actions/setup-go@924ae3a1cded613372ab5595356fb5720e22ba16  # v6
+        with:
+          go-version: ${{ matrix.go-version }}
+          cache-dependency-path: go/go.sum
+      - name: Download dependencies
+        run: |
+          go mod download
+          go mod verify
+      - name: Check go.mod is tidy
+        run: |
+          go mod tidy
+          git diff --exit-code -- go.mod go.sum
+      - name: Lint
+        run: make lint
+      - name: Static analysis
+        if: matrix.go-version == '1.26.x'
+        run: make lint-strict
+      - name: Offline tests (PR gate)
+        # Coverage threshold lives in the Makefile ($(COVERAGE_MIN)); raise it
+        # there and it applies here too.
+        run: make test-coverage
+      - name: Race detector
+        run: make test-race
+      - name: Integration tests (live FR24)
+        uses: nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08  # v3
+        with:
+          timeout_minutes: 10
+          max_attempts: 3
+          command: cd go && make test-integration
+        continue-on-error: ${{ github.event_name == 'push' }}
+      - name: Vulnerability scan (shipped dependencies)
+        if: matrix.go-version == '1.26.x'
+        run: make security
+      - name: Verify the package builds as a dependency
+        run: |
+          go build ./...
+          mkdir -p /tmp/consumer && cd /tmp/consumer
+          go mod init consumer
+          go mod edit -require=github.com/JeanExtreme002/FlightRadarAPI/go@v0.0.0
+          go mod edit -replace=github.com/JeanExtreme002/FlightRadarAPI/go=$GITHUB_WORKSPACE/go
+          cat > main.go <<'EOF'
+          package main
+
+          import (
+          	"fmt"
+
+          	"github.com/JeanExtreme002/FlightRadarAPI/go/flightradarapi"
+          )
+
+          func main() {
+          	client := flightradarapi.New()
+          	fmt.Println("Install OK:", len(client.GetZones()), "zones")
+          }
+          EOF
+          go mod tidy
+          go run .

.github/workflows/labeler.yml

@@ -34,26 +34,46 @@ jobs:
             const paths = files.map((f) => f.filename);
             core.info(`Changed files (${paths.length}):\n  ` + paths.join("\n  "));
 
+            const goPackage = "go/flightradarapi/";
+
+            // Go keeps its tests inside the package, where python/ and nodejs/
+            // keep them in a sibling tests/ directory. Told apart here so a
+            // test-only PR gets "tests" and not "api".
+            const isGoTest = (f) =>
+              f.startsWith(goPackage) &&
+              (/_test\.go$/.test(f) || f.startsWith(goPackage + "testdata/"));
+
             const isCore = (f) =>
               f === "python/FlightRadarAPI/core.py" ||
               f === "python/FlightRadarAPI/request.py" ||
               f === "nodejs/FlightRadarAPI/core.js" ||
-              f === "nodejs/FlightRadarAPI/request.js";
+              f === "nodejs/FlightRadarAPI/request.js" ||
+              f === "go/flightradarapi/core.go" ||
+              f === "go/flightradarapi/request.go" ||
+              // The Go port owns the cookie jar its siblings get from their
+              // HTTP client, so it belongs to the same layer as request.go.
+              f === "go/flightradarapi/cookies.go";
 
             const isEntities = (f) =>
-              /^(python|nodejs)\/FlightRadarAPI\/entities\//.test(f);
+              /^(python|nodejs)\/FlightRadarAPI\/entities\//.test(f) ||
+              // One package per directory in Go: the entities are files.
+              /^go\/flightradarapi\/(entity|airport|flight)\.go$/.test(f);
 
             const isInPackage = (f) =>
-              /^(python|nodejs)\/FlightRadarAPI\//.test(f);
+              /^(python|nodejs)\/FlightRadarAPI\//.test(f) ||
+              (f.startsWith(goPackage) && !isGoTest(f));
 
-            const isTests = (f) => /^(python|nodejs)\/tests\//.test(f);
+            const isTests = (f) =>
+              /^(python|nodejs)\/tests\//.test(f) || isGoTest(f);
 
             const isCi = (f) => f.startsWith(".github/");
 
             const isDeps = (f) =>
               f === "python/pyproject.toml" ||
               f === "nodejs/package.json" ||
-              f === "nodejs/package-lock.json";
+              f === "nodejs/package-lock.json" ||
+              f === "go/go.mod" ||
+              f === "go/go.sum";
 
             const isBuild = (f) =>
               /(^|\/)Makefile$/.test(f) ||
@@ -69,6 +89,7 @@ jobs:
 
             const isPython = (f) => f.startsWith("python/");
             const isNode = (f) => f.startsWith("nodejs/");
+            const isGo = (f) => f.startsWith("go/");
 
             const desired = new Set();
 
@@ -83,6 +104,7 @@ jobs:
               if (isDocs(f)) desired.add("docs");
               if (isPython(f)) desired.add("pkg:python");
               if (isNode(f)) desired.add("pkg:node");
+              if (isGo(f)) desired.add("pkg:go");
             }
 
             // Dependabot PRs (we only enable Dependabot for security advisories).
@@ -119,7 +141,7 @@ jobs:
               "api:core", "api:entities", "api", "tests",
               "ci", "build", "feature", "docs",
               "revert", "performance", "bug",
-              "deps", "security", "pkg:python", "pkg:node",
+              "deps", "security", "pkg:python", "pkg:node", "pkg:go",
             ]);
 
             const { data: currentLabels } = await github.rest.issues.listLabelsOnIssue({

.github/workflows/publish.yml

@@ -32,14 +32,19 @@ jobs:
         run: |
           py_version=$(grep -oP '__version__\s*=\s*"\K[^"]+' python/FlightRadarAPI/__init__.py)
           npm_version=$(node -p "require('./nodejs/package.json').version")
+          go_version=$(grep -oP 'const Version = "\K[^"]+' go/flightradarapi/doc.go)
           echo "python=$py_version" >> "$GITHUB_OUTPUT"
           echo "npm=$npm_version" >> "$GITHUB_OUTPUT"
-          echo "Python: $py_version | npm: $npm_version"
+          echo "go=$go_version" >> "$GITHUB_OUTPUT"
+          echo "Python: $py_version | npm: $npm_version | Go: $go_version"
 
       - name: Check versions are in sync
+        # The Go module is published by the release tag itself, so it has no
+        # upload job below — only this check keeps its version honest.
         run: |
-          if [ "${{ steps.versions.outputs.python }}" != "${{ steps.versions.outputs.npm }}" ]; then
-            echo "::error::Version mismatch: python=${{ steps.versions.outputs.python }} npm=${{ steps.versions.outputs.npm }}"
+          if [ "${{ steps.versions.outputs.python }}" != "${{ steps.versions.outputs.npm }}" ] \
+            || [ "${{ steps.versions.outputs.python }}" != "${{ steps.versions.outputs.go }}" ]; then
+            echo "::error::Version mismatch: python=${{ steps.versions.outputs.python }} npm=${{ steps.versions.outputs.npm }} go=${{ steps.versions.outputs.go }}"
             exit 1
           fi
 
@@ -53,6 +58,33 @@ jobs:
             exit 1
           fi
 
+  tag-go-module:
+    needs: verify-versions
+    if: github.event_name == 'release'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write  # Required to push the module tag
+    steps:
+      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262  # v4
+        with:
+          fetch-depth: 0
+
+      # A module in a subdirectory is released by a tag carrying that prefix, so
+      # `go get .../go@latest` sees nothing without this.
+      - name: Tag the Go module
+        env:
+          TAG: ${{ github.event.release.tag_name }}
+        run: |
+          version="${TAG#v}"
+          module_tag="go/v${version}"
+          if git rev-parse -q --verify "refs/tags/${module_tag}" >/dev/null; then
+            echo "${module_tag} already exists"
+            exit 0
+          fi
+          git tag "${module_tag}" "${TAG}"
+          git push origin "${module_tag}"
+          echo "Pushed ${module_tag}"
+
   publish-pypi:
     needs: verify-versions
     if: github.event_name == 'release' || inputs.target == 'both' || inputs.target == 'pypi'

.gitignore

@@ -20,6 +20,9 @@ coverage.xml
 # Node.js
 node_modules/
 
+# Go
+coverage.out
+
 # Version managers (local dev only)
 .tool-versions
 .python-version

CONTRIBUTING.md

@@ -1,8 +1,8 @@
 # Contributing to FlightRadarAPI
 
-Thanks for your interest. This repo ships two SDKs in parallel — Python and
-Node.js — that must stay behavior-aligned, so most non-trivial changes touch
-both sides.
+Thanks for your interest. This repo ships three SDKs in parallel — Python,
+Node.js and Go — that must stay behavior-aligned, so most non-trivial changes
+touch every side.
 
 ## Development setup
 
@@ -25,25 +25,37 @@ make lint               # eslint
 make test-types         # tsd
 ```
 
-## Keeping Python and Node aligned
+### Go
+```bash
+cd go
+make deps
+make test               # offline suite (the PR gate)
+make test-integration   # live FR24 suite
+make lint               # gofmt + go vet
+make lint-strict        # adds staticcheck
+```
 
-When you change behavior, change it in both SDKs in the same PR unless there
+## Keeping the SDKs aligned
+
+When you change behavior, change it in every SDK in the same PR unless there
 is a documented reason not to. Common targets that must stay in sync:
 
 - Error taxonomy (`AirportNotFoundError`, `LoginError`, `CloudflareError`,
   `FlightRadarError`).
 - `RetryPolicy` semantics (which exceptions are transient, backoff math).
 - Cloudflare detection rules.
-- The public surface — `FlightRadar24API` methods, the `Countries` enum,
-  `FlightTrackerConfig` fields, and the `Entity` / `Airport` / `Flight`
-  attributes consumers depend on.
+- The public surface — `FlightRadar24API` methods (`Client` in Go), the
+  `Countries` enum (`Country` constants in Go), `FlightTrackerConfig` fields,
+  and the `Entity` / `Airport` / `Flight` attributes consumers depend on.
+  `docs/go.md` documents where the Go surface deliberately differs.
 
 ## Style
 
 - Python: flake8 + mypy.
 - Node: eslint + tsd.
+- Go: gofmt + go vet + staticcheck.
 - Comments must explain **why**, not **what**. The codebase has a few exemplars in
-  `request.py`/`request.js` — read those before adding new comments.
+  `request.py`/`request.js`/`request.go` — read those before adding new comments.
 
 ## Commits and PRs
 
@@ -53,10 +65,17 @@ is a documented reason not to. Common targets that must stay in sync:
 
 ## Releases
 
-Before publishing a new release, the version **must be bumped**. The version lives in two places:
+Before publishing a new release, the version **must be bumped**. The version lives in three places:
 
 - `python/FlightRadarAPI/__init__.py` (`__version__`)
 - `nodejs/package.json` (`version`)
+- `go/flightradarapi/doc.go` (`Version`)
+
+The Go module needs no registry upload — the tag *is* the release. Because it
+lives in a subdirectory, the Go toolchain only sees tags carrying that prefix,
+so the `tag-go-module` job of `publish.yml` pushes `go/v1.6.0` alongside the
+release tag. Nothing to do by hand; if that job is skipped, `go get
+.../go@latest` finds no release and callers fall back to a pseudo-version.
 
 ## Reporting bugs and asking questions
 

README.md

@@ -1,15 +1,20 @@
 # FlightRadarAPI
-Unofficial SDK for [FlightRadar24](https://www.flightradar24.com/) for Python 3 and Node.js.
+Unofficial SDK for [FlightRadar24](https://www.flightradar24.com/) for Python 3, Node.js and Go.
 
 This SDK should only be used for your own educational purposes. If you are interested in accessing Flightradar24 data commercially, please contact business@fr24.com. See more information at [Flightradar24's terms and conditions](https://www.flightradar24.com/terms-and-conditions).
 
 **Official FR24 API**: https://fr24api.flightradar24.com/
 
 [![Python Package](https://github.com/JeanExtreme002/FlightRadarAPI/workflows/Python%20Package/badge.svg)](https://github.com/JeanExtreme002/FlightRadarAPI/actions)
-[![Pypi](https://img.shields.io/pypi/v/FlightRadarAPI?logo=pypi)](https://pypi.org/project/FlightRadarAPI/)
+[![Node.js Package](https://github.com/JeanExtreme002/FlightRadarAPI/actions/workflows/node-package.yml/badge.svg)](https://github.com/JeanExtreme002/FlightRadarAPI/actions)
+[![Go Package](https://github.com/JeanExtreme002/FlightRadarAPI/actions/workflows/go-package.yml/badge.svg)](https://github.com/JeanExtreme002/FlightRadarAPI/actions)
 [![License](https://img.shields.io/pypi/l/FlightRadarAPI)](https://github.com/JeanExtreme002/FlightRadarAPI)
+[![Pypi](https://img.shields.io/pypi/v/FlightRadarAPI?logo=pypi)](https://pypi.org/project/FlightRadarAPI/)
 [![Python Version](https://img.shields.io/badge/python-3.10+-8A2BE2)](https://pypi.org/project/FlightRadarAPI/)
 [![Npm](https://img.shields.io/npm/v/flightradarapi?logo=npm&color=red)](https://www.npmjs.com/package/flightradarapi)
+[![Node Version](https://img.shields.io/badge/node-18.17+-339933)](https://www.npmjs.com/package/flightradarapi)
+[![Go Reference](https://pkg.go.dev/badge/github.com/JeanExtreme002/FlightRadarAPI/go.svg)](https://pkg.go.dev/github.com/JeanExtreme002/FlightRadarAPI/go/flightradarapi)
+[![Go Version](https://img.shields.io/badge/go-1.25+-00ADD8)](https://go.dev/dl/)
 [![Downloads](https://static.pepy.tech/personalized-badge/flightradarapi?period=total&units=international_system&left_color=grey&right_color=orange&left_text=downloads)](https://pypi.org/project/FlightRadarAPI/)
 [![Frequency](https://img.shields.io/pypi/dm/flightradarapi?style=flat&label=frequency)](https://pypi.org/project/FlightRadarAPI/)
 
@@ -24,8 +29,13 @@ pip install FlightRadarAPI
 npm install flightradarapi
 ```
 
+**For Go:**
+```
+go get github.com/JeanExtreme002/FlightRadarAPI/go@latest
+```
+
 ## Documentation
-Explore the docs of FlightRadarAPI package, for Python or NodeJS, through [FlightRadarAPI Documentation](https://JeanExtreme002.github.io/FlightRadarAPI/) page.
+Explore the docs of FlightRadarAPI package, for Python, NodeJS or Go, through [FlightRadarAPI Documentation](https://JeanExtreme002.github.io/FlightRadarAPI/) page.
 
 ## Project resources
 **Contributing**: [`CONTRIBUTING.md`](CONTRIBUTING.md)<br>