---
name: bijection-table-history
description: "Evaluate and integrate the Table History component with Bijection."
---

# Table History

Application-maintained edit history

- Package: @bijectionhq/table-history
- Category: Database & Backend
- Status: Reference
- License: Apache-2.0
- Bijection source (repository access required): https://github.com/bijectionhq/table-history/tree/5e7a19d6d99543e85c624680e22746899e449af4
- Upstream: https://github.com/convex/table-history/tree/db94c867e796d3aa18a52f9acc6efedf9ebd9ef8
- Documentation: https://docs.bijection.com/components/using
- Directory: https://bijection.com/components/table-history

## Get the source

Bijection repository access is required. Request access at https://bijection.com/contact.

```sh
git clone https://github.com/bijectionhq/table-history.git
cd table-history
git checkout 5e7a19d6d99543e85c624680e22746899e449af4
```

## Before using this component

Read the package README at the recorded revision for setup, dependencies, and API examples. Upstream documentation describes the original package and may differ from the Bijection adaptation. This is a source candidate for evaluation. Catalog inclusion does not establish npm availability or runtime qualification. Check compatibility with your SDK and deployment before adoption. External providers run their own compute.

## Integration workflow

1. Read the source README and package manifest at the recorded revision.
2. Confirm the required SDK, dependency availability, and runtime compatibility.
3. Follow the component's documented setup and configuration. Never invent an npm install command from a catalog package name.
4. Keep credentials in the project's existing secret store.
5. Follow the project's execution rules for verification and report what was actually checked.