Skip to content
HEY Research Lab
Menu

Scvd General Store Repo

Payments

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 →

scvd.store is an evidence observatory for agentic commerce. Free preflight and conformance checks on any issuer's x402 doors, offers and receipts. Every verdict is one dated observation, signed and verifiable offline. Bitcoin-anchored corpus. USDC on Base, Arbitrum One, World Chain, Polygon & Solana.

Read more

What HEY knows

Development

Last shipped 9 days agoActive: 4 counted ships in 30 days; latest ship 9 days ago. Evidence Source

Build Momentum 40How it is measured

Latest: Code changes, week of 2026-10-26 – 2026-11-01 · 5 commits

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Scvd General Store Repo 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 Scvd General Store Repo

No account? Email me Scvd General Store Repo’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
Unknown1 gap: Official site changes (stale). The last read of its website’s files is out of date.
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: 4 counted ships in the last 30 days, the newest 2026-10-31.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-26 – 2026-11-01 · 5 commitsCode changes, week of 2026-10-19 – 2026-10-25 · 24 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 63 commits+2 moreWhat 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".
Research coverage: HEY can answer 10 of the 11 research questions that apply.
10 of 11 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 2h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 54d ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 17h ago.
  • API descriptionMeasuredRead 42d ago.
  • Official site changesStaleThe last read of its website’s files is out of date.

Code and packages

  • Repository detailsMeasuredRead 5d ago.
  • Published packagesMeasuredRead 56m ago.
  • Package advisoriesMeasuredRead 5d 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)Sources

Latest ship

Checked

Code changes, week of 2026-10-26 – 2026-11-01 · 5 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:

3 active days in seancrecord/scvd-general-store-repo.

This week HEY looked inside 1 of 5 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 4 automated commits (bot accounts or a repeating scripted message) not counted.

Record ship:e3faf0b3… · 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-10-31; HEY first knew on 2026-10-26.
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 · Verified Builder

Scvd General Store Repo is now a Verified Builder: HEY checked its builder sources.

4 meaningful development events were recorded in the last 30 days. Builder status: Active.

Observed by HEY on 2026-09-24Source: 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: 3 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-19 – 2026-10-25 · 24 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in seancrecord/scvd-general-store-repo.

    How HEY read this week

    This week HEY looked inside 1 of 24 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 3 automated commits (bot accounts or a repeating scripted message) not counted.

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

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

    Code activitySource-backed

    What changed, in the repository’s own words:

    6 active days in seancrecord/scvd-general-store-repo.

    How HEY read this week

    This week HEY looked inside 4 of 63 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. 10 automated commits (bot accounts or a repeating scripted message) not counted.

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

  3. Code changes, week of 2026-10-05 – 2026-10-11 · 46 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    7 active days in seancrecord/scvd-general-store-repo.

    How HEY read this week

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

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

  4. Code changes, week of 2026-09-28 – 2026-10-04 · 95 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in seancrecord/scvd-general-store-repo.

    How HEY read this week

    This week HEY looked inside 3 of 95 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. 8 automated commits (bot accounts or a repeating scripted message) not counted.

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

  5. Code changes, week of 2026-09-21 – 2026-09-27 · at least 48 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    at least 5 active days in seancrecord/scvd-general-store-repo since 2026-09-21; the count stops at the newest 100 commits listed.

    How HEY read this week

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

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

  6. 2 releases in seancrecord/scvd-general-store-repo on 16 Sep

    GitHub release

    Show all 2 releases

    1. September 16: catalog verifier archive-signing patch

      GitHub releaseSource-backed

      Archive-signing patch for the September 16 catalog and verifier release. PR #755 replaces deprecated Cosign output flags with a supported signature bundle and verifies the exact tagged workflow identity before upload. It changes release machinery and documentation; the original… Show all

      Archive-signing patch for the September 16 catalog and verifier release. PR #755 replaces deprecated Cosign output flags with a supported signature bundle and verifies the exact tagged workflow identity before upload. It changes release machinery and documentation; the original catalog, MCP parity and onboarding work shipped in PR #751. The original tag is…

      View evidence: September 16: catalog verifier archive-signing patch (opens in a new tab)

    2. September 16: catalog and verifier consistency

      GitHub releaseSource-backed

      The storefront and MCP verifier now share generated buyer facts and consistent verification metadata. Released through PR #751. · The catalog has 35 active items; Hosted Profile is $21. The reported $19/24-item discrepancy did not reproduce, so no price or item ID was changed.… Show all
      • The storefront and MCP verifier now share generated buyer facts and consistent verification metadata. Released through PR #751.
      • The catalog has 35 active items; Hosted Profile is $21. The reported $19/24-item discrepancy did not reproduce, so no price or item ID was changed. The release adds repeatable checks across catalog, pricing, item pages, unsigned 402 quotes, agent guidance, OpenAPI and sitemap.
      • Both MCP endpoints now give the same effect hints for preflight, receipt conformance and artifact verification.…
      View evidence: September 16: catalog and verifier consistency (opens in a new tab)

  7. v1.0.0

    GitHub releaseSource-backed

    View evidence: v1.0.0 (opens in a new tab)

Other changes on HEY’s record

10 changes on HEY’s record for Scvd General Store Repo: 3 releases · 1 new Verified Builder or owner proof · 6 weeks of code pushed.

All 10 changes for Scvd General Store Repo →

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

Sources

8 places HEY reads for Scvd General Store Repo
3 more sources (docs)

Security context: bug bounty page on the project’s site · a published security contact. An audit shows an audit took place; it is not a guarantee of safety.