Initial vc-api-mock implementation#1
Merged
Merged
Conversation
Implements all VCALM/VC API endpoints: credential issue/verify/derive/status, presentations, workflows and exchanges, challenges, status lists, and interactions. Includes unit, integration, and conformance test suites, OAS spec, CI config, and shared JSDoc typedefs with no @type {any} casts. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Import randomUUID from node:crypto explicitly instead of relying on the global crypto object, which was only added in Node 19. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…429. Use localWorkflowId and localExchangeId path parameter names to match the upstream W3C VCALM spec. Add 413 and 429 response codes to POST /presentations/verify. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
BigBlueHat
reviewed
May 19, 2026
BigBlueHat
approved these changes
May 19, 2026
BigBlueHat
left a comment
BigBlueHat
left a comment
There was a problem hiding this comment.
This is great! @PatStLouis is working on a new test suite approach, and this might be handy to add to the initial "implementations" list.
It may even work with parts of the existing test suites:
- https://github.com/w3c-ccg/vc-api-issuer-test-suite
- https://github.com/w3c-ccg/vc-api-verifier-test-suite
(though these two are going to likely be replaced with Patrick's work)
Thanks for tackling this @djscruggs!
- Update USE_CASES.md to include ecdsa-sd-2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Review Guide
Start with
INITIAL_BUILD.md— it documents every design decision made during the initial build: the fake proof strategy, store injection pattern, mandatory pointer enforcement, single-use challenges, conformance test architecture, and what was intentionally left out.Summary
tsc --checkJs --noEmitfor type safety (no TS compilation)VCALM_BASE_URL)spec/oas.yaml, used by conformance validator at runtimeBefore merging
INITIAL_BUILD.md— it is a reviewer aid, not permanent documentation. Remove it in a follow-up commit or squash before merge.Test plan
npm testpasses (79 tests)npm run lintcleannpm run typecheckcleannpm run test:conformancepasses against the mock🤖 Generated with Claude Code