feat(sdks): fill verified registry metadata for 25 Algorand, Filecoin and Somnia SDK offers

[CodeRabbit-byte]

Fills latestKnownVersion, latestKnownReleaseDate, maintainer and license on 25 SDK rows referenced by the Algorand, Filecoin and Somnia listings. 96 previously empty cells, 25 rows, one file.

These four columns are objectively checkable — they come from package registries and the projects' own repositories, so nothing here rests on vendor marketing copy.

slug	version	release date	maintainer	license
abitype	1.3.0	2026-07-16	wevm	MIT
algokit-avm-vscode-debugger	1.1.7	2025-11-07	Algorand Foundation	MIT
algokit-cli	2.10.2	2026-01-30	Algorand Foundation	MIT
algokit-client-generator-py	2.2.0	2025-07-24	Algorand Foundation	MIT
algokit-client-generator-ts	6.0.1	2025-11-21	Algorand Foundation	MIT
algokit-utils-py	4.2.3	2025-12-15	Algorand Foundation	MIT
algokit-utils-ts	9.2.0	2025-12-15	Algorand Foundation	MIT
algorand-go-sdk	2.12.0	2026-08-19	Algorand	MIT
algorand-java-sdk	2.11.0	2026-08-24	Algorand	MIT
algorand-javascript-sdk	3.7.0	2026-08-19	Algorand	MIT
algorand-python-sdk	2.12.0	2026-08-19	Algorand	MIT
alloy	2.4.1	2026-08-13	Alloy	Apache-2.0
ape-framework	0.8.51	2026-08-22	The ApeWorX Collective	Apache-2.0
eth-abi	6.0.0	2026-08-22	The ApeWorX Collective	MIT
eth-account	0.14.0	2026-08-23	The ApeWorX Collective	MIT
ethereumjs	—	—	EthereumJS	—
go-ethereum	1.17.5	2026-07-27	—	LGPL-3.0
ox	1.7.2	2026-08-26	wevm	MIT
safe-api-kit	5.0.2	2026-08-04	Safe Labs GmbH	MIT
safe-protocol-kit	8.0.6	2026-08-12	Safe Labs GmbH	MIT
somnia-data-streams-sdk	0.12.2	2026-01-20	Somnia	MIT
synapse-sdk	1.2.1	2026-08-26	FilOz & Friends	MIT / Apache-2.0
tevm	1.0.0-next.148	2025-10-04	tevm	MIT
viem	2.55.19	2026-08-19	wevm	MIT
web3j	6.0.0	2026-06-29	Web3J	Apache-2.0

Where each value came from. Versions and dates are the latest GitHub release for standalone repositories. For the three packages published out of a monorepo the repo tag does not identify the package, so the npm registry was used instead: safe-api-kit and safe-protocol-kit sit under one r71 monorepo tag, and somnia-data-streams-sdk publishes as @somnia-chain/streams with no GitHub releases at all. Licenses are GitHub's detected SPDX identifier, cross-checked on npm where GitHub returned NOASSERTION — that is how viem (MIT), synapse-sdk (MIT / Apache-2.0) and web3j (Apache-2.0, its LICENSE is the Apache 2.0 text verbatim) were resolved. Maintainers are the GitHub organisation's own published display name, which is why a few differ from the provider brand in the same row — Safe is maintained by Safe Labs GmbH, the AlgoKit tooling by the Algorand Foundation rather than Algorand.

Formatting follows the rows that already carry real values. Versions are bare semver with no v prefix, matching four of the five populated examples in the file. Dates are ISO YYYY-MM-DD. Licenses are SPDX identifiers, with the existing MIT / Apache-2.0 form reused for the dual-licensed row.

Left empty rather than guessed. Three gaps I could not close from a source I actually read:

• go-ethereum maintainer — the ethereum organisation publishes no display name and the README states none, so there was nothing to cite.
• ethereumjs version, date and license — a monorepo whose packages carry different licences (packages/vm is MPL-2.0), with no root LICENSE and no single release version. Its latest release tag is @ethereumjs/vm@10.1.3, which describes one package rather than the row.
• iso-filecoin and nethereum are untouched — neither has a repository link in actionButtons to verify against.

I would rather leave a cell empty than fill it with something that reads as verified and is not.

Note on TBD. Most rows in this file carry TBD in these four columns — 120 of them for version and date. I have not touched those, since replacing a placeholder is a different change from filling an empty cell and would balloon the diff past the size limit. If you would like the same treatment applied to the TBD rows I am happy to do it in follow-up PRs, batched to stay inside the 100-line / 200-cell limit.

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

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

[USS-Supervisor]

Verdict: APPROVE
Risk: LOW
Summary: The PR is narrow to references/offers/sdks.csv and only fills registry/repository metadata columns for existing SDK rows. CSV parsing stays stable at 18 columns/158 rows, required validation passed, and the reviewer-owned current-cycle link-check run 32983721214 completed successfully with 45/45 successful links and 0 errors/timeouts/unknown/unsupported.
Findings: None.
Confidence: HIGH

[USS-Supervisor]

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?

[CodeRabbit-byte]

Flagging a compliance problem with this PR that I found after it was approved, rather than letting it merge unmentioned.

The SDKs wiki page, lines 74-77, says of latestKnownVersion, latestKnownReleaseDate, maintainer and license:

Fields reserved for automation scripts from Chain.Love team - fetching this information from the action buttons link.
Can't be modified manually.

This PR modifies those columns manually. I did not know that paragraph existed when I opened this in August, and the review process did not surface it — but that does not make the edit compliant.

I am not asking for an exception. #3574 now puts the question directly to the maintainers: run the automation, drop the reservation, or drop the columns. If the reservation stands, please close this PR. If it is lifted, the change is ready as it is.

Every value here is sourced from the row's own action-button link — the package's registry entry or its GitHub repository — and the branch has been rebuilt on current main after yesterday's upstream SDK additions, with a cell-by-cell check confirming that no value this PR writes has since been set upstream. That part I stand behind. Whether it is mine to write is the open question.