Code changes this week (since Mon 9 Nov) · 19 commits
Code activitySource-backed
Why it matters: One of 5 counted ships in the last 30 days: building continued, not a one-off.
What changed, in the repository’s own words:
6 active days in crossmint/crossmint-sdk.
This week HEY looked inside 1 of 19 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.
Record ship:4a070ceb… · 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-11-14; HEY first knew on 2026-11-09.
- 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.