Introduction

UnRepo is a repository verification and analysis platform.

It establishes technical trust in open-source codebases. It has a strong focus on Web3 ecosystems.

UnRepo helps you understand what a repository represents beneath the surface. It explains structure, behavior over time, and claim alignment.

Modern Web3 repos are often reused or rapidly assembled. Some repos are partially automated or intentionally obfuscated. Surface-level inspection becomes unreliable.

UnRepo addresses this with structured, repeatable analysis. It highlights technical signals, not opinions.

When you see UnRepo in this documentation, keep the casing exact.

Quick start

Use the app for interactive analysis. Use the SDK for automation.

Open the Application Read the Documentation

Open the Dashboard Install the SDK

Who this is for

• Developers doing due diligence on dependencies or upstream repos.

• Web3 teams validating integrations, forks, or “claimed” codebases.

• Researchers comparing behavior across versions and time.

• Traders and community members needing fast, evidence-based context.

What you get

• Evidence you can cite. It is derived from repo data.

• Explainable outputs. You can trace why a score changed.

• Repeatable runs. Compare versions, forks, and time windows.

• Automation paths. Use UI, export, or API workflows.

What UnRepo is (and is not)

• Infrastructure, not an advisory product.

• Neutral analysis, not endorsements.

• Evidence-based outputs, not speculation.

What “verification” means in UnRepo

Verification means “can the repository’s claims be supported by observable data.”

Claims can be technical (tests exist) or behavioral (active maintenance).

1

Foundations

Start with platform principles and constraints. Go to Platform Foundations.

2

Architecture

Understand layers and responsibilities. Go to System Architecture.

3

Flow and engine

Learn the user journey and analysis pipeline. Go to Application Flow and Analysis Engine.

Read this documentation in order

Start with Access Modes for details.

Token verification unlocks advanced functionality. It helps keep the platform sustainable. It also respects privacy and avoids friction.

UnRepo supports Solana wallet authentication and GitHub authentication. Each path has clearly defined capabilities.

Access paths

What “signals” means here

Signals are measurable indicators from repository data. They come from structure, history, and patterns in code.

flowchart LR
  A[GitHub URL] --> B[Repository intake]
  B --> C[Code parsing]
  C --> D[Signal evaluation]
  D --> E[Scoring + report]
  E --> F[UI / Export / API]
  F --> G[Chat explanations]

UnRepo turns repository data into explainable findings and scores. Each stage is isolated for safety and repeatability.

How UnRepo works (high level)

You provide a GitHub repository URL. UnRepo runs a deterministic pipeline.

1. Intake normalizes the repository and metadata.

2. Parsing builds an internal model of the codebase.

3. Signals are computed from structure and history.

4. Scoring aggregates signals into a consistent report.

5. Delivery exposes results in UI, exports, and integrations.

Outputs focus on “what changed” and “why it matters.” They avoid subjective takes.

Trust and safety

Only use official domains and channels. Avoid lookalike links.

See Official Links.