Skip to content

avaira.xyz

AI Agents

Is this your project? Claim and verify →

Runtime governance layer that makes AI agents auditable, accountable, and rated. Like a credit score for autonomous agents.

What HEY knows

Building
Last shipped yesterdayShipping: 2 meaningful events in 30 days; latest ship yesterday. Evidence Source

Build Momentum 32How it is measured

This change
Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit 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-10-25; HEY first knew on 2026-10-25.
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 avaira.xyz 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 avaira.xyz’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
Unknown3 gaps: Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer.

HEY can answer 7 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
Shipping.
“Shipping” by the activity rule: 2 meaningful events in the last 30 days, the newest 2026-10-25.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-19 – 2026-10-25 · 18 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 26 commitsWhat 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".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source2 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-19 – 2026-10-25 · 18 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 26 commitssource:9859b0ef-b604-423c-a07b-a8aba1e1954dWhat 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

Latest ship

Checked

Code changes, week of 2026-10-19 – 2026-10-25 · 18 commits

Code activitySource linked

2 active days in ranaalyan1/avaira.xyz.

This week HEY looked inside 1 of 18 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

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

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: 9 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about avaira.xyz — as of 26 Oct

Is avaira.xyz still being built?
DerivedShipping: 2 meaningful events in 30 days; latest ship yesterday. Evidence
What did avaira.xyz ship last?
FactCode changes, week of 2026-10-19 – 2026-10-25 · 18 commits — Code activity, yesterday. Evidence
What does HEY not know about avaira.xyz?
Unknown3 gaps: Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer. 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. Code changes, week of 2026-10-12 – 2026-10-18 · 26 commits

    Code activitySource linked

    3 active days in ranaalyan1/avaira.xyz.

    How HEY read this week

    This week HEY looked inside 4 of 26 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.

What changed

3 changes on HEY’s record for avaira.xyz: 1 new project on HEY · 2 weeks of code pushed.

avaira.xyz on What changed →

The full change record holds 1 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 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 10d ago.

Building

  • Building activityMeasuredRead 12m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsSource unavailableIts website did not answer.
  • API descriptionSource unavailableIts website did not answer.
  • Official site changesSource unavailableIts website did not answer.

Code and packages

  • Repository detailsMeasuredRead 23h ago.
  • Published packagesMeasuredRead 23h ago.

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