Rivvetch / permission check

Before we explore the code, let’s check the boundary.

Share a public GitHub repository you own or have permission to explore. Rivvetch checks the public endpoint for access and a visible license signal, then stores a bounded metadata preview for exploration.

Public does not mean permissionless. Your attestation stays part of the check.

A license signal is not legal advice. GitHub metadata can be incomplete.

Start with a repository URL
We check the public GitHub endpoint for access and visible license metadata, then save a bounded preview of the accepted repository for later exploration.

HTTPS links only. A trailing slash or .git suffix is okay.

GitHub’s public response cannot verify this attestation for you.

Three signals

A small check with a clear boundary.
  • 01URL format is checked before any network request.
  • 02Public access is verified through GitHub’s repository metadata.
  • 03Licensee-detected metadata must be visible for a pass.

We never fetch the submitted URL directly, inspect private code, or claim that a public API response proves legal permission.

What happens next

A successful check means the repository is publicly accessible and GitHub exposes detectable license metadata. The follow-up preview reads bounded README and license text, a directory projection, and supported package metadata. It does not prove ownership, authorization, or that every file is legally reusable.