WeSearch
Show HN: Soothsay - Your AI types curl | sh. soothsay checks the script first

Show HN: Soothsay - Your AI types curl | sh. soothsay checks the script first

·11 min read · 0 reactions · 0 comments · 6 views
More from GitHub ai Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

🔮 soothsay Read the omens before you curl | sh. soothsay reads a shell install script and tells you, in plain English, what it's about to do to your machine before you run it. Why this exists In 2026 almost every developer tool installs the same way: curl -fsSL https://<some-ai-cli>.dev/install.sh | bash Coding agents, runtimes, package managers and language toolchains all do it. You're handing a stranger's 2,000-line shell script a root-capable terminal.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 7,248 of its stories.

Original article
GitHub
Read full at GitHub →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherGitHub
Canonical URLhttps://github.com/rijuld/soothsay
Publication timeFri, 02 Oct 2026 00:04:39 +0000
Retrieval time2026-10-02T00:22:54.808Z
Last seen2026-10-02T00:22:54.808Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Clusterq0MU0G629T5r · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

🔮 soothsay Read the omens before you curl | sh. soothsay reads a shell install script and tells you, in plain English, what it's about to do to your machine before you run it. As a Claude Code hook, it also stops AI coding agents from piping installers into your shell until you've seen what they do. curl -fsSL https://example.com/install.sh | soothsay Guard Claude Code (needs the soothsay binary, see Install): /plugin marketplace add rijuld/soothsay /plugin install soothsay@soothsay Claude's curl … | sh is then blocked, reviewed, pinned to the exact bytes, and put to you for approval. How it works.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub