Release Alert
Actively maintained
≈ 6visits/mo
Use not read yet · estimate, read Oct 23, 2026
- For
- Developers and teams who want release and CVE alerts for the packages they depend on across registries
- Activity
- Actively maintainedsite updated 5 days ago
- Used for
- get Slack or email alerts when dependencies publish new releases
- watch npm, PyPI and Docker Hub projects for new versions
- flag CVEs that match the projects in your stack
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsreleasealert.dev ↗
- MCP serverdev.releasealert/mcpverified in the MCP registry
- Stateanswers, 6 toolschecked 2026-10-23
- Address to connectreleasealert.dev/mcp
- MCP docsreleasealert.dev/docs/mcpthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use Release Alert for?
Sign in to leave a noteWhat is Release Alert?
Watches package registries for new releases and matched CVEs, then sends alerts to Slack, Discord or email.
Who is Release Alert for?
Developers and teams who want release and CVE alerts for the packages they depend on across registries
Is Release Alert still maintained?
Actively maintained: site updated 5 days ago.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.