Repo Analyzer
Zero-dependency GitHub trust scorer. Runs 29 analysis modules across 12 scoring categories.
Usage
# Single repo
node scripts/analyze.js <owner/repo or github-url> [flags]
# From a tweet (auto-extracts GitHub links)
node scripts/analyze.js <x.com-or-twitter.com-url> [flags]
# Batch mode
node scripts/analyze.js --file <repos.txt> [--json]
Flags
--json — JSON output (for pipelines)--oneline — compact one-line score--badge — shields.io markdown badge--verbose — show progress--token <pat> — GitHub PAT (or set GITHUB_TOKEN env)--file <path> — batch mode, one repo per line (# comments ok)
Environment
CRITICAL: Always run with GITHUB_TOKEN loaded. Without it, scores are severely degraded (missing stars, forks, commits).
Before running: source ~/.bashrc (token is in ~/.bashrc as GITHUB_TOKEN).
Or pass explicitly: GITHUB_TOKEN="$(grep GITHUB_TOKEN ~/.bashrc | cut -d'"' -f2)" node scripts/analyze.js ...
Scoring (14 categories, 168pts normalized to 100)
| Category |
Max |
What it checks |
| Commit Health |
20 |
Human vs bot, GPG sigs, code dumps, fake timestamps |
| Contributors |
15 |
Bus factor, contributor diversity |
| Code Quality |
25 |
Tests, CI, license, docs, lock files |
| AI Authenticity |
15 |
AI slop detection in code/README |
| Social |
10 |
Stars, forks, star/fork ratio, botted stars |
| Activity |
10 |
Recent pushes, releases |
| Crypto Safety |
5 |
Token mints, rug patterns, wallet addresses |
| Dependency Audit |
10 |
Known malicious packages, typosquatting, install hooks, lock files |
| Fork Quality |
8 |
Fork divergence, suspicious changes, gutted vs meaningful forks |
| README Quality |
10 |
Install guide, examples, structure, API docs |
| Maintainability |
10 |
File sizes, nesting, code/doc ratio |
| Project Health |
10 |
Abandoned detection, velocity, issue response, PR review |
| Originality |
5 |
Copy-paste, template detection, backer verification |
| Agent Safety |
15 |
Install hooks, prompt injection, secrets, CI audit, permissions |
Grade Scale
- A (85+): LEGIT
- B (70-84): SOLID
- C (55-69): MIXED
- D (40-54): SKETCHY
- F (<40): AVOID
Key Features
- Enhanced dependency audit: Detects known malicious packages (event-stream, ua-parser-js, etc.), typosquatting attacks, install hooks, and estimates transitive dependency bloat
- Fork comparison: Analyzes fork divergence, detects cosmetic vs meaningful changes, flags suspicious modifications (removed CI, added wallets), identifies gutted forks
- Agent safety: Detects prompt injection, credential harvesting, install script hooks, obfuscated code
- Secrets detection: Finds hardcoded API keys, tokens, private keys via regex + entropy
- Network mapping: Categorizes all outbound domains (API, CDN, unknown)
- CI/CD audit: Checks GitHub Actions for pull_request_target, unpinned actions, secret leaks
- Permissions manifest: Summarizes what the code needs to run (like an app permissions list)
- Author reputation: Org memberships, suspicious repos, account age
- Backer verification: Cross-references investor claims vs committer org membership
- Complexity hotspots: Flags large files with deep nesting and high conditional density
Batch File Format
# One repo per line, # for comments
Uniswap/v3-core
https://github.com/aave/aave-v3-core
OpenZeppelin/openzeppelin-contracts
Output
Default: rich terminal report with bar charts, sections, verdict.
--json: Full structured data for programmatic use.
--oneline: RepoName: 85/100 [A] — 2 flags
When Reporting to User
Keep it concise. Lead with score/grade and notable findings. Skip sections with nothing interesting. Example:
"Uniswap/v3-core scored 75/B — 96% GPG-signed, 11 authors, MIT license. Flagged: abandoned (466 days no push), 2,597 transitive deps (bloated), secrets in CI run commands. Agent safety: CAUTION."
1---2name: repo-analyzer3description: GitHub repository trust scoring and due diligence. Use when asked to analyze, audit, score, or evaluate any GitHub repo — especially for crypto/DeFi project DD, checking if a repo is legit, evaluating code quality, verifying team credibility, or comparing multiple repos. Also handles X/Twitter URLs containing GitHub links — auto-extracts and analyzes repos from tweets. Triggers on "analyze this repo", "is this legit", "check this GitHub", "trust score", "audit this project", "repo quality", "batch scan repos", "analyze this tweet". ALSO auto-triggers when the user pastes an X/Twitter URL that contains a GitHub link — no explicit "analyze" command needed. When triggered by a tweet, ALWAYS include the tweet text/context above the analysis. Do NOT use for general GitHub browsing, reading READMEs, or cloning repos without analysis.4---5
6# Repo Analyzer
7
8Zero-dependency GitHub trust scorer. Runs 29 analysis modules across 12 scoring categories.
9
10## Usage
11
12```bash
13# Single repo
14node scripts/analyze.js <owner/repo or github-url> [flags]
15
16# From a tweet (auto-extracts GitHub links)
17node scripts/analyze.js <x.com-or-twitter.com-url> [flags]
18
19# Batch mode
20node scripts/analyze.js --file <repos.txt> [--json]
21```
22
23### Flags
24- `--json` — JSON output (for pipelines)
25- `--oneline` — compact one-line score
26- `--badge` — shields.io markdown badge
27- `--verbose` — show progress
28- `--token <pat>` — GitHub PAT (or set GITHUB_TOKEN env)
29- `--file <path>` — batch mode, one repo per line (# comments ok)
30
31### Environment
32**CRITICAL:** Always run with GITHUB_TOKEN loaded. Without it, scores are severely degraded (missing stars, forks, commits).
33Before running: `source ~/.bashrc` (token is in ~/.bashrc as GITHUB_TOKEN).
34Or pass explicitly: `GITHUB_TOKEN="$(grep GITHUB_TOKEN ~/.bashrc | cut -d'"' -f2)" node scripts/analyze.js ...`
35
36## Scoring (14 categories, 168pts normalized to 100)
37
38| Category | Max | What it checks |
39|----------|-----|----------------|
40| Commit Health | 20 | Human vs bot, GPG sigs, code dumps, fake timestamps |
41| Contributors | 15 | Bus factor, contributor diversity |
42| Code Quality | 25 | Tests, CI, license, docs, lock files |
43| AI Authenticity | 15 | AI slop detection in code/README |
44| Social | 10 | Stars, forks, star/fork ratio, botted stars |
45| Activity | 10 | Recent pushes, releases |
46| Crypto Safety | 5 | Token mints, rug patterns, wallet addresses |
47| Dependency Audit | 10 | Known malicious packages, typosquatting, install hooks, lock files |
48| Fork Quality | 8 | Fork divergence, suspicious changes, gutted vs meaningful forks |
49| README Quality | 10 | Install guide, examples, structure, API docs |
50| Maintainability | 10 | File sizes, nesting, code/doc ratio |
51| Project Health | 10 | Abandoned detection, velocity, issue response, PR review |
52| Originality | 5 | Copy-paste, template detection, backer verification |
53| Agent Safety | 15 | Install hooks, prompt injection, secrets, CI audit, permissions |
54
55## Grade Scale
56- A (85+): LEGIT
57- B (70-84): SOLID
58- C (55-69): MIXED
59- D (40-54): SKETCHY
60- F (<40): AVOID
61
62## Key Features
63- **Enhanced dependency audit**: Detects known malicious packages (event-stream, ua-parser-js, etc.), typosquatting attacks, install hooks, and estimates transitive dependency bloat
64- **Fork comparison**: Analyzes fork divergence, detects cosmetic vs meaningful changes, flags suspicious modifications (removed CI, added wallets), identifies gutted forks
65- **Agent safety**: Detects prompt injection, credential harvesting, install script hooks, obfuscated code
66- **Secrets detection**: Finds hardcoded API keys, tokens, private keys via regex + entropy
67- **Network mapping**: Categorizes all outbound domains (API, CDN, unknown)
68- **CI/CD audit**: Checks GitHub Actions for pull_request_target, unpinned actions, secret leaks
69- **Permissions manifest**: Summarizes what the code needs to run (like an app permissions list)
70- **Author reputation**: Org memberships, suspicious repos, account age
71- **Backer verification**: Cross-references investor claims vs committer org membership
72- **Complexity hotspots**: Flags large files with deep nesting and high conditional density
73
74## Batch File Format
75```
76# One repo per line, # for comments
77Uniswap/v3-core
78https://github.com/aave/aave-v3-core
79OpenZeppelin/openzeppelin-contracts
80```
81
82## Output
83Default: rich terminal report with bar charts, sections, verdict.
84`--json`: Full structured data for programmatic use.
85`--oneline`: `RepoName: 85/100 [A] — 2 flags`
86
87## When Reporting to User
88Keep it concise. Lead with score/grade and notable findings. Skip sections with nothing interesting. Example:
89
90"Uniswap/v3-core scored 75/B — 96% GPG-signed, 11 authors, MIT license. Flagged: abandoned (466 days no push), 2,597 transitive deps (bloated), secrets in CI run commands. Agent safety: CAUTION."
modbender