Skip to content

Security

Security

How to report a vulnerability, where to verify our signing keys, and the current state of manifest signing.

Responsible disclosure

We take security reports seriously. Email security@trusteed.xyz and we respond within 72 hours for critical vulnerabilities. If a merchant disputes a trust score suspension, the appeal route is POST /api/v1/stores/:slug/trust-score/appeal.

Full policy and threat model →

Verifying our signing keys

Three places verify different things. Pick the one that matches what you are checking.

Live JWKS

GET /.well-known/jwks.json

The keys in use right now, to verify a signature made today.

Dated snapshot

GET https://api.trusteed.xyz/api/v1/trust/jwks/snapshots/{YYYY-MM-DD}

The keys that were active and signing on that specific date. Use it to verify something signed in the past, after a key rotation. The MCP tool get_store_trust publishes this URL per response as jwks_snapshot_uri.

Embedded in the receipt (v1.1)

No separate URL

A v1.1 Trust Receipt carries its own historical key material for offline verification, so it does not depend on either endpoint above staying reachable.

Manifest signing, right now

Just verified: the capability manifest at /.well-known/trusteed-capabilities.json is being served with a valid signature. Verify it yourself against the live JWKS above.