Skip to content
Back to the index

PortClash

visualstudio.comStatic analysis & linters

No liveness check has reached it yet; it is registered on the VS Code Marketplace and has been in the index since 13 Oct 2026. How this is checked

PortClash is a VS Code extension that scans project configuration for declared ports across Docker Compose, .env files, package scripts, dev servers, devcontainers, launch configurations, and Kubernetes. It flags duplicate assignments, publicly exposed databases, and macOS AirPlay conflicts for developers.

Inferred · not functionally tested

FreeWebWindowsmacOSLinux
Visit visualstudio.com

Overview

6 features

Purpose: Prevents development failures by identifying duplicate or risky port assignments before services and dev servers start.

Inferred · not functionally tested

Audience: software developers using VS Code

Inferred · not functionally tested

Functions: monitoring

Inferred · not functionally tested

Interfaces: API: unknown · MCP: unknown · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: free · license: Proprietary · platforms: WEB · deployment: browser, windows, macos, linux

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: unknown.

PortClash is a Static analysis & linters project. Inferred · not functionally tested: It prevents development failures by identifying duplicate or risky port assignments before services and dev servers start. Inferred · not functionally tested: It is built as a B2B product for software developers using VS Code. Basis unknown · not verified: PortClash costs nothing to use. Basis unknown · not verified: It ships for the web, Windows, macOS, and Linux.

Behind PortClash is jaytank_dev, and it first shipped in 2026. Inferred · not functionally tested: Key capabilities include port conflict detection, compose scanning, and .env scanning.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Port conflict detection
  • Compose scanning
  • .env scanning
  • Dev server scanning
  • Kubernetes scanning
  • Database exposure warnings

Topics: Inferred · not functionally tested

Tags
port-conflict-detectiondocker-composedevcontainerskubernetes-configeaddrinuse

JSON profile · Text profile · Access guide

Built with & integrations

Runs on
BrowserWindowsmacOSLinux

Trust & compliance

Public signals
HTTPSFree tierStore listing found

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed13 Oct · 03:16 UTC
    PortClash: Find Port Conflicts Across Compose, .env & Dev Servers seen via VS Code Marketplace
    Source: VS Code Marketplace · Open

Frequently asked questions about PortClash

What does PortClash do?
Inferred · not functionally tested: PortClash prevents development failures by identifying duplicate or risky port assignments before services and dev servers start. It is catalogued under Static analysis & linters on PulseGate.
Who is PortClash for?
Inferred · not functionally tested: PortClash is a B2B product built for software developers using VS Code.
Does PortClash have a free plan?
Basis unknown · not verified: Yes — PortClash is free to use.
What platforms does PortClash run on?
Basis unknown · not verified: PortClash runs on the web, Windows, macOS, and Linux.
Is PortClash still active?
Unverified. PortClash has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What projects are similar to PortClash?
Similar projects tracked by PulseGate include Codeberg / GitLab.com Anonymous Fetch Lint, ArangoDB Migration Check, and Apache ECharts Migration.Codeberg / GitLab.com Anonymous Fetch LintArangoDB Migration CheckApache ECharts Migration
Who develops PortClash?
PortClash is developed by jaytank_dev.
How long has PortClash been around?
PortClash first shipped in 2026.

Also in Static analysis & linters

Same category — not a similarity match