Dependency monitoring
Know what's falling behind, before it breaks.
Every day Versyka checks your repositories for vulnerable packages, outdated API SDKs and retiring AI models, and turns each one into a tested pull request when you say so.
How monitoring works
Daily scan
Once a day, Versyka reads the manifests and lock files in each covered repository on GitHub or GitLab (package.json, requirements files, pyproject.toml, go.mod, Maven and Gradle), including projects in subfolders, and the code for AI model IDs. Nothing is cloned for this.
What it finds
Packages with known vulnerabilities (from OSV.dev), API SDKs that are major versions behind or deprecated, and AI models that are retired or retiring within 90 days. Each shows its evidence: the advisories, the release notes or the shutdown date.
You choose what to fix
In your dashboard, tick what to fix and review it, with the cost, before anything starts. Versyka upgrades, updates the code where needed, runs your tests before and after, and opens a pull request.
What a morning's scan looks like
- Vulnerable
requests 2.25.13 advisories from OSV.dev, fixed in 2.32.4Version bump - Major behind
openai 0.28.1Latest is 1.x; the chat API changed shapeMigration - Retiring
gpt-4-0613Called in 3 files; shuts down within 90 daysMigration - Fixed
lodash 4.17.15Pull request merged, alert clearedDone
What to know
40 API vendors
Stripe, OpenAI, Anthropic, AWS, Twilio and more.See every vendorSkips what you ignore
Anything underConfigurationpackages.ignorein.versyka.ymlis left alone.Alerts, then your go-ahead
Email, Slack and a weekly summary tell you what was found. Nothing is fixed until you tick it in your dashboard.Reads manifests only
Just dependency files and .versyka.yml, through the GitHub app.How access works
Check one repository now
The free upgrade check runs the same lookup on a manifest you paste. No account, nothing stored.