Skip to content

Automic Vault

$AUTOMIC

Dev Tools

Is this your project? Claim and verify →

pple has spent years strengthening Mac app security with Gatekeeper, notarization, malware checks, and permissions for sensitive data.

What HEY knows

Building
Shipped this weekDerivedShipping: 1 meaningful event in 30 days; latest ship yesterday. Evidence Source

Build Momentum 25How it is measured

Latest ship
Code changes, week of 2026-10-12 – 2026-10-18 · · Code activity

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

FollowCreate alertTerminal previewView latest ship
Share

Follow puts Automic Vault on your private watchlist and at the top of “Since you were last here” when you come back. Then pick what HEY should notify you about. Following needs an account; browsing never does.

No account? Email me Automic Vault’s changes — or read its RSS feed.

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.

Product usage
UnknownThe project has a contract, but HEY does not count its calls yet: a token joins the watch once it takes calls in a thirty-day window, and any contract the project’s own sources name is watched. Unknown, not zero.
Contracts
Fact1 contract watched, 1 with verified source; no implementation or interface change recorded.
Token market · context
Market data insufficientToken verified
Not yet known
Unknown5 gaps: API description (no source), Contract creation (not enough yet), Current market (not enough yet), Market history (not enough yet), Supply distribution (not enough yet). Its website links no API description.

HEY can answer 14 of the 19 research questions that apply · Research coverage

What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 1 meaningful event in the last 30 days, the newest 2026-10-12.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18What 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.
Source28 registered sources, 0 of them context only.ReadWhat 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.
Token verified.
Token verified: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedToken verified: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Market data insufficient.
Market data insufficient: HEY holds no market reading for the token.
Source1 reading from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Market data insufficient”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Market figures are context only and never change activity status. Methodology

Latest ship

Code changes this week (since Mon 12 Oct) · 1 commit

Code activitySource linked

1 active day in automicvault/automicvault.

What changed, in the repository’s own words:

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

Record ship:f4bf599d… · 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: 11 weeks before HEY began reading this project’s sources — not yet read, not zero.

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about Automic Vault? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

Research coverage

HEY can answer 14 of the 19 research questions that apply.

14 of 19 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 12h ago.

Building

  • Building activityMeasuredRead just now.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 12m ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 34m ago.

Code and packages

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

Contracts

  • Contract creationNot enough yetHEY has not read the contract’s creation yet.
  • Contract activityMeasuredRead today.
  • Verified sourceMeasuredRead 1h ago.
  • Contract interfaceMeasuredRead 1h ago.

Market

  • Current marketNot enough yetNo market reading yet.
  • Market historyNot enough yetNo daily market history recorded yet.
  • Supply distributionNot enough yetHEY has not mapped this token’s supply yet.
  • LocksMeasuredRead 3h ago.
  • Market checksMeasured

Not applicable here: Package advisories, 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

23 more sources (docs)

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

Contract
0x5e9d…f30e0x5e9def5ee90d34f8d94350765c43899b8147f30e