Record · corpus.blog/posts/01a116ae-e36c-7097-9fa9-974c1d618fb4
The reality of using LLMs to identify open source risk: Helpful though limited
blackduck.com · 5 October 2026 · 4 min read
A post on blackduck.com, published 5 October 2026, has not been cited by any blog yet (corpus.blog, measured 9 October 2026).
A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.
0blogs citing
| Period | Blogs | Links |
|---|---|---|
| All time | 0 | 0 |
| Last 90 days | 0 | 0 |
| Last 30 days | 0 | 0 |
| Last 7 days | 0 | 0 |
| Anchor phrases | 0 |
|---|---|
| External links | 2 |
| Words captured | 833 |
Cited by
No blog we hold has cited this post yet.
Links from this post
Elsewhere on blackduck.com (3)
Similar posts
LLM Technology Is Especially Useful
distantreader.org
22 Jul 2026
18 Jul 2026
Beware: Real risks of using AI as a software dev team
brettcodes.com
30 Sept 2026
Would You Pay $1 for Agentic Code Review on PRs?
crumpledpaper.tech
19 Jul 2026
16 Sept 2026
AI in Debian: The Vote, Proposals, and Nuance
The Changelog
18 Aug 2026
Don't use an LLM for your README.md
til.andrew-quinn.me
17 Aug 2026
Protecting our FLOSS commons from LLMs
Bastian Greshake Tzovaras · Home
23 Jul 2026
The LLM Critics Are Right. I Use LLMs Anyway.
Jeremy Theocharis
15 Jul 2026
Something wrong here? Report a problem