Skip to content
HEY Research Lab
Menu

Insight

AI Agents

Integration record: HEY holds no Robinhood Chain evidence for this project (no token, contract or registry listing on the chain), so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim it →

What HEY knows

Development

Shipping consistentlyShipping: 7 counted ships in 30 days; latest ship yesterday. Evidence Source

Build Momentum 59How it is measured

Latest: Code changes this week (since Mon 2 Nov) · 114 commits

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Insight on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow Insight

No account? Email me Insight’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

More detail
Not yet known
Unknown2 gaps: API description (no source), Official site changes (stale). Its website links no API description.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 7 counted ships in the last 30 days, the newest 2026-11-06.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 2 Nov) · 114 commitsCode changes, week of 2026-10-26 – 2026-11-01 · 38 commitsCode changes, week of 2026-10-19 – 2026-10-25 · 59 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Research coverage: HEY can answer 9 of the 11 research questions that apply.
9 of 11 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 47d ago.

Building

  • Building activityMeasuredRead 36m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 23d ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 7h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesStaleThe last read of its website’s files is out of date.

Code and packages

  • Repository detailsMeasuredRead 3d ago.
  • Published packagesMeasuredRead 42m ago.
  • Package advisoriesMeasuredRead 3d ago.

Not applicable here: Contract creation, Contract activity, Published source code, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)X (opens in a new tab)Sources

Latest ship

Checked

Code changes this week (since Mon 2 Nov) · 114 commits

Code activitySource-backed

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

What changed, in the repository’s own words:

5 active days in imokokok/insight.

This week HEY looked inside 3 of 114 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count. 5 automated commits (bot accounts or a repeating scripted message) not counted.

Record ship:a5b0442b… · HEY counts it as building; it does not judge the release’s quality.

Code changes, read from the team’s GitHub · not a deployment
What it names
3 of 3 commits HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or a deployment: code is not a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it to the week of 2026-11-06; HEY first knew on 2026-11-02.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

View evidence ↗ (opens in a new tab)

Shared change · Development spike

Insight: 4 meaningful ships were recorded in the latest 7 days, from 1 in the 7 days before.

Builder status: Shipping.

Dated 2026-10-17 by the sourceSource: HEY Signal

View evidence ↗Evidence receipt

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-10-26 – 2026-11-01 · 38 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    7 active days in imokokok/insight.

    How HEY read this week

    This week HEY looked inside 3 of 38 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-26 – 2026-11-01 · 38 commits (opens in a new tab)

  2. Code changes, week of 2026-10-19 – 2026-10-25 · 59 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    6 active days in imokokok/insight.

    How HEY read this week

    This week HEY looked inside 4 of 59 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-19 – 2026-10-25 · 59 commits (opens in a new tab)

  3. Code changes, week of 2026-10-12 – 2026-10-18 · 51 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    7 active days in imokokok/insight.

    How HEY read this week

    This week HEY looked inside 3 of 51 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 51 commits (opens in a new tab)

  4. Insight Guard SDK 0.6.0

    GitHub releaseSource-backed

    Insight Guard SDK 0.6.0 and verify-insight-receipt 0.5.0 are published to npm from GitHub Actions with provenance (Trusted Publishing via OIDC; no long-lived publish token exists). Both attached tarballs are the artifacts built by this workflow run and carry Sigstore build… Show all

    Insight Guard SDK 0.6.0 and verify-insight-receipt 0.5.0 are published to npm from GitHub Actions with provenance (Trusted Publishing via OIDC; no long-lived publish token exists). Both attached tarballs are the artifacts built by this workflow run and carry Sigstore build attestations: verify with gh attestation verify -R imokokok/Insight. The companion .sha256 assets record their checksums. Install: npm install oracle-insight-guard@0.6.0.

    View evidence: Insight Guard SDK 0.6.0 (opens in a new tab)

  5. Code changes, week of 2026-10-05 – 2026-10-11 · 60 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    7 active days in imokokok/insight.

    How HEY read this week

    This week HEY looked inside 3 of 60 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count. 17 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 60 commits (opens in a new tab)

  6. 2 releases in imokokok/insight on 10 Oct

    GitHub release

    Show all 2 releases

    1. Insight Guard SDK 0.5.1

      GitHub releaseSource-backed

      Insight Guard SDK 0.5.1 and verify-insight-receipt 0.4.0 are published to npm from GitHub Actions with provenance (Trusted Publishing via OIDC; no long-lived publish token exists). Both attached tarballs are the artifacts built by this workflow run and carry Sigstore build… Show all

      Insight Guard SDK 0.5.1 and verify-insight-receipt 0.4.0 are published to npm from GitHub Actions with provenance (Trusted Publishing via OIDC; no long-lived publish token exists). Both attached tarballs are the artifacts built by this workflow run and carry Sigstore build attestations: verify with gh attestation verify -R imokokok/Insight. The companion .sha256 assets record their checksums. Install: npm install oracle-insight-guard@0.5.1.

      View evidence: Insight Guard SDK 0.5.1 (opens in a new tab)

    2. Insight Guard SDK 0.5.0

      GitHub releaseSource-backed

      Insight Guard SDK 0.5.0 adds transaction review: a pinned-block risk review of the exact original Uniswap V3 single-pool ERC-20 swap call before any optional PriorSeal authorization. · Review router code, route simulation, cross-oracle price deviation, signed trade size, minimum… Show all
      • Insight Guard SDK 0.5.0 adds transaction review: a pinned-block risk review of the exact original Uniswap V3 single-pool ERC-20 swap call before any optional PriorSeal authorization.
      • Review router code, route simulation, cross-oracle price deviation, signed trade size, minimum output, slippage and freshness for the exact original call.
      • Require an acceptable fresh review before optional PriorSeal authorization and bind the unsigned review commitment to the exact call. This does not sign or broadcast a transaction.
      • Add an independent RWA v2 signing domain with sequence/predecessor…
      View evidence: Insight Guard SDK 0.5.0 (opens in a new tab)

  7. Code changes, week of 2026-09-28 – 2026-10-04 · 44 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    7 active days in imokokok/insight.

    How HEY read this week

    This week HEY looked inside 4 of 44 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 44 commits (opens in a new tab)

  8. Code changes, week of 2026-09-21 – 2026-09-27 · 64 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    7 active days in imokokok/insight.

    How HEY read this week

    This week HEY looked inside 3 of 64 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 64 commits (opens in a new tab)
Earlier ships (2)

  1. oracle-insight-guard 0.4.0

    GitHub releaseSource-backed

    Insight Guard SDK 0.4.0 adds opt-in, independently verified data coverage readiness for standalone Insight and Insight + PriorSeal workflows. · Deterministically evaluate the immutable coverage policy and verify EIP-712 reports against caller-owned policy and signer trust pins.… Show all
    • Insight Guard SDK 0.4.0 adds opt-in, independently verified data coverage readiness for standalone Insight and Insight + PriorSeal workflows.
    • Deterministically evaluate the immutable coverage policy and verify EIP-712 reports against caller-owned policy and signer trust pins.
    • Fetch authenticated coverage assessments and sampled SLO summaries.
    • Revalidate source and destination coverage immediately before provider entry, preserving the signed reports for downstream evidence workflows.
    • Keep coverage readiness separate from trade safety, principal authorization, settlement verification…
    View evidence: oracle-insight-guard 0.4.0 (opens in a new tab)

  2. oracle-insight-guard 0.3.0

    GitHub releaseSource-backed

    Insight Guard SDK 0.3.0 adds explainable diagnostics and recoverable workflows for standalone Insight and Insight + PriorSeal integrations. · Expose assessment scope, evidence insufficiency, typed rechecks, freshness budgets, and the earliest authorization/submission deadline.… Show all
    • Insight Guard SDK 0.3.0 adds explainable diagnostics and recoverable workflows for standalone Insight and Insight + PriorSeal integrations.
    • Expose assessment scope, evidence insufficiency, typed rechecks, freshness budgets, and the earliest authorization/submission deadline.
    • Persist Watch incidents through an application-supplied adapter, require explicit acknowledgement, and expose unavailable-monitor and budget conditions.
    • Read request/cost metadata, estimate workflow budgets, retain joint evidence checkpoints, and resume collection without automatically submitting another…
    View evidence: oracle-insight-guard 0.3.0 (opens in a new tab)

Other changes on HEY’s record

18 changes on HEY’s record for Insight: 5 releases · 1 new Verified Builder or owner proof · 2 official source changes · 3 build pace changes · 7 other changes in 1 more kind.

All 18 changes for Insight →

The full change record holds 7 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Sources

7 places HEY reads for Insight
2 more sources (docs)