present our findings from our SLSA compliance review of Vitess. SLSA is a framework for assessing artifact integrity and ensure a secure supply chain for downstream users. In this part of the audit, we Provenance - Non-falsifiable ⛔ ⛔ Provenance - Dependencies complete ⛔ Provenance - Identifies artifact ⛔ ⛔ ⛔ ⛔ Provenance - Identifies builder ⛔ ⛔ ⛔ ⛔ Provenance - Identifies build instructions ⛔ ⛔

migration tools gh-ost and pt-online-schema-change create artifact tables or end with leftover tables: Vitess automatically collects those tables. The artifact or leftover tables are immediate moved to purge state operation can be dangerous in production as it commonly locks the buffer pool for a substantial period. Artifact tables are identifiable via SELECT artifacts FROM _vt.schema_migrations in a VExec command, see

migration tools gh-ost and pt-online-schema-change create artifact tables or end with leftover tables: Vitess automatically collects those tables. The artifact or leftover tables are immediate moved to purge state operation can be dangerous in production as it commonly locks the buffer pool for a substantial period. Artifact tables are identifiable via SELECT artifacts FROM _vt.schema_migrations in a VExec command, see

migration tools gh-ost and pt-online-schema-change create artifact tables or end with leftover tables: Vitess automatically collects those tables. The artifact or leftover tables are immediate moved to purge state a migration completes (either successful or failed). You will normally not need to do anything. Artifact tables are identifiable via SELECT artifacts FROM _vt.schema_migrations in a VExec command, see

migration tools gh-ost and pt-online-schema-change create artifact tables or end with leftover tables: Vitess automatically collects those tables. The artifact or leftover tables are immediate moved to purge state a migration completes (either successful or failed). You will normally not need to do anything. Artifact tables are identifiable via SELECT artifacts FROM _vt.schema_migrations in a VExec command, see

a migration completes (either successful or failed). You will normally not need to do anything. Artifact tables are identifiable via SELECT artifacts FROM _vt.schema_migrations in a VExec command, see migration tools gh-ost and pt-online-schema-change create artifact tables or end with leftover tables: Vitess automatically collects those tables. The artifact or leftover tables are immediate moved to purge state