Skip to content

feat(sdks): fill vendor SDK metadata from each row's own documented package - #3233

Open
CodeRabbit-byte wants to merge 1 commit into
Chain-Love:mainfrom
CodeRabbit-byte:fill-vendor-sdk-metadata
Open

feat(sdks): fill vendor SDK metadata from each row's own documented package#3233
CodeRabbit-byte wants to merge 1 commit into
Chain-Love:mainfrom
CodeRabbit-byte:fill-vendor-sdk-metadata

Conversation

@CodeRabbit-byte

Copy link
Copy Markdown
Contributor

Fills latestKnownVersion, latestKnownReleaseDate, maintainer and license on 10 vendor SDK rows across Tatum, Pinata, LI.FI and Wormhole. 37 placeholder cells, plus one correction. 10 rows, one file.

In #3232 I left the vendor pricing-tier rows alone because a docs link pointing at a family of SDKs does not identify a package. For these four vendors it turned out the linked page names the package outright, in its own install command — so the identification comes from the row, not from me.

slug version release date maintainer license package, per the row's own docs link
tatum-sdk-free 4.2.59 2026-06-08 Tatum MIT @tatumio/tatum
tatum-sdk-pro 4.2.59 2026-06-08 Tatum MIT @tatumio/tatum
tatum-sdk-scale 4.2.59 2026-06-08 Tatum MIT @tatumio/tatum
tatum-sdk-starter 4.2.59 2026-06-08 Tatum MIT @tatumio/tatum
pinata-sdk-fiesta 2.5.6 2026-04-29 Pinata MIT pinata
pinata-sdk-free 2.5.6 2026-04-29 Pinata MIT pinata
pinata-sdk-picnic 2.5.6 2026-04-29 Pinata MIT pinata
lifi-sdk 4.5.0 2026-08-25 LI.FI Apache-2.0 (was MIT) @lifi/sdk
wormhole-sdk-free 6.1.5 2026-07-29 Wormhole (already Apache-2.0) @wormhole-foundation/sdk
wormhole-sdk-usage 6.1.5 2026-07-29 Wormhole (already Apache-2.0) @wormhole-foundation/sdk

Where the package name came from. docs.tatum.io/docs/javascript-sdk gives npm install @tatumio/tatum. docs.pinata.cloud/sdk/getting-started gives npm i pinata. docs.li.fi/sdk/overview gives npm install @lifi/sdk. wormhole.com/docs/tools/typescript-sdk/get-started/ gives npm install @wormhole-foundation/sdk. All four are the URLs already sitting in those rows' actionButtons.

Why tiers of the same vendor share a version. The published SDK does not vary by pricing plan — tatum-sdk-free and tatum-sdk-scale install the same @tatumio/tatum. Repeating the version across a vendor's tiers is the accurate answer, not a copy-paste artefact.

One correction, and I want to be explicit about it since it overwrites a real value rather than a placeholder. lifi-sdk carried license = MIT. @lifi/sdk is Apache-2.0: on npm for the current 4.5.0, on npm for every published version back to the earliest previews, and on the lifinance/sdk repository itself. I checked all three before changing it. Everything else in this PR only touches cells reading exactly TBD.

Still deliberately untouched. thirdweb-sdk and sequence-sdk-free — I fetched both linked docs pages and neither states a package name, so their rows keep TBD. Likewise the Web3Auth, Dfns, Blockdaemon, Dynamic, Magic and ConnectKit-adjacent tiers not covered here or in #3232.

Safety of the edit. A scripted diff against upstream/main confirms 10 lines changed, no width changes, nothing outside the four target columns, and no non-TBD cell altered except the single sanctioned lifi-sdk licence correction above.

validate_csv.py from the json-tools branch: All checks passed. No links added or changed.

Reward address: 0x1589423BeCC3F87EA9406155EaF4D5E04C34Dcf1 (USDC/USDT, Ethereum mainnet)

…ackage

Fills latestKnownVersion, latestKnownReleaseDate, maintainer and license
on 10 vendor SDK rows across Tatum, Pinata, LI.FI and Wormhole. 37
placeholder cells, plus one correction.

Each row's package was taken from the install command on the docs page
that row already links, not inferred: @tatumio/tatum, pinata, @lifi/sdk
and @wormhole-foundation/sdk. Values then come from the npm registry.

Version metadata is identical across a vendor's pricing tiers because the
published SDK does not vary by plan.

Correction: lifi-sdk had license MIT. @lifi/sdk is Apache-2.0 on npm for
every published version and on the lifinance/sdk repository.

validate_csv.py: All checks passed.
@github-actions

Copy link
Copy Markdown

Summary

Status Count
🔍 Total 6
🔗 Unique 6
✅ Successful 6
⏳ Timeouts 0
🔀 Redirected 0
👻 Excluded 0
❓ Unknown 0
🚫 Errors 0
⛔ Unsupported 0

Full Github Actions output

@USS-Supervisor USS-Supervisor left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: APPROVE
Risk: LOW
Summary: The PR is narrow to references/offers/sdks.csv and fills version/date/maintainer/license metadata for existing vendor SDK rows, with the only non-placeholder overwrite limited to the LI.FI license correction supported by package metadata. CSV parsing stays stable at 18 columns/158 rows, required validation passed, and the reviewer-owned current-cycle link-check run 32983724612 completed successfully with 6/6 successful links and 0 errors/timeouts/unknown/unsupported.
Findings: None.
Confidence: HIGH

@USS-Supervisor

Copy link
Copy Markdown
Member

Hi @eugene17kotov - this PR is stale, required CI is passing, and I don't see a blocking review. Could you please review when you have a chance?

@USS-Supervisor

Copy link
Copy Markdown
Member

@eugene17kotov following up on this stale PR. Required CI is passing and I do not see a blocking review, so it still looks ready for reviewer action when you have a chance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants