Dependency Migration Check — verified upgrade risk avatar

Dependency Migration Check — verified upgrade risk

Pricing

Pay per usage

Go to Apify Store
Dependency Migration Check — verified upgrade risk

Dependency Migration Check — verified upgrade risk

For every pinned dependency in a requirements.txt: how far behind it is and which execution-verified breaking changes sit in the upgrade path (LibPulse corpus).

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Shinobu Otani

Shinobu Otani

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Dependency Migration Check

Audit a pinned requirements.txt: for every pkg==version pin, how far behind the latest release it is, and which execution-verified breaking changes (LibPulse corpus) sit in the upgrade path.

Input

{"requirements": "numpy==1.26.4\nrequests==2.31.0"}

Output

One item per pin: latest, behind, verified_breaking_count, verified_breaking_changes (with before/after migration snippets), corpus_covered.

Use it to prioritize dependency upgrades by actual migration cost instead of version distance.