Installation

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

• 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

TypeScript

bun add @veritio/core@0.4.7

Python

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

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

Go

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

TypeScript

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

Expected: function

Python

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

Expected: True

Go

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

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.