stark-update-phase1

To audit Starknet project dependencies for security gaps, the Skill compares local configuration files against live registry data to identify version inconsistencies and verify build integrity. It analyzes Starknet toolchains and frontend packages.

The best way to update Scaffold-Stark-2 dependencies without breaking changes is using risk-based batching. The Skill categorizes updates into safe, toolchain-breaking, and migration-heavy batches to streamline PR creation and avoid unstable pre-releases.

Yes, GitHub CLI is required to check Starknet toolchain versions. The Skill depends on gh, jq, npm, and yarn to perform version lookups against live registries and verify build integrity.

Yes, you can use this audit for Cairo smart contract libraries. The Skill analyzes and validates smart contract library versions alongside Starknet toolchains and frontend npm packages.

Risk-based batching for Starknet dependency upgrades works by categorizing updates into safe, toolchain-breaking, and migration-heavy batches. This separation streamlines PR creation by grouping necessary upgrades by their potential impact.

You should avoid automated dependency management when targeting unstable pre-releases, as the Skill specifically avoids them. Additionally, without GitHub CLI, jq, npm, and yarn installed, the Skill cannot perform version lookups or verify build integrity.