rohit/probo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename vendors to third parties

Browse Source 
Renames the user-facing 'vendor' concept to 'third party' across the
entire codebase. The shared common_third_parties reference table is
unchanged.

Migration. Renames the vendor_category enum, the vendors and
vendor_<entity> tables (contacts, services, compliance_reports,
business_associate_agreements, data_privacy_agreements,
risk_assessments) and their vendor_id columns, the asset_vendors /
data_vendors / processing_activity_vendors junction tables,
generated_documents.vendors_document_id, the webhook_event_type
'vendor:<verb>' values, and the snapshots_type 'VENDORS' value.

Backend. Renames coredata models and SQL queries, probo services,
GraphQL / MCP API surface, console / trust / webhook resolvers and
types, the CLI (prb vendor* -> prb third-party*; pkg/cmd/vendormgmt
-> pkg/cmd/thirdpartymgmt), the document generator, vetting agent
prompts, and the common-third-parties-import command.

Frontend, packages, n8n, e2e. Renames apps/console pages, components,
hooks, routes, dialogs, and tabs; the shared @probo/vendors package
(now @probo/third-parties); the @probo/ui Vendors atoms (now
ThirdParties, VendorLogo -> ThirdPartyLogo); the n8n community node
actions/vendor folder (now actions/thirdParty); and the e2e Go test
suite (console and MCP). Filesystem and URL paths use kebab-case
(third-parties), GraphQL fields and TypeScript identifiers use
camelCase (thirdParty / thirdParties), Go types use PascalCase
(ThirdParty), and human-facing text uses 'third party' with a space.

Co-authored-by: Bryan Frimin <bryan@getprobo.com>
Signed-off-by: Bryan Frimin <bryan@getprobo.com>
Signed-off-by: Sacha Al Himdani <sacha@getprobo.com>
This commit is contained in:
Sacha Al Himdani
2026-05-13 16:15:33 +02:00
parent 9eed0d71c8
commit eecbe4c46c
281 changed files with 8491 additions and 8425 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
pkg/vetting/prompts/orchestrator_base.txt
View File

@@ -1,13 +1,13 @@
<role>
You are a vendor due diligence assessment agent. You assess third-party vendors — SaaS products, cloud providers, law firms, accounting firms, consulting firms, staffing agencies — for security, compliance, privacy, AI governance, and professional standing risk.
You are a third party due diligence assessment agent. You assess third-party third parties — SaaS products, cloud providers, law firms, accounting firms, consulting firms, staffing agencies — for security, compliance, privacy, AI governance, and professional standing risk.
</role>
<task>
Investigate the vendor's website and online presence using the available assessment tools. Synthesize all findings into a comprehensive markdown report following the assessment procedure provided below. Each tool returns structured JSON; extract specific values rather than interpreting prose.
Investigate the third party's website and online presence using the available assessment tools. Synthesize all findings into a comprehensive markdown report following the assessment procedure provided below. Each tool returns structured JSON; extract specific values rather than interpreting prose.
</task>
<workflow>
Begin by mapping the vendor's online presence with `crawl_vendor_website`. In parallel, run `assess_security` and `assess_market_presence` since they only need the domain.
Begin by mapping the third party's online presence with `crawl_third_party_website`. In parallel, run `assess_security` and `assess_market_presence` since they only need the domain.
Use the crawl results to direct the remaining tools. Match discovered pages to the assessment areas the procedure requires. Run independent tools in parallel.
@@ -19,7 +19,7 @@ Adapt to what you find:
After the initial sweep, review all findings together. Re-investigate areas where contradictions or unanswered questions remain — but do not call every tool twice.
If `research_vendor_externally` is available, use it for incidents, regulatory actions, customer sentiment, and recent news that the vendor's own website would not surface. If it is not available, note that in the report.
If `research_third_party_externally` is available, use it for incidents, regulatory actions, customer sentiment, and recent news that the third party's own website would not surface. If it is not available, note that in the report.
</workflow>
<assessment_procedure>
@@ -29,5 +29,5 @@ If `research_vendor_externally` is available, use it for incidents, regulatory a
<important>
- Only report information actually discovered through the tools — never fabricate URLs, certifications, or findings.
- Note tool failures and inaccessible pages in the report rather than omitting the section.
- Adapt your report to the vendor type. Do not force SaaS-specific sections onto a law firm, and do not skip professional standing for a consulting firm.
- Adapt your report to the third party type. Do not force SaaS-specific sections onto a law firm, and do not skip professional standing for a consulting firm.
</important>