package-version-safety

Analyze Sui package upgrade risk via UpgradeCap ownership and governance.

276|56|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/PlamenTSV/plamen --skill package-version-safety
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: package-version-safety
Source: https://github.com/PlamenTSV/plamen/tree/main/agents/skills/sui/package-version-safety
Command: npx skills add https://github.com/PlamenTSV/plamen --skill package-version-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps auditors evaluate upgrade risk in Sui packages by analyzing UpgradeCap ownership, upgrade policies, and versioning across upgrades.

Core Features & Use Cases

  • Trigger Pattern analysis: detects PACKAGE_UPGRADE signals and related upgrade controls.
  • Upgrade policy inventory: identifies UpgradeCap location, holder, and governance model (single address vs multisig).
  • Version consistency checks: assesses cross-version object compatibility and migration safety across V1/V2 like scenarios.
  • Dependency and type checks: pins dependencies and verifies stable type definitions across upgrades.

Quick Start

Run a structured upgrade risk assessment on a Sui package by inspecting its UpgradeCap, migration logic, and version guards.

Frequently Asked Questions about package-version-safety

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess Sui package upgrade risk before deploying a new version?

Assess Sui package upgrade risk by evaluating UpgradeCap ownership, governance policies, and version guards. You must verify that dependencies are pinned and type definitions remain stable across versions to prevent unauthorized upgrades and state corruption.

What does UpgradeCap ownership analysis check during a Sui security audit?

UpgradeCap ownership analysis identifies the holder's location and governance model, checking whether a single address or multisig controls it. This determines if unauthorized parties can execute package upgrades and compromise the system.

How do I ensure migration safety and cross-version object compatibility in Sui packages?

Ensure migration safety by applying version consistency checks across multiple package versions. This process evaluates shared object compatibility and verifies that migration logic preserves state integrity when upgrading from V1 to V2 scenarios.

Can I detect unauthorized upgrade policies in Sui packages automatically?

Detect unauthorized upgrade policies by inventorying UpgradeCap settings and scanning for PACKAGE_UPGRADE signals. This identifies whether governance controls like multisig requirements are properly enforced before any package modifications occur.

What happens if dependencies are not pinned during a Sui package upgrade?

Unpinned dependencies during a Sui package upgrade risk state corruption and type instability. Verifying stable type definitions and pinned dependencies ensures cross-version compatibility and prevents unauthorized upgrades from breaking shared objects.