WeSearch

CodeCrucible: A blueprint for LLM-driven SAST

Clinton Carpene, Alex Rosenzweig, Andrew Kitis· ·16 min read · 0 reactions · 0 comments · 1 view
#codecrucible#blueprint#llm-driven#sast
CodeCrucible: A blueprint for LLM-driven SAST
TL;DR · WeSearch summary

~/posts/codecrucible-a-blueprint-for-llm-driven-sast...$ cd .. That release is not really why this post exists. "LLM-driven SAST" is an established category, and this particular tool will probably age.

Key facts
About this source

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

Original article
Block Engineering Blog · Clinton Carpene, Alex Rosenzweig, Andrew Kitis
Read full at Block Engineering Blog →
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 publisherBlock Engineering Blog
Canonical URLhttps://engineering.block.xyz/blog/codecrucible-a-blueprint-for-llm-driven-sast
Publication timeWed, 29 Jul 2026 08:53:51 +0000
Retrieval time2026-07-29T09:01:01.371Z
Last seen2026-07-29T09:01:01.371Z
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.
Cluster4TCV1UZz5Dse · 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

~/posts/codecrucible-a-blueprint-for-llm-driven-sast...$ cd .. EngineeringJuly 1, 2026CodeCrucible: A blueprint for LLM-driven SASTHow we built a whole-repo AI security scanner and the tradeoffs that made it useful$ git blameCommit HashAuthorSocials0002e49Clinton Carpene00034d0Alex Rosenzweig00025fcAndrew Kitis$ cat content.mdToday we're releasing CodeCrucible, a new LLM-driven static application security testing (SAST) tool for vulnerability discovery. That release is not really why this post exists. "LLM-driven SAST" is an established category, and this particular tool will probably age. What will last longer is the blueprint: the design choices, tradeoffs, and reference codebase that let other teams adapt the approach to their own pipelines and keep iterating on it.

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

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

Discussion

0 comments