Know what you are depending on

Rate a repository before you build on it, see what everyone else found, and say what you found.

Sign in with GitHub Look around first
Scroll Down

What it does

Every check reads public GitHub metadata through the documented API. Nothing here reads your code.

Security Score

A repository starts at 100 and loses points for a missing license, no issue tracker, no security policy, and a few more. Checks that cannot be read cost nothing.

Repository Analysis

Metadata, release cadence, contributor spread, workflow permissions. Enough to judge whether a project is maintained before you depend on it.

Secret Scanning

Finds keys left in recent commits, restricted to repositories you can push to. Your own code, your own leaks, yours to rotate.

Shared Findings

Publish a scan of a repository you maintain, dispute one you disagree with, and talk it over. Every published score carries the date it was computed.

Smart Rate-Limiting

Runs on your own GitHub quota, with automated pause and retry so a long audit does not die halfway through.

Localization

Infrastructure open to community support and ready for global expansion.

Use it in your browser

No install, no server of ours in the middle. Sign in with GitHub and scan from the page you are on.

Signing in

One button, GitHub handles it. The first time you sign in, your account here is created — there is no separate form to fill in and no password for us to hold.

What we ask for

Read-only access to your public profile. EXC cannot write to your repositories, open issues, or push code. You can revoke it from GitHub settings at any time.

Where the work happens

Scans run in your browser against GitHub's API on your own rate limit. Your code never reaches us, and we never receive your token.

Reading and scanning need no account. An account is what lets you publish a result, post, and follow. Publishing a scan of a repository is limited to repositories you can push to. By signing in you accept the Terms of Use and the Privacy Notice.

Install in Seconds

Choose your platform and start analyzing.

Should we interpret your request as a definitive commitment to download EXC Analyzer?
PS C:\> pip install exc-analyzer
user@linux:~$ sudo dpkg -i exc-analyzer_1.3.1-1_all.deb
user@linux:~$ sudo apt-get install -f
macbook:~ % brew install python3
macbook:~ % pip3 install exc-analyzer

System Requirements: Python 3.9+, pip/pipx, 500MB+ disk space.

Quick Start

Below you can find realistic command examples and sample CLI output.

1 GitHub Authentication

On first run, the CLI requests the access required for the tool to function. Follow the staged flow below.

exc login

1) Permission and consent prompt

- This tool requests access to repositories for ANALYSIS purposes only.
- IT DOES NOT PERFORM ANY WRITE, MODIFY, OR TRIGGER OPERATIONS.

- Permissions are managed by GitHub and can be revoked at any time.

Do you want to continue? (y/N):

Users can choose Y to continue or N to cancel. To proceed, select Y.

2) Device code and browser step

========================================
[ACTION] First copy your one-time code: 9A24-9C5C
========================================

URL: https://github.com/login/device

Press ENTER to open GitHub in your browser...

Press Enter to open GitHub automatically, or open the URL manually. On the opened page, enter the one-time code 9A24-9C5C to grant access.
Note: your one-time code will be different on your device; this is only a sample output.

3) Successful sign-in output

[SUCCESS] Authentication successful! Welcome, <username>.
Let's start the initial analysis using: exc analysis <owner/repo>.

4) Output when cancelled

[CANCELLED] Authentication cancelled by user.

Note: To revoke account access and sign out, use the exc logout command.

2 Repository Analysis

This command produces a structured analysis report in multiple stages, from repository metadata to completion status.

exc analysis torvalds/linux

1) Repository information

[*] Repository Information
Name          : torvalds/linux
Description   : Linux kernel source tree
Created At    : 04 Sep 2011 (14 years ago)
Last Updated  : 27 Feb 2026 (5 minutes ago)
Stars         : 219687
Forks         : 60665
Default Branch: master
License       : Other
Open Issues   : 0

This section gives the repository’s identity and activity baseline: project age, recent update time, popularity metrics, branch default, license type, and open issue count.

2) Language distribution

[*] Languages
  Makefile      : 0.20%
  C             : 97.97%
  Assembly      : 0.69%
  C++           : 0.01%
  Shell         : 0.40%
  Perl          : 0.08%
  Awk           : 0.01%
  Python        : 0.28%
  UnrealScript  : 0.00%
  Yacc          : 0.01%
  Lex           : 0.00%
  Gherkin       : 0.00%
  XS            : 0.00%
  Roff          : 0.01%
  Clojure       : 0.00%
  M4            : 0.00%
  sed           : 0.00%
  SmPL          : 0.01%
  MATLAB        : 0.00%
  Rust          : 0.32%

This part shows language composition by percentage. It helps identify the dominant implementation language and detect secondary tooling or build-script ecosystems.

3) Commit statistics (last 100)

[*] Commit Statistics (Last 100)
Analyzed Commits : 100

  Top Committers (in last 100)
  - torvalds      : 23 commits
  - tiwai         : 5 commits
  - kuba-moo      : 5 commits
  - gregkh        : 5 commits
  - airlied       : 4 commits

This snapshot focuses on short-term development momentum and author concentration. It is useful for understanding recent ownership and maintainership activity.

4) Contributors summary

[*] Contributors
Total Contributors: 0

This value reports the contributor count returned by the current query context. If it looks unexpected, re-run analysis or verify API scope and repository visibility.

5) Issues and pull requests

[*] Issues and Pull Requests
Open Issues   : 0
Total PRs     : 0

This section summarizes operational backlog signals. Open issue and PR totals provide a quick indicator of project load and review pipeline pressure.

6) Completion status

[INFO] Completed.

When this line appears, the analysis pipeline finished successfully and all prior blocks were generated without an interrupt.

Open Full README

For commands and detailed information, use the official README.

Open Full README