Reading the repo — stats and the shipped feed land in about ten seconds…
The Dart implementation of atSDK used for implementing Atsign's technology into other software
1.4k 31 197 openLast shipped 4h ago
The Dart implementation of atSDK used for implementing Atsign's technology into other software
The team focused on stabilizing the SDK's cryptographic operations and test reliability this week. Work included wiring up APSK (Asymmetric Pre-Shared Key) routing and auto-publish functionality, integrating post-quantum algorithm size specifications, and updating wire format handling for at-lookup…
Get this in your inbox every Monday →A deterministic 0–100 hygiene score — README, license, CI, tests, docs, and freshness.
Who ships this repo — author concentration and the bus factor across the last 300 mainline commits.
How welcoming this repo is to contributors — issue throughput, close time, responsiveness, and good-first-issue count.
What this project is built on — dependency count by ecosystem, the license mix, and anything worth a legal look before you adopt it.
Whether this project's CI can be trusted — pass rate, run times, flaky runs, and which workflow is the weak link.
Grounded in at_client_sdk's README, structure, and recent commits — answers won't invent code they haven't seen.
A Monday email with what shipped, in plain English — no account needed.
A floor, not a guess: counts only commits whose author, co-author trailer, or message explicitly credits an AI tool (Claude, Copilot, Cursor, aider, Codex…). Based on 30 mainline commits. Unattributed AI code isn't counted here — the full audit estimates that separately.
