feat: add ucp_validate.py CLI readiness validator#34
Draft
sbeashwar wants to merge 1 commit intoUniversal-Commerce-Protocol:mainfrom
Draft
feat: add ucp_validate.py CLI readiness validator#34sbeashwar wants to merge 1 commit intoUniversal-Commerce-Protocol:mainfrom
sbeashwar wants to merge 1 commit intoUniversal-Commerce-Protocol:mainfrom
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
sbeashwar
force-pushed
the
pr3-validator
branch
from
d86e4f1 to
71db60b
Compare
sbeashwar
force-pushed
the
pr3-validator
branch
3 times, most recently
from
f2611ec to
098b2ab
Compare
Standalone merchant readiness validator for UCP endpoints. Point it at any merchant URL, get a structured pass/fail report. Features: - Fetches and validates /.well-known/ucp discovery profile - Dual schema version support (2026-01-11 + 2026-01-23) - Structural consistency checking (version vs service/capability format) - Only checkout is required; other declared capabilities validated - Payment handler validation (structure, reverse-DNS naming) - URL reachability checking for all spec/schema references - Signing key JWK format validation - Optional checkout smoke test (--smoke) - JSON output mode (--json) - Colored terminal output with ANSI badges - Exit code 0 for READY, 1 for NOT_READY Usage: uv run ucp_validate.py https://merchant.example.com uv run ucp_validate.py http://localhost:8182 --smoke uv run ucp_validate.py https://merchant.example.com --json
sbeashwar
force-pushed
the
pr3-validator
branch
from
098b2ab to
17d7660
Compare
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
1 participant
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.
A standalone CLI that produces a single READY / NOT_READY verdict for a UCP merchant's discovery profile, without requiring the conformance test fixtures (sample items, buyer, payment instrument, SDK wiring).
Complements
protocol_test.pyrather than replacing it:BusinessSchema/ReverseDomainName, same as protocol_test after fix: validate payment handler structure from profile instead of hardcoded list #33).signing_keys[](kid, kty, EC crv/x/y, RSA n/e) - not covered by the conformance suite today.POST /checkout-sessionswith a known-fake item; treats 400 as "endpoint alive" - not covered by conformance without a full integration setup.--jsonoutput + non-zero exit on NOT_READY for CI gates.Usage:
Kept as draft pending feedback on whether maintainers want this in-tree or as a separate utility.