Dev Facts Check
Agent Tools · tools.openkrill.app
Check the facts a developer asks for again and again: when a software version reaches end of life, whether the runtimes a repository pins are still supported, what an open-source license is, whether a web feature works in a browser, what an RFC says about itself and what changed between two versions of a package.
How to install Dev Facts Check in ChatGPT
- Open the official listing for Dev Facts Check in the ChatGPT workspace you want to use.
- Choose Install plugin if available. Follow any connection steps for the apps listed on the page.
- Open a new conversation on a supported ChatGPT surface. Select Dev Facts Check from the plugin options or mention it by name.
How to use Dev Facts Check
Check the marketplace listing or publisher’s documentation for supported actions and examples.
Historial de posiciones
Consulta el orden de los plugins en el directorio público de ChatGPT por fecha de captura. Popular es una selección editorial. OpenAI no publica cifras de instalaciones ni de uso en este directorio.
Frequently asked questions
Why is Install plugin missing?
Check your account, workspace, plan and region. If the listing says Desktop only, open it in the ChatGPT desktop app.
Información
Ask "is Node.js 20 still supported?", "is anything in this repo past end of life?", "is the MIT license OSI approved?", "can I use CSS container queries in Safari?", "which RFC obsoletes RFC 2616?" or "what changed in express between 4.18.2 and 5.1.0?". For a repository, pass the files that pin runtimes (package.json, .nvmrc, .python-version, pyproject.toml, go.mod, a Dockerfile or compose file, .tool-versions, mise.toml, .ruby-version, a Gemfile, composer.json or global.json) and get one row per runtime with its end-of-life date, days left, latest patch and the next supported cycle. It reads five public sources: endoflife.date for release cycles and support dates, the SPDX License List for license identifiers and OSI and FSF status, webstatus.dev for Baseline status and the first browser version that supports a web feature, the RFC Editor and IETF Datatracker for RFC status, abstracts and obsoleting links, and GitHub releases and changelog files for the notes of each release in a version range. Every answer names its source and the date of the data. endoflife.date is maintained by volunteers, so confirm a date with the vendor before a contract or compliance decision. A license answer identifies a license and does not say what it lets you do: it is not legal advice. It does not scan packages for vulnerabilities or health: use the Package Health Check plugin for that. It stores nothing about you: answers are cached for a few hours and the only lasting record is a daily count of calls per tool.
Funciones
- Shows whether a version of a product has reached end of life
- with its end-of-life and LTS dates
- Lists the release cycles of a product that are still supported
- newest first
- with the latest patch
- Reads the runtime pins in a repo (Node.js
- Python
- Go
- Ruby
- PHP
- .NET
- Docker images) and flags any past end of life
- Looks up an SPDX license by identifier or name: OSI approved
- FSF free
- deprecated or not
- Shows the first release of each major browser that supports a web feature
- and its Baseline status
- Looks up an RFC by number or title words: status
- abstract
- and the RFCs that obsolete or update it
- Lists the GitHub release notes of an npm or PyPI package between 2 versions and flags breaking changes
- Names the source and the date of its data in every answerShow more