eol-pin-check 0.1.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,27 @@
1
+ CC0 1.0 Universal — Public Domain Dedication
2
+
3
+ The person who associated a work with this deed has dedicated the work to the
4
+ public domain by waiving all of his or her rights to the work worldwide under
5
+ copyright law, including all related and neighboring rights, to the extent
6
+ allowed by law.
7
+
8
+ You can copy, modify, distribute and perform the work, even for commercial
9
+ purposes, all without asking permission.
10
+
11
+ Full text: https://creativecommons.org/publicdomain/zero/1.0/legalcode
12
+
13
+ ---
14
+
15
+ This dedication covers the compilation and the code in this package.
16
+
17
+ The underlying facts are taken from third-party sources, each of which is cited
18
+ by URL in the shipped data alongside the verbatim quote the value was read from:
19
+
20
+ * PyTorch's RELEASE.md and .ci/manywheel/build_cuda.sh — BSD-3-Clause
21
+ (pytorch/pytorch LICENSE)
22
+ * NVIDIA's CUDA Toolkit release notes and CUDA GPUs page — vendor technical
23
+ documentation
24
+
25
+ Facts are not copyrightable. What is reproduced from those sources is a fact
26
+ plus a short attributed quote linking back to it; neither document is
27
+ reproduced.
@@ -0,0 +1,153 @@
1
+ Metadata-Version: 2.4
2
+ Name: eol-pin-check
3
+ Version: 0.1.0
4
+ Summary: Find the runtime versions your repo pins — Python, Node.js, Ubuntu, Debian, Alpine, Go, PostgreSQL — and say whether the publisher has stopped supporting each one, with the publisher's own sentence as evidence
5
+ Author: referencesource.org
6
+ License: CC0-1.0
7
+ Project-URL: Homepage, https://referencesource.org/software-end-of-support/
8
+ Project-URL: Source, https://referencesource.org/software-end-of-support/
9
+ Keywords: eol,end-of-life,end-of-support,python-version,dockerfile,docker,ubuntu,node,postgres,security,ci,pre-commit,lint,supply-chain
10
+ Classifier: Development Status :: 4 - Beta
11
+ Classifier: Intended Audience :: Developers
12
+ Classifier: Programming Language :: Python :: 3
13
+ Classifier: Topic :: Software Development :: Quality Assurance
14
+ Classifier: Topic :: System :: Systems Administration
15
+ Requires-Python: >=3.8
16
+ Description-Content-Type: text/markdown
17
+ License-File: LICENSE
18
+ Dynamic: license-file
19
+
20
+ # eol-pin-check (Python)
21
+
22
+ Finds the Python, Node.js, Ubuntu, Debian, Alpine Linux, Go and PostgreSQL
23
+ versions your repository pins, says whether each one is still supported, and
24
+ shows the record each date was read from — endoflife.date's own row for that
25
+ release, quoted as it was served, with the date we last re-checked it. Exits
26
+ non-zero when something has lost free security support, so it works as a CI
27
+ gate or a `pre-commit` hook.
28
+
29
+ ```console
30
+ $ pip install eol-pin-check
31
+ $ eol-pin-check
32
+ Python 3.8 — security support has ended
33
+ Dockerfile:1 FROM (written "3.8-slim", read as 3.8)
34
+ security support ends 2024-10-07; active support ended 2021-05-03
35
+ ""name":"3.8","label":"3.8","releaseDate":"2019-10-14","isEol":true,"eolFrom":"2024-10-07","isMaintained":false"
36
+ https://endoflife.date/api/v1/products/python
37
+ our record: https://referencesource.org/software-end-of-support/python-3-8/ last checked 2026-10-05
38
+ the publisher still supports Python 3.15 (supported to 2031-10-31)
39
+ (that this project runs on it is not something our records know, and is not claimed)
40
+
41
+ Python 3.12 — past active support, still getting security fixes
42
+ .github/workflows/ci.yml:8 python-version
43
+ security support ends 2028-10-31; active support ended 2025-04-02
44
+ ...
45
+
46
+ 5 runtime pin(s) in 4 files: 4 out of support, 1 past active support, 0 with no end date stated, 0 not in our records, 0 unpinned.
47
+ Only the files this scan opened were looked at; a pin in a file it did not open has not been cleared.
48
+ $ echo $?
49
+ 1
50
+ ```
51
+
52
+ This is the Python twin of the [npm package of the same
53
+ name](https://www.npmjs.com/package/eol-pin-check). It exists because most of
54
+ the files it reads belong to a Python project — `pyproject.toml`, `setup.cfg`,
55
+ `tox.ini`, `Pipfile`, `.python-version`, `runtime.txt`, `environment.yml`,
56
+ `.readthedocs.yaml` and the Dockerfile beside them — and a project laid out
57
+ that way installs a check like this with `pip` or `pre-commit`, neither of
58
+ which can reach npm. Both packages are built from the same records by the same
59
+ script, so they agree about what is supported by construction rather than by
60
+ hand; a gate fails if the two data files ever differ or if the two give
61
+ different verdicts on the same pin.
62
+
63
+ ## What it reads
64
+
65
+ Dockerfiles and `Containerfile`; `docker-compose*.yml`; dev container configs;
66
+ `.github/workflows/*.yml` (`python-version`, `node-version`, `runs-on`,
67
+ `container`); `.gitlab-ci.yml`, `azure-pipelines.yml`,
68
+ `bitbucket-pipelines.yml`, `.travis.yml`, `cloudbuild.yaml`, `.drone.yml`,
69
+ `.woodpecker.yml`, `.circleci/config.yml`; `pyproject.toml` and `setup.cfg`
70
+ (`requires-python` floor); `tox.ini` and `noxfile.py` (`py38`, `py312`);
71
+ `Pipfile`; `.python-version`; `runtime.txt`; `environment.yml` (conda);
72
+ `.readthedocs.yaml`; `.nvmrc`, `.node-version`, `.tool-versions`, `mise.toml`,
73
+ `netlify.toml`; and `package.json` (`engines.node` floor, `volta.node`).
74
+
75
+ Caches, build output, virtualenvs and vendored code are not read —
76
+ `node_modules`, `.venv`, `dist`, `.tox`, `.yarn` and the rest — because a pin
77
+ inside an installed toolchain is a fact about something you downloaded, and
78
+ reporting it as yours names a file you cannot edit.
79
+
80
+ ## Commands
81
+
82
+ ```
83
+ eol-pin-check scan the current directory
84
+ eol-pin-check src deploy scan these paths
85
+ eol-pin-check --pin Python 3.8 look one version up, scan nothing
86
+ eol-pin-check --supported Python what the publisher still supports today
87
+
88
+ --json machine-readable output (for CI and agents)
89
+ --strict exit 1 for a release past active support as well
90
+ --quiet print only the pins that are not plainly supported
91
+ --full-quote print the whole quoted sentence
92
+ --today YYYY-MM-DD judge against this date instead of today
93
+ ```
94
+
95
+ ## pre-commit
96
+
97
+ There is no GitHub mirror of this package to point `repo:` at yet, so the
98
+ stanza below is the one that works today: pip installs it from PyPI and
99
+ `pre-commit` runs the installed command.
100
+
101
+ ```yaml
102
+ repos:
103
+ - repo: local
104
+ hooks:
105
+ - id: eol-pin-check
106
+ name: eol-pin-check (is a pinned runtime out of support?)
107
+ entry: eol-pin-check
108
+ language: python
109
+ additional_dependencies: [eol-pin-check]
110
+ pass_filenames: true
111
+ types: [text]
112
+ ```
113
+
114
+ A `.pre-commit-hooks.yaml` ships inside the package as well, so the moment a
115
+ mirror repository exists the three-line `repo:`/`rev:`/`hooks:` form will work
116
+ without any change here. Pointing you at that repository before it exists
117
+ would be telling you to install something that is not there.
118
+
119
+ ## What it will not do
120
+
121
+ **It does not rewrite your files.** The npm twin can edit a dead pin to a
122
+ supported release (`--fix` / `--write`); that half is deliberately not ported
123
+ yet, because a rewrite that is wrong edits your code, and the rules that make
124
+ it safe — put the `-slim` back on a tag, refuse a range with two clauses —
125
+ deserve their own tests rather than a hurried port. `--fix` and `--write` exit
126
+ 2 here and say so. This build still *names* what the publisher supports
127
+ instead, which is the part that needs no write.
128
+
129
+ **It does not call a blank "supported".** Where a source states no end date,
130
+ what you get is which of three things the source actually said: ended with no
131
+ date given, maintained with no date announced (Go's habit), or nothing at all
132
+ — which is reported as its own status, because answering "supported" there
133
+ would be inventing the answer that suits a passing build.
134
+
135
+ **It does not fail a build over active support ending.** A release still
136
+ inside its security-fix window is a normal thing to be running. Only the end of
137
+ free security support, or of the paid extended cover that followed it, exits 1.
138
+ `--strict` changes that if you want it to.
139
+
140
+ **It does not clear what it did not read.** Every answer says how many files
141
+ were opened, and that a release we hold no record for is unknown to us rather
142
+ than supported.
143
+
144
+ ## Where the data comes from
145
+
146
+ 189 releases of 7 products, from
147
+ [endoflife.date](https://endoflife.date)'s own API (MIT), re-checked on a
148
+ schedule and published with the quote at
149
+ <https://referencesource.org/software-end-of-support/>. This compilation is
150
+ CC0-1.0. The records, not this package, are the product: every date printed
151
+ came off the publisher's page with the sentence it was read from.
152
+
153
+ Built by an automated system. No value here was typed by hand.
@@ -0,0 +1,134 @@
1
+ # eol-pin-check (Python)
2
+
3
+ Finds the Python, Node.js, Ubuntu, Debian, Alpine Linux, Go and PostgreSQL
4
+ versions your repository pins, says whether each one is still supported, and
5
+ shows the record each date was read from — endoflife.date's own row for that
6
+ release, quoted as it was served, with the date we last re-checked it. Exits
7
+ non-zero when something has lost free security support, so it works as a CI
8
+ gate or a `pre-commit` hook.
9
+
10
+ ```console
11
+ $ pip install eol-pin-check
12
+ $ eol-pin-check
13
+ Python 3.8 — security support has ended
14
+ Dockerfile:1 FROM (written "3.8-slim", read as 3.8)
15
+ security support ends 2024-10-07; active support ended 2021-05-03
16
+ ""name":"3.8","label":"3.8","releaseDate":"2019-10-14","isEol":true,"eolFrom":"2024-10-07","isMaintained":false"
17
+ https://endoflife.date/api/v1/products/python
18
+ our record: https://referencesource.org/software-end-of-support/python-3-8/ last checked 2026-10-05
19
+ the publisher still supports Python 3.15 (supported to 2031-10-31)
20
+ (that this project runs on it is not something our records know, and is not claimed)
21
+
22
+ Python 3.12 — past active support, still getting security fixes
23
+ .github/workflows/ci.yml:8 python-version
24
+ security support ends 2028-10-31; active support ended 2025-04-02
25
+ ...
26
+
27
+ 5 runtime pin(s) in 4 files: 4 out of support, 1 past active support, 0 with no end date stated, 0 not in our records, 0 unpinned.
28
+ Only the files this scan opened were looked at; a pin in a file it did not open has not been cleared.
29
+ $ echo $?
30
+ 1
31
+ ```
32
+
33
+ This is the Python twin of the [npm package of the same
34
+ name](https://www.npmjs.com/package/eol-pin-check). It exists because most of
35
+ the files it reads belong to a Python project — `pyproject.toml`, `setup.cfg`,
36
+ `tox.ini`, `Pipfile`, `.python-version`, `runtime.txt`, `environment.yml`,
37
+ `.readthedocs.yaml` and the Dockerfile beside them — and a project laid out
38
+ that way installs a check like this with `pip` or `pre-commit`, neither of
39
+ which can reach npm. Both packages are built from the same records by the same
40
+ script, so they agree about what is supported by construction rather than by
41
+ hand; a gate fails if the two data files ever differ or if the two give
42
+ different verdicts on the same pin.
43
+
44
+ ## What it reads
45
+
46
+ Dockerfiles and `Containerfile`; `docker-compose*.yml`; dev container configs;
47
+ `.github/workflows/*.yml` (`python-version`, `node-version`, `runs-on`,
48
+ `container`); `.gitlab-ci.yml`, `azure-pipelines.yml`,
49
+ `bitbucket-pipelines.yml`, `.travis.yml`, `cloudbuild.yaml`, `.drone.yml`,
50
+ `.woodpecker.yml`, `.circleci/config.yml`; `pyproject.toml` and `setup.cfg`
51
+ (`requires-python` floor); `tox.ini` and `noxfile.py` (`py38`, `py312`);
52
+ `Pipfile`; `.python-version`; `runtime.txt`; `environment.yml` (conda);
53
+ `.readthedocs.yaml`; `.nvmrc`, `.node-version`, `.tool-versions`, `mise.toml`,
54
+ `netlify.toml`; and `package.json` (`engines.node` floor, `volta.node`).
55
+
56
+ Caches, build output, virtualenvs and vendored code are not read —
57
+ `node_modules`, `.venv`, `dist`, `.tox`, `.yarn` and the rest — because a pin
58
+ inside an installed toolchain is a fact about something you downloaded, and
59
+ reporting it as yours names a file you cannot edit.
60
+
61
+ ## Commands
62
+
63
+ ```
64
+ eol-pin-check scan the current directory
65
+ eol-pin-check src deploy scan these paths
66
+ eol-pin-check --pin Python 3.8 look one version up, scan nothing
67
+ eol-pin-check --supported Python what the publisher still supports today
68
+
69
+ --json machine-readable output (for CI and agents)
70
+ --strict exit 1 for a release past active support as well
71
+ --quiet print only the pins that are not plainly supported
72
+ --full-quote print the whole quoted sentence
73
+ --today YYYY-MM-DD judge against this date instead of today
74
+ ```
75
+
76
+ ## pre-commit
77
+
78
+ There is no GitHub mirror of this package to point `repo:` at yet, so the
79
+ stanza below is the one that works today: pip installs it from PyPI and
80
+ `pre-commit` runs the installed command.
81
+
82
+ ```yaml
83
+ repos:
84
+ - repo: local
85
+ hooks:
86
+ - id: eol-pin-check
87
+ name: eol-pin-check (is a pinned runtime out of support?)
88
+ entry: eol-pin-check
89
+ language: python
90
+ additional_dependencies: [eol-pin-check]
91
+ pass_filenames: true
92
+ types: [text]
93
+ ```
94
+
95
+ A `.pre-commit-hooks.yaml` ships inside the package as well, so the moment a
96
+ mirror repository exists the three-line `repo:`/`rev:`/`hooks:` form will work
97
+ without any change here. Pointing you at that repository before it exists
98
+ would be telling you to install something that is not there.
99
+
100
+ ## What it will not do
101
+
102
+ **It does not rewrite your files.** The npm twin can edit a dead pin to a
103
+ supported release (`--fix` / `--write`); that half is deliberately not ported
104
+ yet, because a rewrite that is wrong edits your code, and the rules that make
105
+ it safe — put the `-slim` back on a tag, refuse a range with two clauses —
106
+ deserve their own tests rather than a hurried port. `--fix` and `--write` exit
107
+ 2 here and say so. This build still *names* what the publisher supports
108
+ instead, which is the part that needs no write.
109
+
110
+ **It does not call a blank "supported".** Where a source states no end date,
111
+ what you get is which of three things the source actually said: ended with no
112
+ date given, maintained with no date announced (Go's habit), or nothing at all
113
+ — which is reported as its own status, because answering "supported" there
114
+ would be inventing the answer that suits a passing build.
115
+
116
+ **It does not fail a build over active support ending.** A release still
117
+ inside its security-fix window is a normal thing to be running. Only the end of
118
+ free security support, or of the paid extended cover that followed it, exits 1.
119
+ `--strict` changes that if you want it to.
120
+
121
+ **It does not clear what it did not read.** Every answer says how many files
122
+ were opened, and that a release we hold no record for is unknown to us rather
123
+ than supported.
124
+
125
+ ## Where the data comes from
126
+
127
+ 189 releases of 7 products, from
128
+ [endoflife.date](https://endoflife.date)'s own API (MIT), re-checked on a
129
+ schedule and published with the quote at
130
+ <https://referencesource.org/software-end-of-support/>. This compilation is
131
+ CC0-1.0. The records, not this package, are the product: every date printed
132
+ came off the publisher's page with the sentence it was read from.
133
+
134
+ Built by an automated system. No value here was typed by hand.
@@ -0,0 +1,36 @@
1
+ [build-system]
2
+ requires = ["setuptools>=61"]
3
+ build-backend = "setuptools.build_meta"
4
+
5
+ [project]
6
+ name = "eol-pin-check"
7
+ version = "0.1.0"
8
+ description = "Find the runtime versions your repo pins — Python, Node.js, Ubuntu, Debian, Alpine, Go, PostgreSQL — and say whether the publisher has stopped supporting each one, with the publisher's own sentence as evidence"
9
+ readme = "README.md"
10
+ requires-python = ">=3.8"
11
+ license = { text = "CC0-1.0" }
12
+ authors = [{ name = "referencesource.org" }]
13
+ keywords = ["eol", "end-of-life", "end-of-support", "python-version",
14
+ "dockerfile", "docker", "ubuntu", "node", "postgres", "security",
15
+ "ci", "pre-commit", "lint", "supply-chain"]
16
+ classifiers = [
17
+ "Development Status :: 4 - Beta",
18
+ "Intended Audience :: Developers",
19
+ "Programming Language :: Python :: 3",
20
+ "Topic :: Software Development :: Quality Assurance",
21
+ "Topic :: System :: Systems Administration",
22
+ ]
23
+ dependencies = []
24
+
25
+ [project.urls]
26
+ Homepage = "https://referencesource.org/software-end-of-support/"
27
+ Source = "https://referencesource.org/software-end-of-support/"
28
+
29
+ [project.scripts]
30
+ eol-pin-check = "eol_pin_check.__main__:main"
31
+
32
+ [tool.setuptools.packages.find]
33
+ where = ["src"]
34
+
35
+ [tool.setuptools.package-data]
36
+ eol_pin_check = ["data.json"]
@@ -0,0 +1,4 @@
1
+ [egg_info]
2
+ tag_build =
3
+ tag_date = 0
4
+