How Verification Works

Verification Overview

Nexr verification exists to prove that a builder's work is authentic, active, and contains real technical depth. Unlike self-reported resumes, Nexr programmatically verifies projects directly at the source.

When a build is submitted, our backend initiates a series of automated pipelines that query public APIs, run structural code metrics, parse codebase structures, and execute semantic AI analysis to confirm the validity of the work.

Code & Repository Pipeline

For projects imported from GitHub, verification runs a multi-layered check to prove authorship and codebase complexity:

• API Integration: We query the GitHub REST API using authenticated OAuth tokens. We fetch repository details, language distribution metrics, full commit history, and public contributors list.
• Boilerplate & Size Checks: The pipeline checks the number of directories, files, and language distributions. Repositories with no code (e.g., empty readmes, single-file bookmarks, or pure configuration templates) are rejected.
• Structural Analysis: We extract and analyze the top-level folder tree, dependencies (from package.json or requirements.txt), and overall folder layout.
• AI Semantic Review: The file structure, README, package manifest, and metadata are analyzed by Gemini to generate an architectural description, assess test coverage, and output a technical confidence score.

Design Portfolio Pipeline

For design work hosted on platforms like Figma, Behance, and Dribbble, verification validates the layout and presence of actual work:

• Domain Allowlisting: Link validation checks that the URL belongs to recognized, authoritative design networks.
• Metadata Extraction: The parser fetches the page's Open Graph data, public titles, and creation info to verify the project isn't a blank draft or placeholder link.
• Semantic Check: AI evaluates the text, description length, and project descriptors to assess the scope of the design.

Video & Media Pipeline

For videos from YouTube, TikTok, and Vimeo, verification prevents duplicate theft and confirms ownership:

• Metadata Analysis: We extract the creator handle, views, publish timestamps, and description directly via oEmbed endpoints or platform-specific APIs.
• Social Attributing: The channel handle is matched against the builder's verified social profiles linked to their Nexr account.

Reverification & Rate Limits

Builders can request updates to their projects to reflect new progress:

• Quick Verify: Updates live stats like stars, forks, and the repository homepage link.
• Full Reverify: Re-runs the full codebase and AI parsing engine. This operation is rate-limited to 3 requests per 10 minutes per builder to prevent quota abuse.