✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Greptile Summary

Increases the PKI Sync name field length to 256 characters to match secret syncs, resolving a discrepancy where the DB column was limited to 32 chars, destination-specific Zod schemas allowed 64, and the base schema/frontend allowed 255. All layers (DB migration, backend Zod schemas across 6 destination types + base schema, and frontend form validation) are now consistently set to 256. Frontend UI components are also updated to handle longer names gracefully with CSS truncation.

• DB migration alters the name column on PkiSync table from 32 to 256 characters
• All 6 destination-specific backend schemas (Create/Update) updated from max(64) to max(256)
• Base PkiSyncSchema updated from max(255) to max(256)
• Frontend form schema updated from max(255) to max(256)
• UI components add truncate, min-w-0, and shrink-0 CSS classes to handle long name overflow

Confidence Score: 4/5

• This PR is safe to merge — it's a straightforward column size increase with consistent schema updates across all layers.
• The changes are simple and mechanical: increasing a name field length limit from various inconsistent values to a uniform 256 across DB, backend schemas, and frontend. All destination-specific schemas are updated consistently. The migration is guarded with a hasTable check. Frontend UI changes properly handle longer names with CSS truncation. No security concerns, no breaking API changes, no logic changes.
• No files require special attention. The migration file is the only one worth a quick review to confirm it runs cleanly in your environment.

Important Files Changed

_{Last reviewed commit: cd6f48f}