How To See If Im On The Tea App: The Complete Profile And Package Verification Guide

To verify if your open-source software packages or developer identity have been indexed on the tea protocol (tea.xyz), navigate to the official tea web application, use the centralized search directory to query your GitHub username or specific package identifiers, and inspect the resulting "tea Rank" metric. If your profile appears, you can securely claim your digital identity and any associated developer rewards by authenticating your ownership through a standard GitHub OAuth handshake or by merging a cryptographic configuration file into your repository root. This comprehensive guide outlines the exact processes for both Web3 developer protocol verification and social "Tea" application profile lookups.

Pre-Verification Requirements and Setup Criteria

Before initiating the search and verification process on the tea platform, you must gather specific credentials and understand the underlying indexing architecture. The tea protocol automatically crawls open-source registries such as npm, PyPI, Crates.io, and GitHub repositories. Because of this automated pipeline, many developers find themselves listed on the platform without having manually signed up.

To ensure a seamless verification session, review the following essential tools, prerequisite knowledge, and benchmarks:

• Essential Search & Identification Tools:

  
  
  
  • Your primary GitHub, GitLab, or Bitbucket account usernames.
  • Complete list of published package names and their respective package registry scopes (for example, @username/package-name for npm).
  • A secure, Web3-compatible browser extension or hardware wallet (such as MetaMask, Coinbase Wallet, or WalletConnect) if you intend to claim ownership of indexed assets.
  • Access to the command-line interface (CLI) or terminal of your local machine to verify repository configurations if manual cryptographic signing is required.

• Mandatory Prerequisite Knowledge:

  
  
  
  • Familiarity with standard software package registries (npm, PyPI, Maven, Cargo, or Homebrew).
  • Basic understanding of GitHub OAuth permissions and third-party application authorization.
  • A foundational grasp of dependency graphs and how package dependencies influence algorithmic rankings (referred to as tea Rank).

• Estimated Benchmarks and Costs:

  
  
  
  • Time Required: 5 to 10 minutes for basic search and profile verification; 15 minutes for complete cryptographic ownership validation.
  • Financial Cost: $0 USD. Searching, verifying, and claiming your developer profile on the tea protocol is entirely free and does not require gas fees on the blockchain layer during the initial identification phases.

Step-by-Step Developer Profile and Package Verification

To determine if your digital footprint has been registered on the tea protocol, follow this highly structured search and claim sequence. This workflow covers both automated search identification and the secondary manual configuration verification steps.

Step 1: Navigating the tea Protocol Registry

Open a secure web browser and proceed to the official tea web interface at app.tea.xyz. Do not use unverified third-party search tools or aggregate sites, as these may expose your system to phishing risks. Once the dashboard loads, locate the global search bar situated prominently at the top of the user interface. This search utility acts as a direct window into the decentralized database where all crawled developer repositories and individual profiles reside.

Step 2: Executing a Target Query

Type your exact GitHub handle into the search input field and press enter. If your username does not yield an immediate match, run a secondary query using the exact name of an open-source package you have authored or contributed to significantly. For scoped packages (e.g., packages within a specific organization on npm), input the full string including the organizational prefix to ensure the indexing engine can locate the specific nested directory.

Pro-Tip: If you have contributed to major open-source dependencies but do not own the primary repository, search for the parent project name. The tea protocol maps contributor networks, meaning your profile may exist as a sub-entity of a larger, highly-ranked ecosystem project.

Step 3: Analyzing the Profile Status and tea Rank

If a profile matching your search query appears in the results, select it to open the detailed entity page. Observe the primary metrics displayed on this screen. The most critical indicator is the tea Rank, which is a mathematical score derived from the project's position within the global open-source dependency graph.

Next, inspect the profile header for an Unclaimed badge. If the badge is present, it means the system has automatically indexed your open-source contributions based on public registry metadata, but no user has officially linked their Web3 identity to those contributions.

Step 4: Initiating the Secure Ownership Claim

To confirm that you are indeed the legitimate owner of the discovered profile and to prevent identity hijacking, click the Claim Profile button. The interface will prompt you to select a verification path.

The fastest method is GitHub OAuth. Select the GitHub option, which redirects you to GitHub's secure authentication portal. Review the requested scopes carefully—the tea application only requires read-only access to your public profile, email addresses, and repository metadata to confirm your identity. Authorize the application to complete the linkage.

Step 5: Advanced Verification via tea.yaml Configuration

In cases where OAuth is restricted by organizational security policies, you must verify your profile manually by inserting a metadata file directly into your codebase.

1. Create a file named tea.yaml in the root directory of your open-source project's primary branch.
2. Populate the file with your unique, tea-generated developer decentralized identifier (DID) and signature string, which is provided to you on the manual verification screen of the web application.
3. Commit this file to your main branch and push the changes to GitHub.
4. Return to the tea app and click Verify Repository. The tea indexing engine will execute an automated pull request and file-check scan to validate the cryptographic presence of your DID.

Warning: Never share the private keys or recovery phrases of the Web3 wallet connected to your tea profile. The verification protocol will only ever ask you to sign a message or upload a public YAML file; it will never require your private credentials.

Step 6: Verifying Presence on the Social Tea App

If your search is not related to software development but rather to the viral social networking mobile application known colloquially as "Tea" (or "The Tea"), the verification process follows a consumer-focused path:

1. Download the official Tea application from the Apple App Store or Google Play Store.
2. Launch the application and enter your primary mobile phone number during the initialization phase.
3. If an account already exists under your number, the app will prompt you for a password reset or display your active profile dashboard immediately, confirming your presence in the system.
4. To check if other users have posted about you or mentioned you within the app's anonymous feeds, use the in-app search directory to input your full name, high school or university affiliation, or social media handles.

Verification Parameters and Profile Metrics

The following comparison table outlines the technical specifications, input protocols, and distinct verification pathways available when checking your presence on both developer and social platforms associated with the "Tea" naming convention.

Verification Failures and System Resolutions

During the lookup and claim process, database mismatches or sync errors can sometimes occur. Below are the most common real-world failure scenarios along with the precise technical remedies to resolve them.

• Scenario 1: GitHub username searches return zero results despite holding active public repositories

  
  
  
  • Root Cause: The tea crawler has not yet indexed your specific package registry (such as npm or PyPI) or your GitHub repository has fewer than the minimum star count or dependency linkages required to trigger automatic ingestion.
  • Actionable Fix: Force an on-demand index of your project. Navigate to the manual project registration page within the tea dashboard, input your repository URL directly, and click Request Index. The system will queue your repository for parsing, typically completing the process within 24 to 48 hours.

• Scenario 2: The profile is found but the claim process fails with an "OAuth Scope Error"

  
  
  
  • Root Cause: Your GitHub organization has active third-party application restrictions that block the tea protocol from validating your repository access.
  • Actionable Fix: Go to your personal GitHub settings, navigate to Applications, and select the Authorized OAuth Apps tab. Find the tea application and request organization access approval from your administrator, or complete the manual tea.yaml verification method to bypass OAuth entirely.

• Scenario 3: The tea.yaml file is committed but the platform cannot verify ownership

  
  
  
  • Root Cause: The YAML syntax is malformed, the file is placed in a subfolder instead of the absolute root directory, or a content delivery network (CDN) cache is serving an outdated version of your repository to the crawler.
  • Actionable Fix: Ensure the file name is precisely lowercase (tea.yaml) and located at the absolute root of your default branch. Use a YAML validator to confirm there are no tab spacing errors, then clear any proxy caches and click Re-verify on the tea dashboard.

Frequently Asked Questions

How does the tea app get my GitHub information without my permission?

The tea developer protocol operates by index-scraping public, open-source software registries and public GitHub repositories. Because this data is published under open licenses (such as MIT, Apache 2.0, or BSD) and is accessible via public APIs, the platform aggregates this information to construct a global dependency graph. No private repository data is ever accessed or displayed without explicit authorization.

Is there a financial fee to claim my developer profile on the tea protocol?

No, claiming your profile and verified packages on the tea protocol is completely free of charge. The claim process utilizes off-chain cryptographic signatures or standard OAuth mechanisms, meaning you do not need to pay blockchain gas fees or connect a funded wallet simply to verify your identity on the dashboard.

Can I remove my packages and profile from the tea app database?

Yes. If you do not wish to participate in the tea protocol, you can remove your indexed profile by completing the ownership verification process first to establish your authority over the identity. Once verified, navigate to your profile settings menu, select the Privacy tab, and click Opt-Out of Indexing to hide your profile and associated statistics from public search results.

What is the tea Rank and how does it affect my profile visibility?

The tea Rank is an algorithmic score calculated using an eigenvector centrality model, similar to the PageRank algorithm used by search engines. It evaluates the entire open-source ecosystem to determine how critical your code is based on how many other projects depend on it. A higher tea Rank increases your profile's visibility and eligibility for protocol rewards.

How do I check if my phone number is registered on the social Tea app?

To check your status on the social Tea app, download the app on a mobile device and enter your phone number on the login screen. If the application prompts you to enter a pre-existing password or sends a verification code to log into an established profile, your number is already registered in their database.

Secure Your Developer Identity

Now that you know how to locate your profile, protect your open-source contributions from unauthorized claims by securing your identity on the network. Visit the official tea dashboard today to verify your tea Rank, claim your packages, and join the decentralized developer ecosystem.