Terms

The agreement

These terms are an agreement between you and Since.dev. You accept them by creating an account, requesting an API key, or using the service. If you do not agree, do not use it.

You must be at least 16 and legally able to enter a contract. If you are using Since.dev for an organisation, you confirm that you are authorised to bind it, and “you” means that organisation.

What the service does

Since.dev tracks what changes across software: package releases, deprecations and end-of-life dates in the registries it follows, and the APIs and AI models that providers publish. Each change is recorded with its source and the date it was read. That is tracking, and it covers the whole catalog.

It analyzes only what touches your code. When you connect a GitHub repository, send code or a manifest through the API or MCP, or scan a public repository, Since.dev finds the packages, APIs and models the code uses and matches them against what changed. Each impact shows the file, the line, the severity, the days left, the replacement and the source. On Team and up it can also open the fix as a pull request. Changes and impacts reach you in the app, over HTTP, through the MCP server, by email or as signed webhooks. AI helps check impact and write fixes.

Repository access and fix pull requests

Connecting a repository, or installing the GitHub App on it, authorizes Since.dev to read it and analyze it within the permissions you approved on GitHub. On Team and up, installing the App also lets Since.dev create branches and commits and open pull requests in the repositories you selected. Free shows impacts and opens none. You must have authority to grant that access and to let us process the contents of the repository.

Fixes are proposals for review. Since.dev builds each one and runs your project’s own checks with it in a single-use, isolated machine, then opens it as a pull request that is ready for review. Your code runs only in that machine, which is deleted when the fix ends. When Since.dev cannot build a repository, the pull request says it was not built before opening and leaves the check to your CI; with no CI, no pull request opens. Since.dev never merges or deploys a pull request and never changes branch protection, secrets or cloud resources. You remain responsible for reviewing the change, running your tests and deciding whether to merge. Passing those checks or your CI does not guarantee production safety. When no safe fix exists, the impact stays open with an explanation instead of a patch.

You can pause a repository, switch off a single change, dismiss an impact (which closes its pull request), remove the repository, or remove the App on GitHub. These stop new work. Work already in progress may finish. A removed repository can be restored for 30 days, and its data is deleted 30 days after removal. Pull requests and branches already on GitHub are yours, and closing or deleting them is up to you.

A comment on a pull request that Since.dev opened is read as an instruction for a revision. Comments on other pull requests are not.

The public scanner and the calendar

You can scan a public repository, and read the retirement calendar, without an account. A scan reads only public code. Its result is about public facts, may be incomplete, and is shown to anyone with the link. Scans are limited per visitor per day. Do not get around the limit, for example by spoofing your address.

What Since.dev does not promise

This section is the important one.

• It is not exhaustive. Coverage is limited to the registries, APIs and models Since.dev follows, and to the languages it can read. Dynamic calls, generated code and unsupported languages can hide a use. A coverage gap is shown as a gap, never as a clean result.
• Silence is not a guarantee. Hearing nothing means no impact was found in what was read. It does not prove that every source was checked, that your code is unaffected or that nothing changed. Inspect the coverage shown with a result before drawing conclusions.
• It is not instant. Registries, feeds and provider pages are read on a schedule, and analysis follows. A change can reach you after it ships upstream.
• Webhook delivery is at-least-once. The same change may reach you more than once. Every delivery carries a stable idempotency key so that you can deduplicate, and you are expected to.
• Unknown is not unchanged. An answer of unknown, or an impact marked as needing review, means Since.dev could not settle the question. Treating it as confirmation is the most expensive mistake you can make with this service, and it is your responsibility not to.
• Sources can fail. Registries, feeds, and pages change structure, go down, and restrict automated access. When that happens the gap is shown. A failure is never reported as “no change”.
• Dates and replacements are the provider’s. A retirement date, a replacement or a migration path comes from the provider’s own publication, and providers change them. Check the cited source before you rely on a deadline.
• AI answers and fixes can be wrong. Since.dev uses AI to check impact and to write and review fixes. Each cites its evidence, but a citation is not a guarantee of accuracy, and a fix can be incomplete or incorrect.
• It is not advice. Nothing Since.dev sends is legal, medical, investment, or professional advice.

Do not rely on Since.dev as the sole safeguard for a decision with legal deadlines, safety consequences, or irreversible effects. Keep a second check on anything that matters that much.

Acceptable use

You agree not to use Since.dev:

• to connect, scan or send code you are not authorized to access or share;
• to bypass a paywall, login, or access control; this does not prohibit connecting accounts and resources you are authorized to access through the supported integrations;
• to get around a plan limit, a scanner limit or a rate limit, including by holding multiple accounts, spoofing your address or sharing keys;
• to bulk copy, resell, redistribute or republish the catalog or other data retrieved through the service, or to build a substantially similar competing service from it;
• to probe, overload, or interfere with the service, or to break the law or infringe anyone’s rights.

This does not limit what you may do with third-party data under its own open license, such as security advisories published under CC BY 4.0.

Since.dev may refuse requests that fall inside these categories and may suspend an account for misuse, whatever the stated purpose.

Your account and your keys

The app, the API and MCP use the same credits and plan limits. API keys belong to a workspace. An MCP client you approve acts in one workspace with the access you gave it, and you can disconnect it from the API keys page at any time.

Keep your credentials and API keys secret. A Since API key is shown once and only a one-way hash of it is stored, so we cannot recover one for you, but you can revoke and replace a key at any time. You are responsible for everything done with your keys, including by an agent you operate. Tell us promptly at support@since.dev if you suspect unauthorised access. Webhook destinations are yours: what you do with the notices we send there is your responsibility.

Plans, limits, and billing

• Paid plans are billed in advance through Stripe, monthly or yearly as you choose. A yearly plan costs 10 months of the monthly price. Every billing period ends at noon UTC on the 1st of a month, when the monthly allowances reset. Your first charge for a plan covers the days from the purchase until the 1st, and the full price is charged on the 1st after that, each month on a monthly plan and each year on a yearly one. The current price and the amount due today are shown at checkout before you agree to them. Fees exclude taxes, which are added where they apply.
• An Enterprise plan is governed by its signed agreement wherever that agreement and these terms differ.
• Every plan includes credits and fix pull requests each month. Credits are 1,000 on Free, 25,000 on Team, 150,000 on Business and 500,000 on Platform. Fix pull requests are 25 a month on Team, 100 on Business and 250 on Platform; Free opens none. These monthly allowances reset at noon UTC on the 1st and do not roll over, on a monthly plan and on a yearly plan alike. Credits are the one meter for the API and MCP: reading changes and checking code each cost a fixed number of credits, listed on the pricing page and in Billing. A fix pull request counts as one of the month’s fix pull requests when it opens, not as credits. Webhooks and the repository list cost no credits, and a call that fails uses none. The first paid month of the workspace your account starts with includes the full allowances of the plan it bought, however late in the month it was bought. Every other month, in that workspace and in any additional workspace, has the allowances of every plan the workspace was on, weighted by how long it was on each, so a plan taken part-way through a month includes a share of that month’s allowances.
• Past the month’s allowances, a paid workspace can use a prepaid balance. The owner of a paid workspace adds to it in Billing, from $10 to $2,000 at a time in steps of $1, and pays through Stripe. The balance counts once Stripe confirms the payment. An extra fix pull request costs $2 and extra credits cost $2 per 1,000, taken from the balance. The balance is used only after the month’s included fix pull requests and credits, and nothing is billed after the fact. Each purchase expires 12 months after it was bought, the purchase that expires first is used first, and balance that has expired is lost. A balance belongs to the workspace it was added to and stays when the workspace moves to a lower plan. If a purchase is refunded or disputed, the matching balance is removed. When the month’s credits and the balance cannot pay for a call in full, the API answers HTTP 402 with the error code credits_exhausted and charges nothing, and a fix pull request waits until the month resets or a balance is added. Free cannot add a balance, so a Free workspace stops when its credits run out, until the 1st or a plan change. If Stripe marks the subscription unpaid, the workspace moves to Free. We email the workspace owner when the included credits run out. Rates and allowances may change with notice under these terms.
• Plans limit private repositories, the providers a workspace follows and workspace members. Public repositories are unlimited on every plan. Free shows the impact of each change and does not open fix pull requests; Team and up do. Beyond your plan price, the only charge is a prepaid balance you choose to add. Webhook deliveries and their retries are never metered or billed.
• Free includes 1 private repository and up to 5 providers. Team includes 25 private repositories and up to 50 providers. Business has unlimited private repositories, every provider and the impact API. Platform has unlimited private repositories, up to providers and the impact API.
• Billing shows your credits left, your prepaid balance and the date the month resets.
• Rate limits protect the service and the sources it reads. Sustained excess may be throttled. Talk to us before you need a higher limit rather than after.
• Your login includes one Free owned workspace. Each additional owned workspace requires its own paid subscription. Joining an invited team does not use your Free workspace. Checkout applies to the selected workspace.
• You can change plan, switch between monthly and yearly, or cancel at any time in Billing or the billing portal. A change to a higher plan applies at once, and you pay the difference for the rest of the period, unless it moves from yearly to monthly. A switch from monthly to yearly on the same plan also applies at once. Any other change, such as a lower plan or a switch from yearly to monthly, takes effect at the end of the period you have paid for; until then you keep the current plan and its allowances, and you can undo the change in Billing. A cancellation also takes effect at the end of the month or year you have paid for, and we do not refund partial periods except where the law requires it. Downgrading changes future limits and never deletes your history. A cancellation or a late payment does not change the month’s allowances or your prepaid balance. If you delete a workspace, or the account that owns it, its subscription is cancelled and its billing record and saved cards are deleted. Nothing is invoiced or refunded, the unused part of the period is not credited, and any unused prepaid balance is lost with the workspace. If usage exceeds the applicable private repository, provider or member limits, analysis and fix pull requests pause until you reduce usage or choose a suitable plan. Saved data and cleanup controls remain available. An additional workspace without a paid subscription retains saved-data access and cleanup controls while analysis and fix pull requests stay paused.
• Paying or upgrading does not clear a pause you set on a repository.
• Quotas and prices may change with notice. Material reductions or increases will be announced by email before they take effect, and you may cancel rather than accept them.
• The free tier is offered as-is, may change, and may be withdrawn. We will give notice before withdrawing it.

Your content

You keep ownership of your content, including your code, the snippets, manifests and lockfiles you send, and your instructions on pull requests. You grant Since.dev the licence needed to operate the service for you, which is to read and analyze your repositories, send the code needed to check impact and write fixes to our AI provider, keep the findings, open pull requests, and deliver results to your chosen destinations. Our AI provider processes that code under its commercial terms with us, as the privacy policy describes. What we keep, and for how long, is described in our privacy policy. We do not train models on your content.

Shared answers. When a question about a public change is made only of public facts (the package, the function or class, public argument names and public values), Since.dev may reuse its answer for every workspace. A shared answer never contains your code, file paths or names, and where an answer came from is never shown. A workspace owner can opt out in Settings. The privacy policy says what goes in and what comes out.

Source content

Changes and notices quote short factual excerpts from public sources and link to the original. Rights in that material remain with the publisher. Since.dev is a change tracker, not a content republisher, and your use of quoted material is your responsibility. Data a source publishes under an open license stays under that license, and the sources page lists the attribution each one requires.

Availability and changes to the service

We aim for high availability but do not guarantee uninterrupted operation. Maintenance, source outages, and upstream rate limits can delay checks. We may add, change, or remove features. Where a change removes something you depend on, we will give reasonable notice through the API changelog or by email.

Warranties

The service is provided “as is” and “as available”. To the maximum extent permitted by law, Since.dev disclaims all implied warranties, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the service will be uninterrupted, error free, or that it will detect any particular change or find every use of it. Some jurisdictions do not allow these exclusions, in which case they do not apply to you.

Liability

To the maximum extent permitted by law, Since.dev is not liable for indirect, incidental, special, or consequential loss, for lost profits or revenue, or for any loss arising from a change Since.dev did not detect, did not classify as material, or did not deliver, or from a fix you merged or a date you relied on. Our total liability in any twelve-month period is limited to the amount you paid us in that period. Nothing here excludes liability for fraud, death or personal injury caused by negligence, or anything else that cannot lawfully be excluded.

Indemnity

You will indemnify Since.dev against claims, losses, and reasonable costs arising from your use of the service in breach of these terms, in particular a breach of the acceptable-use section.

Termination

You may close your account at any time from Settings. Sign-in stops at once, and your account and its data are deleted 30 days after removal; until then you can ask us to restore it. We may suspend or terminate an account that breaches these terms, with notice where that is practical and immediately where the service is being harmed. On termination your right to use the service ends; the sections on content, liability, indemnity, and governing law survive.

Governing law and disputes

These terms are governed by the laws of the State of Delaware, United States, without regard to its conflict-of-laws rules, and the courts of that jurisdiction have exclusive jurisdiction over any dispute.

If you are a consumer, these terms do not deprive you of the protection of the mandatory law of the country where you live, or of the right to bring proceedings there.

Before filing anything, write to legal@since.dev. Most disputes are a misunderstanding about coverage, and we would rather fix it than argue about it.

General

• Entire agreement. These terms and the privacy policy are the whole agreement between us about the service, except where a separately signed order form, services agreement or data-processing agreement applies. Those documents govern their agreed subject matter and any expressly stated precedence.
• Severability. If a provision is unenforceable, the rest stands.
• No waiver. Not enforcing a term once does not waive it.
• Assignment. You may not assign these terms without our consent. We may assign them to a successor in a merger or sale of the business, on notice to you.
• Force majeure. Neither party is liable for a failure caused by something outside its reasonable control.
• Notices. We contact you at the email address on your account. You contact us at the addresses on this page.

Changes to these terms

Material changes will be announced by email before they take effect, and the date at the top of this page will change. Continuing to use the service after that is acceptance. If you do not accept a change, cancel before it takes effect. Legal questions: legal@since.dev.