open-index/open-npm huggingface dataset:
npm package: @proof-of-commitment/sdk
Description: TypeScript SDK for the Proof-of-Commitment staking and governance protocol
Latest version: 0.1.0

# Proof-of-Commitment SDK

A lightweight TypeScript wrapper around the Proof-of-Commitment staking and governance contracts. The SDK is designed to be framework-agnostic and works with any `viem` `PublicClient`/`WalletClient` pair.

## Installation

```bash
npm install @proof-of-commitment/sdk viem
```

## Quick Start

```ts
import { createPublicClient, createWalletClient, http } from 'viem';
import { lisk } from 'viem/chains';
import { ProofOfCommitmentSDK } from '@proof-of-commitment/sdk';

const publicClient = createPublicClient({ chain: lisk, transport: http() });
const walletClient = createWalletClient({ chain: lisk, transport: http(), account });

const sdk = new ProofOfCommitmentSDK({ publicClient, walletClient });

const stats = await sdk.staking.getProtocolStats();
await sdk.staking.stake({ amount: '100', lockDays: 30 });
const proposals = await sdk.governance.listProposals();
```

## Packages

- `staking` – approvals, staking flows, rewards, and protocol stats
- `governance` – proposal lifecycle helpers and voting power utilities
- `analytics` – opinionated aggregations (user overview + protocol overview)
- `nft` – helpers for NFT-backed stake data

## Building Locally

```bash
cd sdk
npm install
npm run build
```

This produces ESM + CJS bundles with type declarations inside `dist/`.
npm package: @proof-ui/a11y-plugin
Description: Uses [`axe`](https://www.deque.com/axe/) to scan each story against accessibility rules. Violatons are printed to the console, and included in any reports.
Latest version: 0.3.6

# @proof-ui/a11y-plugin

Uses [`axe`](https://www.deque.com/axe/) to scan each story against accessibility rules. Violatons are printed to the console, and included in any reports.

## Installation

```bash
yarn add -D @proof-ui/a11y-plugin
```

## Usage

```javascript
// proof.config.js
import A11yPlugin from '@proof-ui/a11y-plugin';

export default {
  plugins: [
    new A11yPlugin({
      // Configuration
    })
  ]
};
```

```bash
# Command Line Usage
proof --a11y
```

## Options

You can configure the A11yPlugin through some options in it's constructor:

| Property | Description                                                  | Type                                                                                          | Default   |
| -------- | ------------------------------------------------------------ | --------------------------------------------------------------------------------------------- | --------- |
| `config` | The AXE rule configuration to use when testing a story       | `object` (see [`axe.Spec`](https://github.com/dequelabs/axe-core/blob/develop/axe.d.ts#L118)) |           |
| `root`   | A selector for the root context when checking for violations | `string`                                                                                      | `'#root'` |

## Related

- [add-all-plugin](./add-all)
- [skip-tests-plugin](./skip-tests)
npm package: @proof-ui/add-all-plugin
Description: A plugin to add an empty test for each untested storybook story.
Latest version: 0.3.6

# @proof-ui/add-all-plugin

A plugin to add an empty test for each untested storybook story.

Especially powerful when combined with the [accessibility-plugin](./accessibility) or the [applitools-plugin](./applitools) to get full coverage of each story, even if there are no integration tests written already.

## Installation

```bash
yarn add -D @proof-ui/add-all-plugin
```

## Usage

```javascript
// proof.config.js
import AddAllPlugin from '@proof-ui/add-all-plugin';

export default {
  plugins: [new AddAllPlugin()]
};
```

```bash
# Command Line Usage
proof --add-all
```

## Options

You can configure the applitools-plugin through some options in it's constructor:

| Property | Description                                     | Type                                    |
| -------- | ----------------------------------------------- | --------------------------------------- |
| `filter` | A function to filter out which tests are added. | `function` - `(kind, story) => boolean` |

### Example

To add all stories except ones called `skip-me`

```javascript
import AddAllPlugin from '@proff/add-all-plugin';

new AddAllPlugin({
  filter(kind, story) {
    return story !== 'skip-me';
  }
});
```

## Related

- [accessibility-plugin](./accessibility)
- [applitools-plugin](./applitools)
npm package: @proof-ui/babel-plugin
Description: A plugin to enable babel as a test preprocessor, allowing the use of ES6/ESNext features while authoring. The default configuration uses `@babel/preset-env`
Latest version: 0.3.6

# @proof-ui/babel-plugin

A plugin to enable babel as a test preprocessor, allowing the use of ES6/ESNext features while authoring.
The default configuration uses `@babel/preset-env`

## Installation

```bash
yarn add -D @proof-ui/babel-plugin
```

## Usage

```javascript
// proof.config.js
import BabelPlugin from '@proof-ui/babel-plugin';

export default {
  plugins: [
    new BabelPlugin({
      // Optional Configuration
    })
  ]
};
```

## Options

You can configure the babel-plugin through some options in it's constructor:

| Property | Description                                                                         | Type     | Default |
| -------- | ----------------------------------------------------------------------------------- | -------- | ------- |
| `config` | A [`babel`](https://babeljs.io/) configuration object to use when transpiling tests | `object` |         |

### Example

To enable typescript support in your tests

```javascript
import BabelPlugin from '@proof-ui/babel-plugin';

new BabelPlugin({
  config: {
    extensions: ['.js', '.jsx', '.ts', '.tsx'],
    presets: ['@babel/preset-env', '@babel/preset-typescript']
  }
});
```
npm package: @proof-ui/config
Description: The majority of the configuration for `proof` is set through the `proof.config.js` file in the root of your project.
Latest version: 0.3.6

# Configuration

The majority of the configuration for `proof` is set through the `proof.config.js` file in the root of your project.

# Options

|     name     |   type   |                                       description                                        | 
| ------------ | -------- | ---------------------------------------------------------------------------------------- | 
| plugins      | `array`  | An optional array of plugins to include in the *proof* instance. See [plugins](https://intuit.github.io/proof/#/./plugins/README) for more details |                                                 |
| url          | `string` | The default storybook URL to test against | 
| logLevel     | `info`, `debug`, `trace`, `stupid` | The default log-level to use. Any CLI option will override this | 
| testMath     | `glob`   | A glob to use to look for tests. Defaults to `__automation__/**/*.test.js` | 
| gridOptions  | `object<grid, object>` | A set of properties to include for *any* session created on that grid type | 
| waitForRoot  | `number` | The number of milliseconds to wait for storybook to load. Defaults to 1000ms. | 


## gridOptions

Allows you to pass in options to set on each grid type when creating a browser session. This is a global option that applies to every session.

**Example**

```
{
  gridOptions: {
    remote: {
      url: 'sauce.proof.com',
      apiKey: 'foo-bar'
    }
  }
}
```

This will set the remote grid to use `sauce.proof.com` and the API key `foo-bar`. *Note* these options will only apply if you're running the tests under this grid type. If running proofs locally (using the local-grid), these options won't be added.
npm package: @proof-ui/console-plugin
Description: A plugin that logs test results to the console.
Latest version: 0.3.6

# @proof-ui/console-plugin

A plugin that logs test results to the console.

## Installation

```bash
yarn add -D @proof-ui/console-plugin
```

## Usage

```javascript
// proof.config.js
import ConsolePlugin from '@proof-ui/console-plugin';

export default {
  plugins: [new ConsolePlugin()]
};
```
npm package: @proof-ui/junit-plugin
Description: A plugin that outputs test results in the JUnit XML format.
Latest version: 0.3.6

# @proof-ui/junit-plugin

A plugin that outputs test results in the JUnit XML format.

## Installation

```bash
yarn add -D @proof-ui/junit-plugin
```

## Usage

```javascript
// proof.config.js
import JUnitPlugin from '@proof-ui/junit-plugin';

export default {
  plugins: [
    new JUnitPlugin({
      // Optional Configuration
    })
  ]
};
```

## Options

You can configure the junit-plugin through some options in it's constructor:

| Property     | Description                                                                              | Type     | Default             |
| ------------ | ---------------------------------------------------------------------------------------- | -------- | ------------------- |
| `reportPath` | The filePath to save the junit report to                                                 | `string` | `./proof-junit.xml` |
| `contextDir` | The path to the root of the testing file tree. Use in the report for relative file paths | `string` | `__automation__`    |
npm package: @proof-ui/skip-tests-plugin
Description: A plugin that adds the option to skip the _actual_ test execution, but preserve the before and after side-effects of a test. This is most widely used in conjunction with the [accessibility-plugin](./accessibility) or [applitools-plugin](./applitools) to l
Latest version: 0.3.6

# @proof-ui/skip-tests-plugin

A plugin that adds the option to skip the _actual_ test execution, but preserve the before and after side-effects of a test. This is most widely used in conjunction with the [accessibility-plugin](./accessibility) or [applitools-plugin](./applitools) to limit the scope of each test run.

## Installation

```bash
yarn add -D @proof-ui/skip-tests-plugin
```

## Usage

```javascript
// proof.config.js
import SkipTestsPlugin from '@proof-ui/skip-tests-plugin';

export default {
  plugins: [new SkipTestsPlugin()]
};
```

```bash
# Command Line Usage
proof --skip-tests
```
npm package: @proof-ui/test
Description: Writing a test using proof is very similar to how you write your stories. Typically you'd start with:
Latest version: 0.3.6

# @proof-ui/test

Writing a test using proof is very similar to how you write your stories. Typically you'd start with:

```
import { proofsOf } from '@proof-ui/test';

const proofs = proofsOf('Components|Button');
```

Look familiar? Just like when you write your stories, you can now write a *proof* for that story to verify everything is working as expected.

While *most* of your testing will probably occur at the unit-test using [react-testing-library](https://github.com/testing-library/react-testing-library) or similar -- there's no substitution for grabbing screenshots and running some testing in the browser (especially when you're responsible for supporting some of the more annoying browsers).

# Writing a test

Adding a *proof* is very similar to adding a story. In the callback function, instead of returning a `react` component, you're given a `browser` object to interact with the page.

```
import { proofsOf } from '@proof-ui/test';

const proofs = proofsOf('Components|Button');

proofs.add('Simple', ({ browser }) => {});
```

# API

The test callback function is passed the following:


| **name** | **type** |
| -------- | --------------------------------------- |
| browser  | A `webdriverio` [browser](http://v4.webdriver.io/api.html) |
| story    | `string` |
| kind     | `string` |

# Alternative API

To enable finer control of testing, you can also use the generic version of the test api:

```
import test from '@proof-ui/test';

test({ kind: 'Components|Button', story: 'Simple' }, ({ browser }) => {});
```

The `test` api accepts a *filter* for what stories to run the test on. It can filter on both the `kind` or `story` name -- using the same callback API as the `proofsOf` version.

If no `story` is provided, *all* stories under that kind are executed. Similarly, if neither a `story` or `kind` are provided, the test runs against *every* story in your storybook.
npm package: @proofai/mcp-server
Description: ProofAI MCP Server — AI compliance tools for Claude Code
Author: HIRAM
Latest version: 1.0.1

# @proofai/mcp-server

MCP Server for ProofAI — plug AI compliance into Claude Code.

## Install

```bash
npm install -g @proofai/mcp-server
```

## Configure Claude Code

Add to `~/.claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "proofai": {
      "command": "proofai-mcp",
      "env": {
        "PROOFAI_API_KEY": "pk_live_xxx",
        "PROOFAI_ANON_KEY": "your-supabase-anon-key"
      }
    }
  }
}
```

## Tools

### `proofai_certify`
Certify an AI decision with cryptographic proof. Full pipeline in one call.

```
> Use proofai_certify to certify my analysis of this contract
```

### `proofai_log`
Log an AI decision that already happened (prompt + response you provide).

```
> Use proofai_log to record this decision with prompt "..." and response "..."
```

### `proofai_verify`
Verify a bundle's integrity and blockchain anchoring.

```
> Use proofai_verify to check bundle bnd_8019b37a7f44_1774735436195
```

### `proofai_polygonscan`
Get the Polygonscan URL for independent verification.

```
> Use proofai_polygonscan for tx 0xbbf92ceb6354a066...
```

### `proofai_monitor`
Get AI compliance monitoring stats (EU AI Act Article 72).

```
> Use proofai_monitor to check compliance status
```

## Why MCP?

Developers use Claude Code, not web dashboards. This MCP server brings AI compliance directly into the coding workflow:

- Every AI decision can be certified without leaving the terminal
- Verification is one tool call away
- Monitoring happens alongside development
- No context switching between coding and compliance
npm package: @proofcodec/geoip
Description: GeoIP lookup in 265 KB — drop-in replacement for geoip-lite. Uses proof-carrying compression to shrink DB-IP Lite from 68 MB to a single npm package.
Author: ProofCodec
Latest version: 0.1.0

# @proofcodec/geoip

GeoIP lookup in 265 KB — drop-in replacement for [geoip-lite](https://www.npmjs.com/package/geoip-lite).

Uses [proof-carrying compression](https://github.com/ProofCodec) to shrink DB-IP Lite from 68 MB to a single npm package. Zero dependencies, works in Node.js, browsers, and edge runtimes.

## Install

```bash
npm install @proofcodec/geoip
```

## Usage

```js
import geoip from '@proofcodec/geoip';

const geo = geoip.lookup('8.8.8.8');
// {
//   range: [134744064, 134744319],
//   country: 'US',
//   region: '',
//   eu: '0',
//   timezone: '',
//   city: '',
//   ll: [0, 0],
//   metro: 0,
//   area: 0
// }
```

Returns `null` if the IP is not found or invalid.

## API

### `geoip.lookup(ip)`

Look up geolocation for an IPv4 address. Returns an object matching the [geoip-lite](https://www.npmjs.com/package/geoip-lite) shape, or `null`.

### `geoip.pretty(num)`

Convert a numeric IP to dotted-quad string.

## Why this exists

| | geoip-lite | @proofcodec/geoip |
|---|---|---|
| Install size | 110 MB | **265 KB** |
| License key required | Yes (MaxMind) | **No** |
| Edge runtime support | No | **Yes** |
| Startup time | 200ms+ | **<1ms** |
| Data source | MaxMind GeoLite2 | DB-IP Lite |

## Edge runtimes

Works on Cloudflare Workers, Vercel Edge, Deno Deploy, and any runtime that supports ESM — no `fs` dependency, no native modules, no postinstall scripts.

## Data source

IP geolocation data by [DB-IP](https://db-ip.com), licensed under [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/).

When displaying geolocation results to users, please include attribution:

```html
<a href="https://db-ip.com">IP Geolocation by DB-IP</a>
```

## How it works

A decision tree classifies each /24 IP block by country based on prefix features. A sparse correction table fixes the few blocks where the tree prediction is wrong. Together, tree + corrections achieve 100% accuracy with ~300x compression vs Huffman-optimal encoding.

The compressed format is verified by [proofcodec-verify](https://github.com/ProofCodec/proofcodec-verify).

## License

MIT. See [LICENSE](LICENSE) for details.

IP data: CC-BY-4.0 (DB-IP Lite). See [NOTICE](NOTICE) for attribution requirements.
npm package: @proofdict/domain
Description: Proofdict's domain.
Author: azu
Latest version: 3.1.0

# @proofdict/domain

Proofdict&#39;s domain.

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @proofdict/domain

## Usage

- [ ] Write usage instructions

## Changelog

See [Releases page](https://github.com/proofdict/proofdict/releases).

## Running tests

Install devDependencies and Run `npm test`:

    npm i -d && npm test

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/proofdict/proofdict/issues).

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu
npm package: @proofdict/migrate
Description: Migration tool for proofdict.
Author: azu
Latest version: 3.1.0

# @proofdict/migrate

Migration tool for proofdict.

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @proofdict/migrate

## Usage

    Usage
      $ npx @proofdict/migrate "proof-dictionary/**/*.yaml" [options]

    Options:
      --script migration script name 
    Scripts:
      - noun-to-allows

    Examples
      $ npx @proofdict/migrate "proof-dictionary/**/*.yml" --script noun-to-allows

## Changelog

See [Releases page](https://github.com/proofdict/proofdict/releases).

## Running tests

Install devDependencies and Run `npm test`:

    npm i -d && npm test

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/proofdict/proofdict/issues).

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu
npm package: @proofdict/prh-to-proofdict
Description: Migration tool that convert prh.yml to proof-dictionary.
Author: azu
Latest version: 3.1.0

# @proofdict/prh-to-proofdict

Migration tool that convert prh.yml to proof-dictionary.

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @proofdict/prh-to-proofdict
    # or
    npx @proofdict/prh-to-proofdict

## Usage

    Usage
      $ prh-to-proofdict <input>
 
    Options
      --outDir -o output directory
      --defaultTag  add tags to dictionary
 
    Examples
      $ prh-to-proofdict ./prh.yml --outDir ./_data/proofdict/

## Changelog

See [Releases page](https://github.com/proofdict/proofdict/releases).

## Running tests

Install devDependencies and Run `npm test`:

    npm test

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/proofdict/proofdict/issues).

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu
npm package: @proofdict/tester
Description: Test tool using proofdict.
Author: azu
Latest version: 3.1.0

# @proofdict/tester

Test tool using proofdict.

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @proofdict/tester

## Usage

```ts
const proofdict = require("./fixtures/proofdict.json");
const tester = new ProofdictTester(proofdict);
const text = "Workaound is typo.";
return tester.match(text).then(result => {
    assert.strictEqual(result.details.length, 1);
    const [detail] = result.details;
    assert.strictEqual(detail.actual, "Workaound");
    assert.strictEqual(detail.expected, "Workaround");
    assert.strictEqual(detail.matchStartIndex, 0);
    assert.strictEqual(detail.matchEndIndex, 9);
    assert.strictEqual(text.slice(detail.matchStartIndex, detail.matchEndIndex), "Workaound");
});

```

### API

```ts
import { Diff } from "prh";
export interface Proofdict {
    expected: string;
    patterns: string[];
    description: string;
    id?: string;
    specs?: ProofdictSpec[];
    tags: string[];
}
export interface ProofdictSpec {
    from: string;
    to: string;
}
export interface ProofdictTesterResultDetail {
    description?: string;
    matchStartIndex: number;
    matchEndIndex: number;
    actual: string;
    expected: string;
}
export interface ProofdictTesterResult {
    output: string;
    details: ProofdictTesterResultDetail[];
    diffs: Diff[];
}
export declare class ProofdictTester {
    constructor(proofdictData: Proofdict[]);
    replace(text: string): Promise<string>;
    match(text: string): Promise<ProofdictTesterResult>;
}
```

## Changelog

See [Releases page](https://github.com/proofdict/proofdict/releases).

## Running tests

Install devDependencies and Run `npm test`:

    npm i -d && npm test

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/proofdict/proofdict/issues).

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu
npm package: @proofdict/tester-cli
Description: A CLI for @proofdict/tester.
Author: azu
Latest version: 3.1.0

# @proofdict/tester-cli

A CLI for @proofdict/tester.

This tools validate proof-style dictionary.

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @proofdict/tester-cli

## Usage

    Usage
      $ proofdict-tester [path|glob]

    Examples
      $ proofdict-tester "dict/*.yml"


## Changelog

See [Releases page](https://github.com/proofdict/proofdict/releases).

## Running tests

Install devDependencies and Run `npm test`:

    npm i -d && npm test

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/proofdict/proofdict/issues).

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu
npm package: @proofdict/types
Description: TypeDefinition for proofdict
Author: azu
Latest version: 3.1.0

# types

TypeDefinition for proofdict

## Install

Install with [npm](https://www.npmjs.com/):

    npm install @proofdict/types

## Usage

```
export interface ProofdictRule {
    id?: string;
    description?: string;
    expected: string;
    patterns: string[];
    tags: string[];
    specs?: ProofdictRuleSpec[];
    [index: string]: any;
}
export interface ProofdictRuleSpec {
    from: string;
    to: string;
}
```

## Changelog

See [Releases page](https://github.com/proofdict/proofdict/releases).

## Running tests

Install devDependencies and Run `npm test`:

    npm i -d && npm test

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/proofdict/proofdict/issues).

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D

## Author

- [github/azu](https://github.com/azu)
- [twitter/azu_re](https://twitter.com/azu_re)

## License

MIT © azu
npm package: @proofgeist/kit
Description: Create web application with the ProofKit stack
Latest version: 0.3.2

<p align="center">
  <picture>
  <img src="https://github.com/proofgeist/proofkit/blob/dde6366c529104658dfba67a8fc2910a8644fc64/docs/src/assets/proofkit.png" width="260" alt="Logo for ProofKit">
</picture>
</p>

<h1 align="center">
  ProofKit CLI
</h1>

<p align="center">
  Interactive CLI to manage your TypeScript projects that connect with FileMaker
</p>

<p align="center">
  Get started with a new ProofKit project by running <code>pnpm create proofkit</code>
</p>

View full documentation at [proofkit.dev](https://proofkit.dev)
npm package: @proofgeist/mantine-tanstack-table
Description: An opinionated table component with default styling for [Mantine 7](https://mantine.dev/) and [TanStack Table 8](https://tanstack.com/table/v8).
Latest version: 2.2.10

# mantine-tanstack-table

An opinionated table component with default styling for [Mantine 7](https://mantine.dev/) and [TanStack Table 8](https://tanstack.com/table/v8).

Initialize the `useReactTable` hook and pass it into this component to get a fully functional table with sorting, filtering, pagination, and more.

## Installation

```bash
pnpm i @proofgeist/mantine-tanstack-table
```

Requires `@tanstack/react-table` and `@mantine/core` as peer dependencies.

```bash
pnpm install dayjs @mantine/dates
```

## Basic Example (minimal)

```tsx
import TanstackTable from "@proofgeist/mantine-tanstack-table";
import {
  useReactTable,
  getCoreRowModel,
  createColumnHelper,
} from "@tanstack/react-table";

// this CSS only needs to be imported once in your entire app
// and can be ignored if you want to use your own styles
import "@proofgeist/mantine-tanstack-table/styles.css";

type TData = { name: string };
const columnHelper = createColumnHelper<TData>();

// define your columns outside of your component to avoid re-renders
// or within a useMemo hook if needed to be inside the component
const columns = [columnHelper.accessor("name", { header: "Name" })];

function MyComponent() {
  const table = useReactTable({
    data: [], // add your data here
    columns,
    getCoreRowModel: getCoreRowModel(),
  });
  return <TanstackTable table={table} />;
}
```

More examples to come