Crates.io | what-the-port |
lib.rs | what-the-port |
version | |
source | src |
created_at | 2024-06-05 10:58:02.674541 |
updated_at | 2024-12-11 08:02:59.835362 |
description | Quickly lookup what a port is used for. |
homepage | |
repository | https://github.com/cyqsimon/what-the-port |
max_upload_size | |
id | 1262650 |
Cargo.toml error: | TOML parse error at line 19, column 1 | 19 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
Quickly lookup what a port is used for or what port to use.
This tool is very new, so it hasn't been packaged in many places.
If you would like to help package it, please do so and submit an issue/PR so we can list it here.
paru -S what-the-port
cargo install what-the-port
In essence, this program is a scraper + parser that takes the information in the excellent Wikipedia page List of TCP and UDP port numbers and presents it after formatting the data. There is really nothing special about it.
The main sell, as is the case for many CLI tools, is that of convenience. Instead of having to open up a browser, navigate to the page and scroll or search, you can do it from the comfort of your terminal with one command. There is also the additional benefit that you can now do this lookup offline thanks to caching.
Of course, the intrinsic issue with any scraper is that it isn't particularly resilient. Wikipedia is intended for human consumption first and foremost, not for a program. I fully expect this tool to have issues regularly, when the Wikipedia page gets updated in an unhandled way. Therefore most aspects of this tool are written to be fail-safe, meaning it will try its best to produce usable output. If you encounter errors or warnings, please report them as issues.