# npm-original

> Which same/near-name npm package is the original? (not a typosquat scanner)

Homepage: https://dev.luling.xyz/npm-original/
JSON (browser JS): https://dev.luling.xyz/npm-original/?q=tsc-rs&format=json
Registry: https://dev.luling.xyz/npm-original/agents.json

## When to use

- User searches an npm name and sees scoped forks / clones ranked above the real package
- Need to separate: original vs GitHub-forked clones vs independent same-name projects

## When not to use

- Spelling-fuzz / typosquat enumeration (use a dedicated typosquat tool)
- Security malware scanning (Socket, Snyk, etc.)

## Judgment (short)

1. GitHub fork parent (strongest)
2. Same repo → same-project companion
3. Download order-of-magnitude
4. Repo ownership
5. Publish time is weak only
6. Label independent same-name separately