Guide — 10 minutes, once

Put your AI-built project on GitHub

fnvibes reads your code from GitHub — it's the safest way for you to grant (and revoke) access. If your project only lives in Cursor, Lovable, Bolt or a folder on your laptop, this guide gets it onto GitHub even if you've never touched git. Private repos are completely fine.

01 Create a GitHub account

If you don't have one: go to github.com/signup — free, two minutes. GitHub is where most of the world's code lives; your AI-built app deserves a proper home too.

02 Get your code onto GitHub

Pick the path that matches where your project lives:

Lovable, Replit or v0 — use the built-in sync

These tools connect to GitHub for you. In Lovable: open your project → GitHub → “Connect to GitHub” and it creates and syncs the repo. In Replit: Tools → Git → connect GitHub and push. In v0: use the “Add to codebase” / export options, then follow the local-folder path below. Done? Skip to step 3.

Cursor, Claude Code, or any local folder

Your code is on your machine, so you'll push it up once. First create an empty repo at github.com/new (pick “Private” if you want — don't add a README, keep it empty). Then, in your project folder's terminal:

git init
git add .
git commit -m "first commit"

Then connect it to the repo you just created (swap in your username and repo name from the page GitHub shows you):

git remote add origin https://github.com/YOUR-USERNAME/your-app.git
git branch -M main
git push -u origin main

Refresh the GitHub page — your code is there. From now on, git add . && git commit -m "update" && git push publishes new changes. (Or ask your AI assistant to do it — Cursor and Claude Code both handle git happily.)

Bolt or other export-only tools

Download/export your project as a zip, unzip it into a folder, then follow the local-folder instructions above from that folder.

Before you push: make sure your .env file (API keys, database passwords) is listed in .gitignore so it never goes to GitHub. If you're not sure, ask your AI: “add .env to .gitignore and make sure no secrets are committed.” Our analyzer checks for leaked secrets — it's the #1 thing we catch.

03 Connect it to fnvibes

Sign in with GitHub → “Connect a repo” → pick your repo. You're choosing exactly which repos we can read — read-only, revocable anytime from GitHub's side. Your free 0–100 fnScore is ready about a minute later, with a breakdown of what to fix.

Repo's on GitHub? You're one click away.

Connect it and get your honest 0–100 score in about a minute.