Skip to content
Menu

veyanet

Dev Tools

Is this your project? Claim and verify →

@veyanet/sdk is the TypeScript client for VEYA on Robinhood Chain providing post quantum identity, 2 of 3 consensus, AES sealed execution, and verifiable onchain settlement.

What HEY knows

Building
Last shipped 26 days agoActive: 1 meaningful event in 30 days; latest ship 26 days ago. Evidence Source

Build Momentum 19How it is measured

Latest ship
Code changes, week of 2026-09-28 – 2026-10-04 · 24 commits · · Code activity

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

Latest change
DerivedYesterday: Code changes, week of 2026-10-19 – 2026-10-25. Not counted as building. Evidence Source

Maintenance only, read from the team’s GitHub · not a new capability

What this change is
What it names
Maintenance only, not a new capability: 9 of 10 commits HEY read were documentation, dependency or maintenance changes, and none changed code.
Stage
Maintenance is not a new capability, and code is not a deployment.
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-10-25; HEY first knew on 2026-10-24.
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.

FollowCreate alertTerminal previewView latest ship
Share

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

No account? Email me veyanet’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.

Token market · context
No token tracked
Not yet known
Unknown4 gaps: Published packages (not enough yet), Official docs (no source), API description (no source), Official site changes (no source). Packages name its repository, but none is confirmed as the project’s own.

HEY can answer 6 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule: 1 meaningful event in the last 30 days, the newest 2026-09-30.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 24 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 78 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 20 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source3 registered sources, 2 of them context only.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 24 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 78 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 20 commits+1 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
LinksGitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-09-28 – 2026-10-04 · 24 commits

Code activitySource linked

What changed, in the repository’s own words:

1 active day in veyanet/veya-sdk.

This week HEY looked inside 4 of 24 commits to see what changed: 1 changed code, 3 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

Record ship:de991ea1… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗ (opens in a new tab)

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.

Questions HEY can answer about veyanet — as of 26 Oct

Is veyanet still being built?
DerivedActive: 1 meaningful event in 30 days; latest ship 26 days ago. Evidence
What did veyanet ship last?
FactCode changes, week of 2026-09-28 – 2026-10-04 · 24 commits — Code activity, 26 days ago. Evidence
What does HEY not know about veyanet?
Unknown4 gaps: Published packages (not enough yet), Official docs (no source), API description (no source), +1 more. Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

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

  1. 3 code weeks of maintenance or automation only — not counted as building

    Show the 3 weeks

    1. Code changes, week of 2026-10-19 – 2026-10-25 · 31 commits

      Code activitySource linked

      What changed, in the repository’s own words:

      2 active days in veyanet/veya-sdk.

      Mostly maintenance or automation — not counted as building. A burst of 31 commits, so HEY looked inside a sample and too few changed code. This week HEY looked inside 10 of 31 commits to see what changed: 1 changed code, 9 documentation or maintenance only.

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

    2. Code changes, week of 2026-10-12 – 2026-10-18 · 25 commits

      Code activitySource linked

      What changed, in the repository’s own words:

      6 active days in veyanet/veya-sdk.

      Mostly maintenance or automation — not counted as building. A burst of 25 commits, so HEY looked inside a sample and too few changed code. This week HEY looked inside 10 of 25 commits to see what changed: 10 documentation or maintenance only.

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

    3. Code changes, week of 2026-09-21 – 2026-09-27 · 32 commits

      Code activitySource linked

      What changed, in the repository’s own words:

      5 active days in veyanet/veya-sdk.

      Mostly maintenance or automation — not counted as building. A burst of 32 commits, so HEY looked inside a sample and too few changed code. This week HEY looked inside 10 of 32 commits to see what changed: 10 documentation or maintenance only.

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

  2. Code changes, week of 2026-09-14 – 2026-09-20 · at least 78 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    7 active days in veyanet/veya-sdk.

    How HEY read this week

    A burst of 78 commits this week; HEY is looking inside a sample before it says what changed. So far, HEY looked inside 14 of 78 commits to see what changed: 2 changed code, 5 documentation or maintenance only, 7 could not be classified.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 78 commits (opens in a new tab)

  3. Code changes, week of 2026-09-07 – 2026-09-13 · at least 20 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in veyanet/veya-sdk.

    How HEY read this week

    This week HEY looked inside 2 of 20 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 20 commits (opens in a new tab)

What changed

6 changes on HEY’s record for veyanet: 6 weeks of code pushed.

All 6 changes for veyanet →

The full change record holds 5 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 6 of the 10 research questions that apply.

6 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 5h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 6d ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, 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.

Sources

  • Repository
    https://github.com/veyanet/veya-mcpContext onlyContext only because HEY found this repository by its owner alone and nothing the project controls ties it to the project; it counts once a moderator accepts it, or once the project’s verified owner adds it and a GitHub claim names it, it names the token’s contract, it carries a Robinhood Chain dedication HEY matched to this project, or its homepage is the project’s own site (one the owner did not type in).
  • Repository
    https://github.com/veyanet/veya-sdkOfficial
  • Repository
    https://github.com/veyanet/veya-skillsContext onlyContext only because HEY found this repository by its owner alone and nothing the project controls ties it to the project; it counts once a moderator accepts it, or once the project’s verified owner adds it and a GitHub claim names it, it names the token’s contract, it carries a Robinhood Chain dedication HEY matched to this project, or its homepage is the project’s own site (one the owner did not type in).