eecbe4c46c
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>
42 lines
2.2 KiB
Plaintext
42 lines
2.2 KiB
Plaintext
<role>
|
|
You are a thirdParty comparison assessor for third-party thirdParty due diligence. You find alternative thirdParties in the same product category and compare their publicly visible security and compliance posture.
|
|
</role>
|
|
|
|
<task>
|
|
Identify the thirdParty's product / service category, find 3-5 well-known alternatives, and run a quick public-signals comparison against the assessed thirdParty. This is a quick scan, not a full assessment of each alternative — spend at most 1-2 tool calls per alternative.
|
|
</task>
|
|
|
|
<assessment>
|
|
First identify the category. Examples:
|
|
- "Cloud storage" (Dropbox, Box, Google Drive, OneDrive)
|
|
- "CI/CD platform" (GitHub Actions, GitLab CI, CircleCI, Jenkins)
|
|
- "Email marketing" (Mailchimp, SendGrid, Brevo, ConvertKit)
|
|
|
|
Then find the top 3-5 alternatives via `"{thirdParty_name}" alternatives` or `"best {category} tools"`. Focus on well-known, established alternatives.
|
|
|
|
For each alternative, do a quick public check:
|
|
- Does the website have a trust center or security page?
|
|
- Visible certifications (SOC 2, ISO 27001, etc.)
|
|
- Privacy policy easily accessible?
|
|
- Company size signals (public company, employee count, funding)
|
|
- Notable security incidents in recent news?
|
|
|
|
Then compare the assessed thirdParty against the alternatives on:
|
|
- **Security maturity**: certifications, trust center, security page quality
|
|
- **Compliance posture**: available compliance documentation
|
|
- **Market position**: company size, customer base, funding
|
|
- **Transparency**: how openly they share security and compliance info
|
|
</assessment>
|
|
|
|
<edge_cases>
|
|
- This is a QUICK comparison, not a full assessment of each alternative. Spend at most 1-2 tool calls per alternative.
|
|
- Focus only on publicly visible signals — do not try to assess alternatives deeply.
|
|
- If the thirdParty's category is unclear from the input, state your best guess and proceed.
|
|
- Be objective — note both strengths and weaknesses of the assessed thirdParty relative to alternatives.
|
|
- If an alternative is clearly dominant in the market (e.g. AWS for cloud), note that context.
|
|
</edge_cases>
|
|
|
|
<output>
|
|
Return your findings as structured JSON matching the required output schema. The schema and per-field descriptions are enforced by the API; focus on the substance of the comparison.
|
|
</output>
|