Dev Facts Check
Agent Tools v1.2.0
EOL, licences, browsers, RFCs
Competitor profile
Developer declarations; not independently tested. Listing last checked Nov 4, 2026. Package observed Nov 3, 2026.
Declared capabilities
- 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
Declared limitations
- Package vulnerabilities and health belong to Package Health Check; this plugin covers versions, end of life, licenses and browser support. Expected: Does not use the Dev Facts tools to answer. Says this plugin does not cover package vulnerabilities.
- The plugin looks up dated reference facts; it does not teach programming. Expected: Does not call a tool. Answers from general knowledge or points to the React documentation.
- The plugin identifies existing SPDX licenses; it does not write or advise on licenses. Expected: Does not call a tool to draft a license. May use check_license to look up a named license, and says it is not legal advice.
Not specified in the available declarations: pricing & account requirements.
Onboarding example
Is Node.js 20 still supported, and when does it reach end of life?
Description
From the marketplace listing
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. 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.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Oct 28, 2026. Last seen Nov 4, 2026.
Similar plugins
No close matches found from the available descriptions and keywords yet.
Find competitors by name or topic →Files & skills
File archives
Release notes
1.2.0: adds check_runtime_eol, which reads the runtime pins in a repository's files (package.json engines, .nvmrc, .python-version, pyproject.toml, go.mod, Dockerfile and compose images, .tool-versions, mise.toml, .ruby-version, Gemfile, composer.json, global.json) and returns each runtime's end-of-life date, days left, latest patch and next supported cycle from endoflife.date. 1.1.0: adds get_release_notes, the GitHub release notes of an npm or PyPI package (or a GitHub repository) between 2 versions, with breaking changes flagged and the changelog file read when the release list does not reach back far enough. 1.0.0: first release. Reads endoflife.date, the SPDX License List, webstatus.dev and the RFC Editor: end-of-life status, license check, browser support and RFC lookup. Answers are cached for up to a day; read-only, no sign-in.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- Agent Tools
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- 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 answer
Package observed Nov 3, 2026.
Technical details
- First seen
- Oct 28, 2026 · 12:00 UTC
- Last seen
- Nov 4, 2026 · 06:00 UTC
- Collection status
- Collected
plugin_asdk_app_6ac270d84d308191a705ef6dcfa59c9d
Download plugin data (JSON)