# Changelog of npm Package Scraper — Downloads, Maintainers & Metadata (`haketa/npm-package-scraper`) Actor

- **URL**: https://apify.com/haketa/npm-package-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/haketa/npm-package-scraper.md

## Changelog

### 1.0.0 — 2026-11-01

- **Verified at scale:** a fresh run across 6 broad search terms (`react`, `cli`, `typescript`, `testing`, `logger`, `database`) returned **500 unique packages with 0 duplicates** in ~340s on datacenter proxy. Core-field coverage: `name`/`version`/`description`/`npmUrl`/`downloads`/`downloadPeriod`/`dependenciesCount`/`devDependenciesCount`/`maintainers`/`maintainerEmails`/`publisherUsername` and all four npm scores at **100%**; `license` 99.8%, `repository` 99.4%, `unpackedSize`/`fileCount` 99.4%, `homepage` 98%, `bugsUrl` 94%. The `keywords` (63%), `author` (53%) and `authorEmail` (27%) fields are data-dependent — only present when a package declares them.
- **Bug fix — repository URL normalization:** scheme-less repository values are now normalized to clean, clickable `https://` URLs. This covers SCP-style Git shorthand (`git@github.com:owner/repo`), npm provider shortcuts (`github:`/`gitlab:`/`bitbucket:`/`gist:`) and the bare GitHub shortcut (`owner/repo`). Previously these forms could leak into the `repository` field scheme-less (e.g. `git@github.com:formatjs/formatjs` and `formatjs/formatjs`), breaking the clickable link in the dataset view. All other forms (`git+https`, `git://`, `ssh://git@`, `.git` suffix) were already handled; unit-tested against 13 real variants with standard `https://` URLs left untouched.
- **README refresh:** rewrote the Output example and field reference against the real fresh-run sample, and corrected the score documentation — `popularityScore`/`qualityScore`/`maintenanceScore` are npm's 0–1 signals (currently saturated at `1` for most mainstream packages) and `finalScore` is npm's raw search-relevance score (higher = more prominent, not a 0–1 value), so you no longer see misleading 0–1 claims.
- No changes to input or output field names — fully backward compatible.
