Files
zeekayandHanzo Dev 1bf8bd0b37 upstream attribution belongs in NOTICE, not in the README
The README is the product's front door and carries our brand. NOTICE is where a
fork's provenance is legally required to live, and it is the file a licence audit
reads. Naming the upstream in the README put attribution in the one place nobody
checks for it and branding in a place that had to share.

Where the NOTICE already named the same upstream, the moved line was dropped
rather than duplicated, and markdown link syntax was flattened -- NOTICE is plain
text, not a rendered document.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-05 21:55:55 -07:00

860 B

Hanzo Insights Node.js SDK

Note: The Node.js SDK code has moved to hanzoai/insights-js — use @hanzo/insights-node instead.

Install

npm install @hanzo/insights-node

Usage

import { Insights } from '@hanzo/insights-node'

const insights = new Insights('YOUR_API_KEY', {
  host: 'https://insights.hanzo.ai'
})

insights.capture({
  distinctId: 'user_123',
  event: 'signed_up',
  properties: { plan: 'pro' }
})

await insights.shutdown()

Upstream

This is a branded fork. Active development is in hanzoai/insights-js/packages/node.

To sync upstream:

git remote add upstream https://github.com/PostHog/posthog-node.git
git fetch upstream
git merge upstream/main