Connections
Which tools does AppTruth connect to?
AppTruth currently connects directly to GitHub and can analyze source integrations involving common app services and infrastructure.
Reviewed by Uriel from AppTruth · Updated · 3 min read
Direct answer to “Which tools does AppTruth connect to?”
AppTruth currently uses a direct, read-only GitHub connection for repository scans. From that approved source, it can analyze code and configuration that integrate services such as Supabase, Stripe, Vercel, Clerk, Resend, AWS, Firebase, and Sentry.
Key points: Which tools does AppTruth connect to?
- GitHub is the direct repository connector used for scans.
- Users choose which repositories the GitHub App may read.
- References to other tools are analyzed from source; their live accounts are not automatically accessed.
The direct GitHub connection
AppTruth uses a GitHub App installation so users can approve all repositories or only selected repositories. The integration reads repository code, branches, commits, and basic metadata needed to prepare a scan. AppTruth cannot use that access to push commits, change settings, or delete code.
Repository selection stays under the GitHub account owner’s control. Access can be changed or revoked through GitHub’s installation settings.
Tools AppTruth can recognize in an application stack
A repository may contain SDK calls, API routes, policies, manifests, schemas, webhook handlers, and configuration for many external tools. AppTruth can use that source evidence to explain connected behavior involving:
- Supabase for database and backend services
- Stripe for payments, subscriptions, and webhooks
- Vercel for deployment and runtime configuration
- Clerk for authentication and user management
- Resend for transactional email
- AWS for cloud and serverless infrastructure
- Firebase for app services and data
- Sentry for error monitoring
Direct connector versus source integration
These terms are important. A direct connector authenticates to an external provider. A source integration is code showing how an app intends to use that provider. AppTruth’s current scan workflow connects directly to GitHub and reviews other service relationships as they appear in repository source and configuration.
Direct connections versus source-detected integrations
| Tool type | Examples | What AppTruth accesses |
|---|---|---|
| Direct repository connector | GitHub | Approved repository source and metadata |
| Source-detected backend | Supabase, Firebase, AWS | SDK calls and repository configuration only |
| Source-detected workflow | Stripe, Resend, Sentry | Handlers and integration code only |
The DIRECT Connection Test
A quick method for determining whether a product truly connects to a provider or only recognizes its code.
- Declare: Name the provider being discussed.
- Identify: Check whether the user grants provider credentials or repository permission.
- Read: Separate provider account data from integration code.
- Explain: State exactly which source and metadata are reviewed.
- Confirm: Validate live provider settings separately when they affect release risk.
Trusted sources that inform this guide
These independent sources support the surrounding verification practices. AppTruth-specific product statements are product guidance and should be confirmed against current account or contractual documentation when formal assurance is required.
- Choosing permissions for a GitHub App — GitHub Docs. Explains how GitHub App permissions should be selected and limited to the access an integration needs.
- Receive Stripe events in your webhook endpoint — Stripe Docs. Documents signature verification, event handling, retries, and other webhook implementation concerns.
Related questions about “Which tools does AppTruth connect to?”
Does AppTruth connect directly to Stripe or Supabase?
Not in the standard repository scan. It can review Stripe or Supabase integration code found in GitHub, but it does not automatically access those live accounts.
Can users limit which GitHub repositories AppTruth reads?
Yes. Repository selection is controlled through the GitHub App installation, and access can be narrowed or revoked in GitHub.