Skip to content
Menu

Clanker SDK

Dev Tools

Is this your project? Claim and verify →

TypeScript SDK for interacting with Clanker contracts

What HEY knows

Building
Quiet for 50 daysQuiet: 0 meaningful events in 30 days; latest ship on 2026-08-30. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-08-24 – 2026-08-30 · 1 commit · · Code activity

Why it matters: First week of code changes after 53 quiet days.

Latest change
Derived2 days ago: HEY reclassified the project — official source added: docs. Evidence Source
FollowCreate alertTerminal previewView latest ship
Share

Follow puts Clanker SDK 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 Clanker SDK’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
Unknown2 gaps: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s own.

HEY can answer 8 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
Quiet.
“Quiet” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-08-30.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-08-24 – 2026-08-30 · 1 commitv4.2.19v4.2.18+1 moreWhat 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".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-08-24 – 2026-08-30 · 1 commitv4.2.19v4.2.18+4 moreWhat 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
LinksWebsiteGitHubSources

Latest ship

Checked

Code changes, week of 2026-08-24 – 2026-08-30 · 1 commit

Code activitySource linked

What changed, in the repository’s own words:

1 active day in clanker-devco/clanker-sdk.

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

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

View evidence ↗

Shared change · Release

Clanker SDK shipped v4.2.3.

Builder status: Quiet.

Dated 2026-03-09 by the sourceSource: github

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.

Questions HEY can answer about Clanker SDK — as of 2026-10-19

Is Clanker SDK still being built?
DerivedQuiet: 0 meaningful events in 30 days; latest ship on 2026-08-30. Evidence
What did Clanker SDK ship last?
FactCode changes, week of 2026-08-24 – 2026-08-30 · 1 commit — Code activity, on 2026-08-30. Evidence
What does HEY not know about Clanker SDK?
Unknown2 gaps: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

  1. v4.2.19

    GitHub releaseSource verified

    What's Changed · fix: point Base v4 locker at FeeConversion 1.1 (unblocks Base deploys) by @manan19 in https://github.com/clanker-devco/clanker-sdk/pull/141 New Contributors · @manan19 made their first contribution in https://github.com/clanker-devco/clanker-sdk/pull/141 Full… Show all
    • What's Changed
    • fix: point Base v4 locker at FeeConversion 1.1 (unblocks Base deploys) by @manan19 in https://github.com/clanker-devco/clanker-sdk/pull/141 New Contributors
    • @manan19 made their first contribution in https://github.com/clanker-devco/clanker-sdk/pull/141 Full Changelog: https://github.com/clanker-devco/clanker-sdk/compare/v4.2.18...v4.2.19
    View evidence

  2. v4.2.18

    GitHub releaseSource verified

    What's changed · Bug fix: Robinhood v4 CREATE2 address prediction now uses the correct ClankerToken creation bytecode (shared with BSC v4.1) · Fixes vanity (0x4b07) and predictTokenAddressV4 mismatch where SDK predicted wrong token addresses on Robinhood Upgrade notes Bots and… Show all
    • What's changed
    • Bug fix: Robinhood v4 CREATE2 address prediction now uses the correct ClankerToken creation bytecode (shared with BSC v4.1)
    • Fixes vanity (0x4b07) and predictTokenAddressV4 mismatch where SDK predicted wrong token addresses on Robinhood Upgrade notes Bots and apps deploying on Robinhood (chain ID 4663) should upgrade immediately if they pre-compute token URLs/addresses before deploy. npm install clanker-sdk@4.2.18 Test plan
    • [x] Robinhood incident fixture predicts 0x085844F1... (not 0x75b45af4...)
    • [x] Vanity service + prediction agree on…
    View evidence

  3. v4.2.14

    GitHub releaseSource verified

    (Bug) BSC vanity address

    View evidence

  4. v4.2.13

    GitHub releaseSource verified

    (Bug) Add fee preference to CLI deploys

    View evidence

  5. v4.2.12

    GitHub releaseSource verified

    (Feat) CLI for token deployment · (Feat) Clanker skill.md for AI agents · (Feat) Custom fee % for CLI Show all
    • (Feat) CLI for token deployment
    • (Feat) Clanker skill.md for AI agents
    • (Feat) Custom fee % for CLI
    View evidence

  6. v4.2.11

    GitHub releaseSource verified

    (Chain) BSC

    View evidence

  7. v4.2.10

    GitHub releaseSource verified

    (Feat) getTokenRewards

    View evidence

  8. v4.2.8

    GitHub releaseSource verified

    (Feat) Pass in custom dev buy recipient · (Feat) Add dataSuffix to deploys · (Feat) Claim creator fees for v0-v3.1 Show all
    • (Feat) Pass in custom dev buy recipient
    • (Feat) Add dataSuffix to deploys
    • (Feat) Claim creator fees for v0-v3.1
    View evidence

  9. v4.2.6

    GitHub releaseSource verified

    (Feat) Allowlisted presales

    View evidence

  10. v4.2.5

    GitHub releaseSource verified

    (Feat) Use custom salt to predict address

    View evidence

  11. v4.2.4

    GitHub releaseSource verified

    (Config) 20 ETH pool positions · (Feat) Configurable starting MC in USDC Show all
    • (Config) 20 ETH pool positions
    • (Feat) Configurable starting MC in USDC
    View evidence

  12. v4.2.3

    GitHub releaseSource verified

    (Feat) Claim fees from legacy SAFE · (Feat) Generate merkle proof Show all
    • (Feat) Claim fees from legacy SAFE
    • (Feat) Generate merkle proof
    View evidence

  13. v4.2.2

    GitHub releaseSource verified

    (Feat) Presale extension methods · (Feat) Withdraw ETH early from presale · (Feat) Update presales to new version Show all
    • (Feat) Presale extension methods
    • (Feat) Withdraw ETH early from presale
    • (Feat) Update presales to new version
    View evidence

  14. v4.1.27

    GitHub releaseSource verified

    (Chain) Monad · (Feat) Non-ETH dev buy support · (Feat) Presale fixes Show all
    • (Chain) Monad
    • (Feat) Non-ETH dev buy support
    • (Feat) Presale fixes
    View evidence

  15. v4.1.26

    GitHub releaseSource verified

    (Chain) Mainnet v4.1 support

    View evidence

  16. v4.1.25

    GitHub releaseSource verified

    (Feat) Update token image & metadata

    View evidence

  17. v4.1.24

    GitHub releaseSource verified

    (Feat) v3 updateRewardAdmin functionality

    View evidence

  18. v4.1.23

    GitHub releaseSource verified

    (Config) Add dynamic 3% fee option · (Feat) Update reward recipient for v4 · (Feat) Verify airdrop receivers Show all
    • (Config) Add dynamic 3% fee option
    • (Feat) Update reward recipient for v4
    • (Feat) Verify airdrop receivers
    View evidence

  19. v4.1.21

    GitHub releaseSource verified

    (Feat) v4.1 contracts · (Feat) Update airdrop · (Feat) updateRewardRecipient for v3 contracts · (Feat) Reduce sniperFees secondsToDecay to 20s Show all
    • (Feat) v4.1 contracts
    • (Feat) Update airdrop
    • (Feat) updateRewardRecipient for v3 contracts
    • (Feat) Reduce sniperFees secondsToDecay to 20s
    View evidence

  20. v4.1.15

    GitHub releaseSource verified

    (QoL) DynamicBasic fee config baseFee 50bps -> 100bps · (QoL) Expose RelatedV3_1 type · (Chain) Abstract · (Bug) Fix airdrop precision · (QoL) Better error handling Show all
    • (QoL) DynamicBasic fee config baseFee 50bps -> 100bps
    • (QoL) Expose RelatedV3_1 type
    • (Chain) Abstract
    • (Bug) Fix airdrop precision
    • (QoL) Better error handling
    View evidence

  21. v4.1.14

    GitHub releaseSource verified

    (Feat) Optional vault recipient for v4 deploys

    View evidence

  22. v4.1.13

    GitHub releaseSource verified

    (Feat) Add airdrop extension · (Chain) Monad Testnet · (Feat) Claim vaulted tokens v4 Show all
    • (Feat) Add airdrop extension
    • (Chain) Monad Testnet
    • (Feat) Claim vaulted tokens v4
    View evidence

  23. v4.1.8

    GitHub releaseSource verified

    (Chain) Arbitrum · (Chain) Unichain · (Feat) Multichain reward claiming · (Bug) Fix reward claiming Show all
    • (Chain) Arbitrum
    • (Chain) Unichain
    • (Feat) Multichain reward claiming
    • (Bug) Fix reward claiming
    View evidence

  24. v4.1.4

    GitHub releaseSource verified

    (QoL) Export token types

    View evidence

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 Clanker SDK? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

31 changes on HEY’s record for Clanker SDK: 30 releases · 1 week of code pushed.

All 31 changes for Clanker SDK →

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

8 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 4h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1mo ago.
  • TimelineMeasured

Official site

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

Code and packages

  • Repository detailsMeasuredRead 12h ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

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

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