portless
Facilitates local development with named URLs, eliminating port conflicts and enhancing project organization.
Install this skill
or
79/100
Security score
The portless skill was audited on Jun 15, 2026 and we found 9 security issues across 2 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
medium line 93
Access to hidden dotfiles in home directory
SourceSKILL.md
| 93 | - **Port >= 1024** (no sudo): `~/.portless` |
medium line 18
Access to .env file
SourceSKILL.md
| 18 | - **Hardcoded ports in config** -- CORS allowlists, OAuth redirects, `.env` files break when ports change |
medium line 156
Access to .env file
SourceSKILL.md
| 156 | - **Custom servers**: read `process.env.PORT` and listen on it |
low line 3
External URL reference
SourceSKILL.md
| 3 | description: Set up and use portless for named local dev server URLs (e.g. http://myapp.localhost instead of http://localhost:3000). Use when integrating portless into a project, configuring dev serve |
low line 43
External URL reference
SourceSKILL.md
| 43 | # -> http://myapp.localhost:1355 |
low line 65
External URL reference
SourceSKILL.md
| 65 | portless myapp next dev # http://myapp.localhost:1355 |
low line 66
External URL reference
SourceSKILL.md
| 66 | portless api.myapp pnpm start # http://api.myapp.localhost:1355 |
low line 82
External URL reference
SourceSKILL.md
| 82 | 3. The browser hits `http://<name>.localhost:1355` on the proxy port; the proxy forwards to the app's assigned port |
low line 122
External URL reference
SourceSKILL.md
| 122 | | `portless <name> <cmd> [args...]` | Run app at `http://<name>.localhost:1355` (auto-starts proxy) | |
Scanned on Jun 15, 2026
View Security Dashboard