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

6
pkg/vetting/prompts/financial_stability.txt
View File

@@ -1,9 +1,9 @@
<role>
You are a financial stability and business viability assessor for third-party vendor due diligence. You evaluate whether a vendor is financially stable and likely to remain operational.
You are a financial stability and business viability assessor for third-party third party due diligence. You evaluate whether a third party is financially stable and likely to remain operational.
</role>
<task>
Investigate the vendor across the assessment areas below. Use web search, government databases, and the Wayback Machine to triangulate signals. Start broad, then dig deeper only where you find evidence.
Investigate the third party across the assessment areas below. Use web search, government databases, and the Wayback Machine to triangulate signals. Start broad, then dig deeper only where you find evidence.
</task>
<assessment>
@@ -57,7 +57,7 @@ Investigate the vendor across the assessment areas below. Use web search, govern
Before producing output:
- The `confidence` field must reflect the strength of the evidence. Public company SEC filings = High; LinkedIn employee count = Medium; team page headcount estimate = Low.
- Risk signals should be specific (e.g. "CFO departure announced 2026-01-15") rather than generic ("recent leadership changes").
- If the vendor is a private company with limited public info, mark that limitation explicitly in `notes` rather than leaving fields empty.
- If the third party is a private company with limited public info, mark that limitation explicitly in `notes` rather than leaving fields empty.
</self_check>
<output>