Share your project

Measure any project on your own computer and get a public link for your resume, LinkedIn, or a message to a recruiter. Free, no account needed.

New here? Read the full guide for step-by-step help and the list of supported languages.

The quickest way — one command

Open a terminal inside your project folder and run this. It measures your project, shows you progress as it goes, and prints your link when it finishes. Nothing to upload.

npx --yes @archsetuweb/cli@latest share

  ████████████████████ 100%  Done

  Library Management System
  "Lets a college library issue books and track due dates."
    (from your README - change it with --about "...")
  Built with: Python, Flask, SQLite
  code: https://github.com/you/library-management

  Python · 24 files · 3,100 lines

  Your page is live:

  https://library-management.archsetu.com

Needs Node.js. Nothing is installed permanently and you do not need administrator rights. Works with 47 languages and any editor. It reads your README and your git remote so the page says what you built, and prints both before publishing so nothing is a surprise.

Or do it in two steps, with a file

Use this if the one-line command does not work on your setup. Run this first:

npx --yes @archsetuweb/cli analyze --json > archsetu-report.json

Your terminal will look like nothing happened. That is correct. Everything it measured went into a new file called archsetu-report.json in your project folder, next to your own code. It holds measurements only, never your code.

Then add the file it made

Open your project folder and look for archsetu-report.json. Drag it onto the box below, or click to browse. If you renamed it, that is fine. We check what is inside the file, not what it is called.

Drop archsetu-report.json here

What gets sent, and what does not

Your code is never sent. The measuring happens on your computer. We never see your source files.
Even the report file stays on your computer. Your browser reads it and sends only the small set of numbers your page shows, such as file counts and languages — plus the description and links you typed above.
Security findings are never published. If the analysis noticed a password or key in your code, that stays in your file and never reaches us.
Your page says the numbers are self-reported. You ran the analysis, so we say so honestly rather than pretending we checked it.
Your link is private until you share it. It cannot be guessed and search engines are told not to list it.