Contribute to Faro (open core)
Faro’s verification engine lives in a private monorepo. The public interface is
github.com/vedux98/faro (Apache-2.0) — synced
one-way from private. That’s where community PRs land.
What you can ship
| Accepted | Examples |
|---|---|
| Payment-rail adapters | AP2 / x402 / ACP payload shape fixes |
| SDKs | Bug fixes, new language clients |
| Recipes & docs | Verify-before-pay guides, Guard embed samples |
| Sector adapter samples | Shopify / Razorpay / Dodo checkout snippets (display only) |
What we decline
- Engine changes (signals, scoring, graph, prompts)
- Verdict contract / OpenAPI edits from outside
- Weights, thresholds, or real-data fixtures
Accepted PRs are cherry-picked into private, gated, then re-synced. You keep author credit.
Sign commits with DCO: git commit -s.
Campaign: Build on Faro
- Fork
vedux98/faro - Pick a good-first-issue (adapter churn, docs typo, SDK example)
- Open a small PR with
Signed-off-by - Get listed on the Trust Index contributors wall (display-only — never a trust boost)
Surfaces that use your work
- REST + MCP verify tools
- FaroGuard checkout demo at /guard
- Apify Actor (thin proxy to the same engine)
- x402 / Bazaar (agent paywall — in build, counsel-gated)
Local product suite
Business onboarding (Pages, Keepers, Club) runs on this site + the private API. Open-source contributions stay on the public interface — keep the split sane.