# Installation

Kind

tutorial

For

newcomer · developer

Verified against

@veritio/core@0.4.7 · Python SDK 0.0.1 at veritio@c4100ee · Go module at veritio@c4100ee

Install the SDK path you intend to run, then prove the public entrypoint loads. The examples on this site were verified against the exact releases and source revision shown in the page metadata.

## Runtime requirements

[Section titled “Runtime requirements”](#runtime-requirements)

-   TypeScript: Bun 1.3 or a current Node.js runtime with a package manager.
-   Python: Python 3.11 or newer and a checkout of the OSS repository.
-   Go: Go 1.22 or newer.

## Install the verified build

[Section titled “Install the verified build”](#install-the-verified-build)

-   [TypeScript](#tab-panel-6)
-   [Python](#tab-panel-7)
-   [Go](#tab-panel-8)

Terminal window

```sh
bun add @veritio/core@0.4.7
```

The Python SDK is currently source-backed; do not assume a package-index release.

Terminal window

```sh
git clone https://github.com/getveritio/veritio.git
git -C veritio checkout c4100ee7b678d0c6b227c67ae6ea1d8a1f373967
python3 -m pip install -e ./veritio/sdks/python
```

Terminal window

```sh
go get github.com/getveritio/veritio/sdks/go@c4100ee7b678d0c6b227c67ae6ea1d8a1f373967
```

The Python installation checks out the verified commit before running editable installation. This prevents a local branch or newer `main` from silently changing the example underneath the page.

## Prove the import boundary

[Section titled “Prove the import boundary”](#prove-the-import-boundary)

-   [TypeScript](#tab-panel-9)
-   [Python](#tab-panel-10)
-   [Go](#tab-panel-11)

Terminal window

```sh
bun -e "import { createAuditEvent } from '@veritio/core'; console.log(typeof createAuditEvent)"
```

Expected: `function`

Terminal window

```sh
python3 -c "from veritio import create_audit_event; print(callable(create_audit_event))"
```

Expected: `True`

Terminal window

```sh
go list -m github.com/getveritio/veritio/sdks/go
```

Expected: the module path followed by the resolved revision.

An import check proves package resolution only. It does not select storage, configure a hosted account, or validate your application’s tenant boundary.

## If installation fails

[Section titled “If installation fails”](#if-installation-fails)

Symptom

Likely cause

Check

TypeScript export is missing

A different package version was resolved

`bun pm ls @veritio/core`

Python imports another checkout

`PYTHONPATH` or an older editable install wins

`python3 -c "import veritio; print(veritio.__file__)"`

Go resolves a different revision

The module graph already pins another version

`go list -m -json github.com/getveritio/veritio/sdks/go`

Pin reviewed versions in production and keep server credentials out of browser bundles. Installation alone does not make an event trustworthy; authentication, authorization, and tenant resolution remain host responsibilities.

With the import working, [record two audit events and verify their chain](/docs/start/record-first-event/).

[Edit page](https://github.com/getveritio/veritio-website/edit/main/src/content/docs/docs/start/installation.mdx)

Last updated: Aug 23, 2026

[Previous  
Overview](/docs/)[Next  
Record your first event](/docs/start/record-first-event/)

Veritio provides evidence support, not legal advice or automatic compliance.

This site uses cookieless, anonymous analytics (Umami) by default. With your consent, we also enable Google Analytics, which sets cookies and sends usage data to Google. [Privacy Policy](/legal/privacy/)