Since.dev
Catch breaking changes, deprecations, security advisories and retiring AI models in your dependencies before they break your code, and get the fix: file and line, days left, the pull request.
- Brand
- Since.dev
- Category
- Pending
- Primary Subcategory
- CI/CD & Internal Developer Platforms
Integration details
Description
Your code depends on thousands of things that keep changing. Packages ship breaking major versions, AI models retire on fixed dates, APIs drop fields, and runtimes reach end of life. Since.dev tracks every one of those changes at the source and tells your agent exactly what breaks in your code, when, and how to fix it. What it covers: - Packages: every package in 18 registries, including npm, PyPI, Maven Central, Go modules, crates.io, RubyGems, NuGet, Packagist, Docker Hub, Homebrew and Terraform, with breaking changes, deprecations and security advisories. - AI models: deprecation and retirement dates for OpenAI, Anthropic, Google Gemini and Mistral models on each platform that serves them (the provider's API, Azure, Amazon Bedrock, Vertex AI), with the replacement. - APIs: removed endpoints, new required fields and other breaking changes in the API specs it follows. - Runtimes and CI: end-of-life dates for Node.js, Python, Java, .NET, PHP, Ruby and hundreds more, plus Kubernetes API removals and GitHub Actions runner changes. Three tools: - whats_changed: the changelog for any package, model, API or runtime since a date, a version or your model's training cutoff, and what retires soon. - check_code: checks a model ID, a package version, a snippet, a manifest, a lockfile or a public GitHub repo, and returns what's affected, the file and line, the severity, the days left and what to move to. Anything it can't settle comes back as needs review, never as fine. - fix_code: returns the patch for a snippet, or opens fix pull requests on a connected GitHub repository, each checked before it opens. Nothing merges until a person reviews it. Use it before an upgrade or a migration, to find deprecated model IDs, to review security advisories in your dependencies, or to catch up on what changed since your model was trained. Sign in with your browser, no API key needed. Lookups and checks work on the free plan.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- CI/CD & Internal Developer Platforms
- Secondary Subcategories
- None listed
- Brand
- Since.dev
- Access
- Account required
- First tracked
- 2026-11-05
- Tool count
- 3
- Market
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competing in Claude CI/CD & Internal Developer Platforms
View Category3 tools agents can invoke
Since.dev Claude Connector FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Since.dev's Claude Connector discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Since.dev alternatives on Claude?
As of 2026-11-06, Since.dev competes with Datadog, Grafana Cloud, CircleCI, incident.io, Coralogix, PagerDuty, mcp.betterstack.com, Vercel and 14 more in Claude CI/CD & Internal Developer Platforms, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.


