
Etherscan's Cards tab now surfaces GitMyABI, generating typed npm packages from any verified contract. Developers import the bindings via npm install and get viem-based TypeScript support.
Etherscan has added GitMyABI to its Cards tab, letting developers convert any verified smart contract ABI into an installable npm package with full TypeScript support. The integration goes live as the tool's beta, launched by Swiss Web3 firm AxLabs on February 7, 2025, goes into broader distribution.
The mechanic is straightforward. Developers browsing a verified contract on Etherscan click the GitMyABI card in the Cards tab. The service extracts the contract's ABI – the JSON interface that tells client code how to call contract functions and read events – and publishes it as an npm package under the @gitmyabi scope. Each contract gets a specific package, like @gitmyabi/aethusdc for a given USDC contract on Ethereum.
The TypeScript bindings use the viem type system. That means autocomplete on function names and arguments, compile-time checks for parameter types, and IDE warnings before a transaction hits the mempool. A developer who passes a string where a uint256 is expected sees the error in their editor, not in Etherscan's transaction status page.
AxLabs focused the tool on the full lifecycle of ABI management: extraction from GitHub repositories, versioning, npm publishing, and binding generation. Packages update when the verified contract changes, so stale interface definitions don't require manual tracking.
Etherscan's existing ABI APIs solved the discovery problem – developers could fetch a contract's interface if they knew where to look and how to parse JSON. What those APIs did not solve was the downstream workflow: turning raw JSON into typed client code, keeping it versioned alongside the application, and ensuring every team member uses the same interface. GitMyABI collapses those steps into a single npm install command.
The Cards tab approach means the tool surfaces exactly when a developer is already looking at a contract's code and thinking about integration. For AxLabs, that distribution channel avoids the need to build separate awareness for a developer tool that competes for attention in a crowded ecosystem.
Drafted by a large language model from the source reporting linked above, then screened by automated publishing checks. It is not read by a journalist before publication. Some articles cite our Alpha Score. Verify prices and figures against the original source. Educational coverage, not personalized advice.