since-dev 0.1.0__tar.gz

since_dev-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Since.dev
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

since_dev-0.1.0/PKG-INFO

@@ -0,0 +1,147 @@
+Metadata-Version: 2.4
+Name: since-dev
+Version: 0.1.0
+Summary: Find the code in a repository that is about to stop working: retired model IDs, runtimes past end of life, breaking dependency changes. Each with its date, its line and its replacement.
+Author-email: Nabil A <support@since.dev>
+License: MIT
+Project-URL: Homepage, https://since.dev
+Project-URL: Documentation, https://since.dev/docs#cli
+Project-URL: Source, https://github.com/Since-dev/cli
+Project-URL: Issues, https://github.com/Since-dev/cli/issues
+Keywords: deprecation,end-of-life,breaking-changes,dependencies,ai-models,mcp,cli,continuous-maintenance
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# since-dev
+
+Find the code in a repository that is about to stop working: AI model IDs with a shutdown date, runtimes past end of life, dependencies with security advisories or breaking releases. Every finding comes with its file and line, its date, its replacement and its source.
+
+```bash
+npx since-dev
+```
+
+Run it inside any repository. A public GitHub repository needs no sign-in and no setup.
+
+```
+  acme/shop  main@4f2c1d9  scanned just now
+  3 with a date   1 undated   214 dependencies and 96 files read
+  Read from GitHub (main), not your working tree.
+
+  20 days   claude-sonnet-4-5-20250929 on Claude API: retirement 2026-11-30
+            src/ai/client.ts:14  and 3 more   use claude-sonnet-5-5
+            https://platform.claude.com/docs/en/about-claude/model-deprecations
+
+  31 days   gpt-5 on OpenAI API: retirement 2026-12-11
+            src/ai/summarize.ts:8   use gpt-5.6-sol
+            https://developers.openai.com/api/docs/deprecations
+
+  passed    Node.js 20: end of life 2026-04-30
+            .github/workflows/ci.yml   use 24
+            https://endoflife.date/nodejs
+
+  Full report   https://since.dev/scan/acme/shop?utm_source=cli
+  Next          npx since-dev init   your coding agent checks before it writes
+```
+
+(An example for a made-up repository. The dates are the real ones as of November 10, 2026.)
+
+## Run it
+
+| With | Command |
+| --- | --- |
+| Node 18 or newer | `npx since-dev` |
+| uv | `uvx since-dev` |
+| pipx | `pipx run since-dev` |
+
+To keep it, `npm install -g since-dev` or `pip install since-dev` gives you the command `since`. The npm and PyPI packages are the same CLI: no dependencies in either, and one set of tests holds both to the same output, character for character.
+
+## Commands
+
+| Command | What it does |
+| --- | --- |
+| `since` | Checks the repository you are in. It reads the `origin` remote to know which one. |
+| `since <owner/repo>` | Checks any public GitHub repository. A GitHub URL works too. |
+| `since init` | Sets up your coding agent to check before it writes. See below. |
+| `since calendar` | What ends in the next 30 days: model retirements, runtime end of life, API removals. `--within 90d`, `--provider openai`. |
+| `since changed <package>` | Breaking changes and deprecations of a package. `--since 4.19.2` lists only what changed after that version, `--ecosystem pypi` picks the registry. Needs a key. |
+| `since check` | The same check for CI: exit 1 when a finding fails. See below. |
+| `since login`, `since logout` | Sign in for private repositories, and remove the stored key. |
+
+`--all` shows every finding (10 by default), `--json` prints the answer as JSON, `--within 30d` keeps only dates within that many days.
+
+Findings are listed with the next deadline first, then dates that have passed, then security advisories with no date, then the ones marked `review`: Since found the name in your code but could not prove the change reaches it.
+
+## Set up your coding agent
+
+Coding agents write the model IDs and versions that were current when they were trained. This makes yours check first:
+
+```bash
+npx since-dev init
+```
+
+It writes four files into the repository:
+
+| File | For |
+| --- | --- |
+| `.mcp.json` | Claude Code |
+| `.cursor/mcp.json` | Cursor |
+| `.vscode/mcp.json` | VS Code |
+| `AGENTS.md` | A short rule, between two markers, that tells any agent when to check |
+
+Commit them and everyone who clones the repository gets the same setup. No key goes in any file: the first tool call opens a sign-in in the browser.
+
+It only ever adds its own `since` entry. Other servers in those files stay as they are, a second run changes nothing, and a file it cannot read as plain JSON is left alone with the lines to add by hand. `--dry-run` shows what it would write.
+
+## What it sends
+
+- **A public GitHub repository:** only its name. Since reads the default branch from GitHub, so uncommitted work and other branches are not in the answer. It is free: 10 scans a day per address, and a scan is kept for an hour.
+- **A private repository, after `since login`:** if the repository is connected to your Since workspace and your plan includes it, the answer comes from there. Otherwise the CLI sends the manifests it finds in the folder (`package.json`, `requirements*.txt`, `pyproject.toml`, `go.mod`, `Cargo.toml`, `Gemfile`, `composer.json`, `pom.xml`, `build.gradle`, `*.csproj`), 10 at most unless you raise `--max-files`. Source files are never sent. Each manifest is one call to the API, which uses credits.
+- `--local` checks the manifests in the folder even when the repository is public, for work you have not pushed.
+
+## In CI
+
+```yaml
+- run: npx since-dev check --fail-on high
+  env:
+    SINCE_DEV_KEY: ${{ secrets.SINCE_DEV_KEY }}
+```
+
+With a key it checks the manifests of the checkout. Without one it reads the default branch of a public repository from GitHub, and says so.
+
+| Exit code | Meaning |
+| --- | --- |
+| 0 | Nothing proven at or above `--fail-on` (`low`, `medium`, `high` by default, `critical`, or `none`). |
+| 1 | At least one finding fails. A finding marked `review` never fails a run. |
+| 2 | Something for you to fix: a refused key, a bad option, no manifests. |
+
+If Since cannot be reached, or the free scans for the day are used up, the run passes with a note. An outage on our side never fails your build.
+
+On GitHub Actions, [since-dev/check](https://github.com/since-dev/check) does the same with annotations on the files and a table in the run summary.
+
+## Sign in
+
+```bash
+since login
+```
+
+It asks for your email, prints a link, and waits while you approve it in the browser. The key is stored in `~/.config/since/credentials.json`, readable only by you. Setting `SINCE_DEV_KEY` works as well and wins over the stored key. `since logout` removes the stored key.
+
+## Develop
+
+```bash
+node --test test.mjs
+python3 -m unittest test_cli
+```
+
+Each file in `fixtures/` is one run: the arguments, the folder, and the answers the API gives. `expected/` holds what that run prints, requests and writes. Both test suites replay every fixture and compare with the same expected file. After a change to the Node side, `UPDATE_EXPECTED=1 node --test test.mjs` rewrites the expected files: read the diff, then make the Python side match.
+
+## License
+
+MIT. The data comes from [Since.dev](https://since.dev): the [calendar](https://since.dev/calendar) of what ends when, and the [API](https://since.dev/docs) behind this CLI.

since_dev-0.1.0/README.md

@@ -0,0 +1,126 @@
+# since-dev
+
+Find the code in a repository that is about to stop working: AI model IDs with a shutdown date, runtimes past end of life, dependencies with security advisories or breaking releases. Every finding comes with its file and line, its date, its replacement and its source.
+
+```bash
+npx since-dev
+```
+
+Run it inside any repository. A public GitHub repository needs no sign-in and no setup.
+
+```
+  acme/shop  main@4f2c1d9  scanned just now
+  3 with a date   1 undated   214 dependencies and 96 files read
+  Read from GitHub (main), not your working tree.
+
+  20 days   claude-sonnet-4-5-20250929 on Claude API: retirement 2026-11-30
+            src/ai/client.ts:14  and 3 more   use claude-sonnet-5-5
+            https://platform.claude.com/docs/en/about-claude/model-deprecations
+
+  31 days   gpt-5 on OpenAI API: retirement 2026-12-11
+            src/ai/summarize.ts:8   use gpt-5.6-sol
+            https://developers.openai.com/api/docs/deprecations
+
+  passed    Node.js 20: end of life 2026-04-30
+            .github/workflows/ci.yml   use 24
+            https://endoflife.date/nodejs
+
+  Full report   https://since.dev/scan/acme/shop?utm_source=cli
+  Next          npx since-dev init   your coding agent checks before it writes
+```
+
+(An example for a made-up repository. The dates are the real ones as of November 10, 2026.)
+
+## Run it
+
+| With | Command |
+| --- | --- |
+| Node 18 or newer | `npx since-dev` |
+| uv | `uvx since-dev` |
+| pipx | `pipx run since-dev` |
+
+To keep it, `npm install -g since-dev` or `pip install since-dev` gives you the command `since`. The npm and PyPI packages are the same CLI: no dependencies in either, and one set of tests holds both to the same output, character for character.
+
+## Commands
+
+| Command | What it does |
+| --- | --- |
+| `since` | Checks the repository you are in. It reads the `origin` remote to know which one. |
+| `since <owner/repo>` | Checks any public GitHub repository. A GitHub URL works too. |
+| `since init` | Sets up your coding agent to check before it writes. See below. |
+| `since calendar` | What ends in the next 30 days: model retirements, runtime end of life, API removals. `--within 90d`, `--provider openai`. |
+| `since changed <package>` | Breaking changes and deprecations of a package. `--since 4.19.2` lists only what changed after that version, `--ecosystem pypi` picks the registry. Needs a key. |
+| `since check` | The same check for CI: exit 1 when a finding fails. See below. |
+| `since login`, `since logout` | Sign in for private repositories, and remove the stored key. |
+
+`--all` shows every finding (10 by default), `--json` prints the answer as JSON, `--within 30d` keeps only dates within that many days.
+
+Findings are listed with the next deadline first, then dates that have passed, then security advisories with no date, then the ones marked `review`: Since found the name in your code but could not prove the change reaches it.
+
+## Set up your coding agent
+
+Coding agents write the model IDs and versions that were current when they were trained. This makes yours check first:
+
+```bash
+npx since-dev init
+```
+
+It writes four files into the repository:
+
+| File | For |
+| --- | --- |
+| `.mcp.json` | Claude Code |
+| `.cursor/mcp.json` | Cursor |
+| `.vscode/mcp.json` | VS Code |
+| `AGENTS.md` | A short rule, between two markers, that tells any agent when to check |
+
+Commit them and everyone who clones the repository gets the same setup. No key goes in any file: the first tool call opens a sign-in in the browser.
+
+It only ever adds its own `since` entry. Other servers in those files stay as they are, a second run changes nothing, and a file it cannot read as plain JSON is left alone with the lines to add by hand. `--dry-run` shows what it would write.
+
+## What it sends
+
+- **A public GitHub repository:** only its name. Since reads the default branch from GitHub, so uncommitted work and other branches are not in the answer. It is free: 10 scans a day per address, and a scan is kept for an hour.
+- **A private repository, after `since login`:** if the repository is connected to your Since workspace and your plan includes it, the answer comes from there. Otherwise the CLI sends the manifests it finds in the folder (`package.json`, `requirements*.txt`, `pyproject.toml`, `go.mod`, `Cargo.toml`, `Gemfile`, `composer.json`, `pom.xml`, `build.gradle`, `*.csproj`), 10 at most unless you raise `--max-files`. Source files are never sent. Each manifest is one call to the API, which uses credits.
+- `--local` checks the manifests in the folder even when the repository is public, for work you have not pushed.
+
+## In CI
+
+```yaml
+- run: npx since-dev check --fail-on high
+  env:
+    SINCE_DEV_KEY: ${{ secrets.SINCE_DEV_KEY }}
+```
+
+With a key it checks the manifests of the checkout. Without one it reads the default branch of a public repository from GitHub, and says so.
+
+| Exit code | Meaning |
+| --- | --- |
+| 0 | Nothing proven at or above `--fail-on` (`low`, `medium`, `high` by default, `critical`, or `none`). |
+| 1 | At least one finding fails. A finding marked `review` never fails a run. |
+| 2 | Something for you to fix: a refused key, a bad option, no manifests. |
+
+If Since cannot be reached, or the free scans for the day are used up, the run passes with a note. An outage on our side never fails your build.
+
+On GitHub Actions, [since-dev/check](https://github.com/since-dev/check) does the same with annotations on the files and a table in the run summary.
+
+## Sign in
+
+```bash
+since login
+```
+
+It asks for your email, prints a link, and waits while you approve it in the browser. The key is stored in `~/.config/since/credentials.json`, readable only by you. Setting `SINCE_DEV_KEY` works as well and wins over the stored key. `since logout` removes the stored key.
+
+## Develop
+
+```bash
+node --test test.mjs
+python3 -m unittest test_cli
+```
+
+Each file in `fixtures/` is one run: the arguments, the folder, and the answers the API gives. `expected/` holds what that run prints, requests and writes. Both test suites replay every fixture and compare with the same expected file. After a change to the Node side, `UPDATE_EXPECTED=1 node --test test.mjs` rewrites the expected files: read the diff, then make the Python side match.
+
+## License
+
+MIT. The data comes from [Since.dev](https://since.dev): the [calendar](https://since.dev/calendar) of what ends when, and the [API](https://since.dev/docs) behind this CLI.

since_dev-0.1.0/pyproject.toml

@@ -0,0 +1,34 @@
+[build-system]
+requires = ["setuptools>=64"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "since-dev"
+version = "0.1.0"
+description = "Find the code in a repository that is about to stop working: retired model IDs, runtimes past end of life, breaking dependency changes. Each with its date, its line and its replacement."
+readme = "README.md"
+requires-python = ">=3.9"
+license = { text = "MIT" }
+authors = [{ name = "Nabil A", email = "support@since.dev" }]
+keywords = ["deprecation", "end-of-life", "breaking-changes", "dependencies", "ai-models", "mcp", "cli", "continuous-maintenance"]
+classifiers = [
+  "Environment :: Console",
+  "Intended Audience :: Developers",
+  "License :: OSI Approved :: MIT License",
+  "Programming Language :: Python :: 3",
+  "Topic :: Software Development :: Quality Assurance",
+]
+dependencies = []
+
+[project.urls]
+Homepage = "https://since.dev"
+Documentation = "https://since.dev/docs#cli"
+Source = "https://github.com/Since-dev/cli"
+Issues = "https://github.com/Since-dev/cli/issues"
+
+[project.scripts]
+since = "since_dev.__main__:main"
+since-dev = "since_dev.__main__:main"
+
+[tool.setuptools]
+packages = ["since_dev"]

since_dev-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

since_dev-0.1.0/since_dev/__init__.py

@@ -0,0 +1,3 @@
+"""since-dev: what in a repository is about to stop working. The same CLI as the npm package of the same name."""
+
+__version__ = "0.1.0"

since_dev-0.1.0/since_dev/__main__.py

@@ -0,0 +1,23 @@
+import sys
+
+from .cli import run
+from .realio import RealIo
+
+
+def main():
+    for stream in (sys.stdout, sys.stderr):
+        # A Windows console in a legacy code page would fail on a title outside it; replace what it cannot show.
+        if hasattr(stream, "reconfigure"):
+            stream.reconfigure(encoding="utf-8", errors="replace")
+    try:
+        code = run(sys.argv[1:], RealIo())
+    except KeyboardInterrupt:
+        code = 130
+    except Exception as error:  # noqa: BLE001 - the last line of defense: say what happened in one line
+        sys.stderr.write("since: %s\n" % error)
+        code = 1
+    sys.exit(code)
+
+
+if __name__ == "__main__":
+    main()