EXC Analyzer

1 GitHub Authentication

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

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.

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.

3 Dork Scan

This command runs a targeted public-code scan and returns matched repository paths with direct GitHub links.

1) Scan starts

[INFO] Searching GitHub for: brgkdm
Searching GitHub ... |

This stage confirms the query target and shows that the scanner has started communicating with GitHub. The trailing spinner-like symbol indicates active progress while results are being collected.

2) Matched results list

[INFO] Searching GitHub for: brgkdm

[+] brgkdm/DayZen-good-first-issue | README.md
    -> https://github.com/brgkdm/DayZen-good-first-issue/blob/5b4f3323d7c21e974053871ab3e280e790ec9c8e/README.md

[+] exc-analyzer/exc | pyproject.toml
    -> https://github.com/exc-analyzer/exc/blob/09e8af4183ac3dfd192598cc8e62f238b3032a2d/pyproject.toml

[+] sarpaltinok/Hisse-Senedi-Analizi-Projesi | README_EN.md
    -> https://github.com/sarpaltinok/Hisse-Senedi-Analizi-Projesi/blob/9e1d552e0b20dd3e4a1268db67e17e4e121f4d4c/README_EN.md

[+] brgkdm/special-bank | Docs/usage.md
    -> https://github.com/brgkdm/special-bank/blob/ca7b14aafc020dd24988efa60d656622cc7a8f51/Docs/usage.md

[+] szabgab/pydigger-data-1 | data/pypi/ex/exc-analyzer.json
    -> https://github.com/szabgab/pydigger-data-1/blob/1f76d45dccf65d94edf-b8fc596157ec738c9efb/data/pypi/ex/exc-analyzer.json

Each hit contains three key elements: repository identifier, matched file path, and a direct immutable blob URL. This makes verification straightforward and allows fast triage of where and why the query matched.

3) Final summary and warning

[INFO] Total shown: 10
[WARNING] Use responsibly. You are legally and ethically responsible for the results of this scan.

The summary line shows how many matches were printed to the console. The warning line is a compliance reminder: always validate findings, respect platform policies, and only use results within legal and ethical boundaries.

Open Full README