Repository navigation
TypeScript SDK, ROADMAP points to issue tracker for scope, but no tracking issue exists #438
saintmalik
started this conversation in
General
Replies: 1 comment
|
I am prioritizing the 240-scenario measurement work and cannot commit to a TypeScript SDK review or merge schedule. Please do not start a full port on the strength of the roadmap wording. A scope issue can document the proposal, but it would not be an implementation assignment or acceptance commitment. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ROADMAP.md (line 26) lists "TypeScript SDK - community contribution welcome;" i checked the issue tracker for scope, but no such issue exists. Posting to confirm scope before starting:
To Port the verifier to TypeScript, validated against the language-neutral conformance vectors from #199 so parity is testable from day one
Match the Python SDK's fail-closed behavior on malformed inputs, missing attestations, expired certificates
Conventional commits, DCO, CI parity with the Python test suite
Happy to open the tracking issue and take this on if a maintainer confirms scope here.
cc: @imran-siddique
All reactions