Public Activity Snapshot

Public activity. Clear context.

These numbers describe the public TWiN footprint. They are sourced, bounded, and kept separate from claims about people, clinical outcomes, production readiness, or mission impact.

How to interpret these numbers

Published project sites16

Mapped points78

Relationships171

Public repositories10

Static public snapshot embedded; live refresh runs when available.

Dated audience signal

LinkedIn Audience Snapshot

Profile-visible follower snapshots are kept separate by audience and never presented as unique reach, engagement, outcomes, or impact.

JZ followers: 1,226
Roshi followers: 4,630
TWiN followers: 26

Read the LinkedIn signal

Dated LinkedIn profile and company-page snapshot observed August 24, 2026; not a live API feed and not a measure of unique reach or impact.

Official package distribution

Package Download Activity

NPM is one emerging distribution channel in a much larger ecosystem. Every displayed count comes from npm’s official daily range API. The optional npm-stat comparison never changes the published record.

Open the TWiN NPM profile

Official range history

All TWiN modules

January 1, 2026–October 10, 2026 · official daily range series

Official downloads163

Last week1

Last month10

Last year163

First download day: August 11, 2026 · 102
Peak day: August 11, 2026 · 102
Coverage: 283 official range days · 1 module

Browse the complete daily download record

Official daily npm range record
Date	Downloads
The daily table loads when public telemetry scripts are available; official summary totals remain above.

Official npm range series is authoritative and published unchanged; optional npm-stat comparison differs.

Source ledger

Sources and Interpretation

ECOSYSTEM

Published interfaces come from the curated TWiN profile; mapped points and relationships come from Astrolabe.

CODE

Repository counts come from GitHub’s public account inventory.

NPM

Daily values come from npm’s official range endpoint; npm-stat remains optional comparison context only.

Dated profile and company-page snapshots remain separate, are not scraped at runtime, and are not claims about unique reach or impact.