feat(typescript-recipes): add vendor intelligence recipe#51
Merged
zhengchaol merged 13 commits intoJul 14, 2026
Conversation
16 tasks
georgeatparallel
marked this pull request as ready for review
July 10, 2026 21:27
zhengchaol
approved these changes
Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
This PR adds a local TypeScript recipe for researching vendor risk and keeping the result current with Parallel.
It has three commands:
bootstrapresearches each vendor, applies a deterministic risk policy, and starts a snapshot Monitor.check-updatesreads new Monitor events and runs focused follow-up research when a change crosses the review threshold.cleanupcancels the Monitors recorded in local state.The README explains what each command does, when it consumes credits, what a successful result looks like, and how to recover after an interrupted command. The implementation uses the current TypeScript SDK and V1 Monitor API.
Why it is local
The earlier version in #37 combined n8n workflows, a TypeScript layer, and a hosted Next.js/Supabase app. That gave readers several implementations of the same workflow and a lot of infrastructure to set up.
This version keeps one implementation and one local state file. A reader needs Node.js and a Parallel API key; there is no database, frontend, webhook, or deployment step. Because there is no hosted demo, the Cookbook now supports
websiteUrl: nulland hides the Demo button for verified local recipes.This PR supersedes #37 and keeps Sahith's attribution in the Cookbook registry.
Try it
The normal checks do not call the Parallel API:
cd typescript-recipes/parallel-vendor-intelligence npm ci npm run validate npm audit --audit-level=highTo use the recipe, copy
.env.exampleto.env, addPARALLEL_API_KEY, and run:The opt-in live test consumes credits. It researches Cloudflare, creates a snapshot Monitor, checks for updates, cancels every Monitor it created, and confirms the remote status:
Verified
coreTask andliteMonitor lifecycle, including confirmed cancellation.