AgentStack
SKILL verified MIT Self-run

Upgrade Impact

skill-sebs-claude-ecosystems-skills-upgrade-impact · by sebs

>

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-sebs-claude-ecosystems-skills-upgrade-impact

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Upgrade Impact? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Upgrade Impact Analysis

Before bumping a dependency, show what the new version drags in and what new risk (if any) it introduces.

Tooling

ecosystems CLI with --format json and --mailto "$ECOSYSTEMS_MAILTO" for polite-pool access (email configurable via the ECOSYSTEMS_MAILTO env var; a harmless no-op if unset). The resolve and diff jobs are async — pass --polling-interval 1 to block until done.

Step 1 — Resolve both versions' dependency trees

Resolve the dependency tree for the current and target version (registry is the second positional arg, e.g. npm, pypi, rubygems):

ecosystems resolve create_job   --version "" --polling-interval 1 --format json
ecosystems resolve create_job   --version ""  --polling-interval 1 --format json

--version accepts a range (e.g. "^4.18.0"). --before resolves the tree as it would have looked at a past date — useful for reproducing an old build.

Step 2 — Diff the two trees

Compare the resolved sets to find added / removed / changed transitive deps. You can diff the two resolve outputs directly, or, for source archives, use:

ecosystems diff create_job "" "" --polling-interval 1 --format json

Step 3 — Re-check risk on what changed

For every newly added or version-changed dependency in the diff:

# New advisories pulled in?
ecosystems advisories lookup_advisories_by_purl --purl "pkg:/@" --format json

# License change on a bumped dep?
ecosystems packages get_registry_package --purl "pkg:/" --format json

Report

| Change | Package | From → To | New advisory? | License change? | |---|---|---|---|---| | added / removed / bumped | | | | |

Lead with the verdict: safe / review / risky, justified by the worst item found (new critical advisory, new copyleft license, large transitive expansion). Quantify the tree delta (e.g. "+12 transitive deps, 1 new high-severity advisory"). Hand off to [[dep-audit]] for a full vulnerability pass if the change is large.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.