AI builders digest — monitors top AI builders on X and YouTube podcasts, remixes their content into digestible summaries. Follow builders, not influencers.
This report summarizes scanner evidence for zarazhangrui/follow-builders, a JavaScript project with 6,863 GitHub stars. SynthScan examined 3,349 lines of code across 21 source files, recording 33 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 14.6 (Moderate pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Can maintainers explain intent, assumptions, and trade-offs? 33 finding(s).
Are imports declared and package/API names verified? 0 finding(s).
Are wrappers, guards, and repeated structures necessary? 3 finding(s).
Which changes need focused human review? 33 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 33 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | SKILL.md | 41 | ### Step 1: Introduction | COMMENT |
| LOW | SKILL.md | 55 | ### Step 2: Delivery Preferences | COMMENT |
| LOW | SKILL.md | 66 | ### Step 3: Delivery Method | COMMENT |
| LOW | SKILL.md | 116 | ### Step 4: Language | COMMENT |
| LOW | SKILL.md | 123 | ### Step 5: API Keys | COMMENT |
| LOW⚡ | SKILL.md | 148 | ### Step 6: Show Sources | COMMENT |
| LOW⚡ | SKILL.md | 156 | ### Step 7: Configuration Reminder | COMMENT |
| LOW⚡ | SKILL.md | 166 | ### Step 8: Set Up Cron | COMMENT |
| LOW | SKILL.md | 279 | ### Step 9: Welcome Digest | COMMENT |
| LOW | SKILL.md | 311 | ### Step 1: Load Config | COMMENT |
| LOW | SKILL.md | 315 | ### Step 2: Run the prepare script | COMMENT |
| LOW | SKILL.md | 335 | ### Step 3: Check for content | COMMENT |
| LOW | SKILL.md | 340 | ### Step 4: Remix content | COMMENT |
| LOW | SKILL.md | 368 | ### Step 5: Apply language | COMMENT |
| LOW | SKILL.md | 396 | ### Step 6: Deliver | COMMENT |
| LOW | scripts/generate-feed.js | 384 | // Step 1: Discover episodes from each podcast's RSS feed | COMMENT |
| LOW | scripts/generate-feed.js | 441 | // Step 2: Filter by lookback window, sort newest first | COMMENT |
| LOW | scripts/generate-feed.js | 458 | // Step 3: Try each candidate until we get a transcript from pod2txt | COMMENT |
| LOW | scripts/generate-feed.js | 899 | // Step 1: Discover articles from the blog index page | COMMENT |
| LOW | scripts/generate-feed.js | 918 | // Step 2: Filter to unseen articles, cap at MAX_ARTICLES_PER_BLOG. | COMMENT |
| LOW | scripts/generate-feed.js | 944 | // Step 3: Fetch full article content for each new article | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | scripts/generate-feed.js | 384 | // Step 1: Discover episodes from each podcast's RSS feed | COMMENT |
| LOW | scripts/generate-feed.js | 441 | // Step 2: Filter by lookback window, sort newest first | COMMENT |
| LOW | scripts/generate-feed.js | 458 | // Step 3: Try each candidate until we get a transcript from pod2txt | COMMENT |
| LOW | scripts/generate-feed.js | 899 | // Step 1: Discover articles from the blog index page | COMMENT |
| LOW | scripts/generate-feed.js | 918 | // Step 2: Filter to unseen articles, cap at MAX_ARTICLES_PER_BLOG. | COMMENT |
| LOW | scripts/generate-feed.js | 944 | // Step 3: Fetch full article content for each new article | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | scripts/generate-feed.js | 668 | function parseAnthropicEngineeringIndex(html) { | CODE |
| LOW | scripts/generate-feed.js | 745 | function extractAnthropicArticleContent(html) { | CODE |
| LOW | scripts/generate-feed.js | 811 | function extractClaudeBlogArticleContent(html) { | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | scripts/generate-feed.js | 1 | #!/usr/bin/env node | COMMENT |
| LOW | scripts/deliver.js | 1 | #!/usr/bin/env node | COMMENT |
| LOW | scripts/prepare-digest.js | 1 | #!/usr/bin/env node | COMMENT |