Contact shellmap
shellmap is a small static reference site. We read every message but we're a low-headcount project — please be patient and please be specific.
The fastest way to reach us is email:
hello@shellmap.eversources.app
Plain text is welcome. Code snippets are welcome. Screenshots are welcome. Please put the command or page URL in the subject line so we can triage quickly.
Report an inaccuracy
shellmap covers 227 commands and 176 task pages across five shells. Some of those equivalents will have edge cases we missed — flag-renames in a new util-linux release, a PowerShell 7 vs 5.1 divergence we got backwards, a macOS BSD vs GNU mismatch on a coreutils flag.
When you write in, please include:
- The page URL (e.g.
/cmd/grep). - The shell + version where the snippet misbehaves (
bash --version,$PSVersionTable). - The OS / distro (
uname -a,sw_vers,winver). - What the snippet does on your machine vs what the page claims.
Request a task page
If you searched for a shell-task answer and landed on a competitor because shellmap didn't have it, that's the most useful signal we can get. Tell us the search query you typed and the closest existing task page (if any), and it goes on the build list.
Embedding & the embed API
The widget at /embed-demo is documented end-to-end. If you're hitting a CSP rejection, a shadow-DOM styling clash, or you want to embed shellmap inside a larger documentation toolchain (Docusaurus, MkDocs, MDX), email us with the host page URL and the rendered output so we can repro quickly.
Licensing & partnerships
Want to mirror a slice of the catalog inside an internal developer portal, ship a shellmap-flavoured cheatsheet at a conference, or partner on shell-tooling content? The terms of use covers the default boundary; email us for anything beyond it.
What we can't help with
A few things are outside scope — sending them in just adds latency to the things we can answer:
- Free one-on-one scripting help— we don't debug your specific pipeline. Stack Overflow, the shell's tag on Reddit, and the project's own GitHub Discussions are better venues for that.
- Security-emergency advice— if a command on shellmap matches an active incident on your side, call your usual security responder; don't wait on email.
- Generic SEO / link-building outreach— we don't exchange links, and we don't accept sponsored content for the command corpus. Editorial integrity is the whole value prop.
Related
- About shellmap — why the site exists and how the content is built.
- Privacy policy — what we store on your device and who touches your traffic.
- Terms of use — what you can and can't do with shellmap content.