Skip to Content
Pyxis Docs

Security and privacy

How Pyxis protects project data, and the gaps that are still open.

Design

ConcernControl
Tenant isolationPostgreSQL row-level security; the app connects as a non-owner role, and each request sets its tenant per transaction
Credential theftIngest key secrets are 256-bit and stored only as SHA-256; verification is constant-time; keys are revocable and can expire
Sign-inA signed challenge from a Stellar wallet (a message signature, no transaction); session cookie lasts 7 days
Existence leaksRequests for another project's data return 404 not_found, not 403
Over-collectionStrict allowlists on ingest; traces, logs, bodies, IPs and query strings are rejected or never read
Resource exhaustionBody, data-point, batch, service and route-cardinality caps
Operator accessOperator reads and status changes are written to an audit log
Supply chainLockfile, a small dependency set, Dependabot alerts and updates, secret scanning with push protection

Known gaps

Be aware before you rely on it

These are open. They are tracked in the repository's SECURITY.md.

GapImpactMitigation today
No rate limiting on /v1/*Abuse limited only by size capsRevoke abused keys; add limits at the edge
No scanner or static analysis inside CIVulnerabilities rely on Dependabot and manual reviewReview Dependabot alerts; run npm audit locally
Transitive vulnerabilities from @creit.tech/stellar-wallets-kitnpm audit reports about 20 findings in optional wallet-module libraries used by the demo; no upstream fixThe demo's sign-in is a message signature only; Pyxis stores no wallet secrets
Wallet events are frontend-reportedThey can be inflated by anyone who has the browser keyTreat the funnel as engagement, not proof

Reporting a vulnerability

Use GitHub's private vulnerability reporting: open the repository's Security tab and choose Report a vulnerability, or go to github.com/Pyxis-Hq/pyxis/security/advisories/new. Only the maintainers can see the report. Please do not open a public issue for a vulnerability.

On this page