Skip to content

auraos

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 →

Aura OS — AI company OS on Base / x402

What HEY knows

Development

Quiet for 45 daysQuiet: 0 counted ships in 30 days; latest ship on 2026-09-14. Evidence Source

Build Momentum 0How it is measured

Latest: Code changes, week of 2026-09-14 – 2026-09-20 · 1 commit

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts auraos 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 auraos

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

View latest ship
Share
Not yet known
Unknown1 gap: API description (no source). 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
Quiet.
“Quiet” by the activity rule: 0 counted ships in the last 30 days, the newest 2026-09-14.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · 1 commitWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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 10 research questions that apply.
9 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

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

Official site

  • Official docsMeasuredRead 5d ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 12d ago.

Code and packages

  • Repository detailsMeasuredRead 2d ago.
  • Published packagesMeasuredRead 2d 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.

Market figures are context only and never change activity status. Methodology

Latest ship

Checked

Code changes, week of 2026-09-14 – 2026-09-20 · 1 commit

Code activitySource-backed

Why it matters: The first week of code changes HEY has recorded for this project.

What changed, in the repository’s own words:

1 active day in laszlo23/auraos.

This week HEY looked inside 1 commit to see what changed: 1 changed code.

Record ship:9d84976c… · 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
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-09-14; HEY first knew on 2026-09-18. HEY indexed it later, as history.
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.

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

What changed

2 changes on HEY’s record for auraos: 1 verification change · 1 week of code pushed.

All 2 changes for auraos →

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

Questions HEY can answer about auraos — as of 29 Oct

Show the answers
Is auraos still being built?
DerivedQuiet: 0 counted ships in 30 days; latest ship on 2026-09-14. Evidence
What did auraos ship last?
FactCode changes, week of 2026-09-14 – 2026-09-20 · 1 commit — Code activity, on 2026-09-14. Evidence
What does HEY not know about auraos?
Unknown1 gap: API description (no source). Its website links no API description.

Sources

12 places HEY reads for auraos

Security context: 1 audit report found · a published security contact. An audit shows an audit took place; it is not a guarantee of safety.