Repo brief: sindresorhus/get-port

Generated by RepoPilot · document generated 2026-09-17 · concise human review Evidence snapshot · analyzed 2026-09-17T03:58:02.957Z · commit efbebfb0a290

Verdict

Mixed — Slowing — last commit 6mo ago

• Last commit 6mo ago
• 21+ active contributors
• MIT licensed
• CI configured

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

get-port is a lightweight Node.js utility that finds and reserves available TCP ports for local use. It accepts preferred port preferences (single port or array), falls back to random assignment if unavailable, and optionally reserves ports for the process lifetime. The core capability is async port-discovery with intelligent fallback and in-process locking to prevent race conditions. Single-file ES module: index.js is the implementation, index.d.ts provides TypeScript types, test.js contains unit tests, and index.test-d.ts validates type definitions. No monorepo or complex structure—a tightly scoped utility.

Start here

Open these first:

• index.js — Main entry point implementing the core port-finding logic using Node.js net module to test port availability.
• index.d.ts — TypeScript type definitions for the public API (getPort function and portNumbers helper).
• package.json — Declares Node.js >=16 requirement, ES module configuration, and dev dependencies for testing (xo, ava, tsd).
• test.js — Functional test suite validating port selection, preferred ports, exclusions, and edge cases.
• readme.md — Documents the primary API surface, usage patterns (single port, array, range), and all configuration options.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/sindresorhus/get-port.git
cd get-port
npm install
npm test

Daily commands:

npm test

Runs three sequential checks: xo (linting), ava (unit tests), and tsd (type checking). No dev server—this is a library, not an application.

Key cautions & unknowns

• Slowing — last commit 6mo ago
• Concentrated ownership — top contributor handles 69% of recent commits
• No tests detected in the complete Git tree
• No hidden environment variables or external services required. However: (1) Port reservation via the reserve option locks ports globally by port number only—not by host/ipv6Only combination, so reserved ports are…
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.