# qb-fitbit

The upstream QBCore documentation still lists **qb-fitbit**, but as of **2026-09-27** there is no
public `qb-fitbit` repository in either the `qbcore-fivem` or `qbcore-framework` GitHub
organization.

That means there is currently no official manifest, configuration file, event list or export surface
that qbcore.net can safely document as a current installable resource.

> **Do not assume an old fork is official**
> Third-party copies named `qb-fitbit` may still exist. Treat them as community resources and verify
> their owner, commit history, license, dependencies and server-side validation before deployment.

## What still exists in current QBCore

The current `qb-core` shared item list still defines a `fitbit` item. That is only an item
definition; it does not provide the old gameplay resource by itself.

The QBCore ecosystem has also historically used a `fitbit` metadata field in examples and older
resources. A metadata key remaining in a character record does not prove that an active resource is
currently consuming it.

## Why the old documentation can be misleading

An entry in the documentation navigation can outlive the repository it originally described.
Without an official source repository there is nothing current to verify for:

- `fxmanifest.lua`
- dependencies
- configuration keys
- client or server events
- exports
- database migrations
- security behavior

qbcore.net therefore does **not** invent an API surface for this resource.

## If your server already has qb-fitbit

1. Identify the exact repository or package that supplied your resource.
2. Record its commit SHA or release version.
3. Read its `fxmanifest.lua` and dependency declarations.
4. Search its source for every exported function and registered network event.
5. Check whether it still expects legacy inventory/player APIs.
6. Test it on staging before upgrading `qb-core`, inventory or metadata schemas.

If the package is abandoned, migrate the feature to a maintained health/wearable resource rather
than copying events from historical documentation.

## If you only need the item

The current shared item definition can exist without a dedicated Fitbit gameplay resource. Before
keeping it, search your own resources for references to the item name:

```bash
rg -n "fitbit" resources
```

Remove or rename it only after confirming no active resource depends on it.

## Related documentation

- [Resource references](/docs/resources)
- [Player Data and metadata](/docs/core/player-data)
- [Shared Data](/docs/core/shared)
- [Resource update conflicts](/docs/troubleshooting/resource-update-conflicts)
- [Server authority checklist](/docs/security/server-authority-checklist)

## Sources

- [QBCore documentation repository](https://github.com/qbcore-framework/qb-docs)
- [Current qbcore-fivem organization](https://github.com/qbcore-fivem)
- [Current qbcore-framework organization](https://github.com/qbcore-framework)
- [Current qb-core shared items](https://github.com/qbcore-fivem/qb-core/blob/main/shared/items.lua)

Verified **2026-09-27**. No official `qb-fitbit` repository was published in either current QBCore
organization at verification time.
