Add ReleaseRun Vulnerability Scanner to Monitoring section#474
Closed
Matheus-RR wants to merge 1 commit into
Closed
Add ReleaseRun Vulnerability Scanner to Monitoring section#474Matheus-RR wants to merge 1 commit into
Matheus-RR wants to merge 1 commit into
Conversation
Author
|
Just checking in on this — the tool is live and up to date (covers PG 10 through 18). Happy to adjust the description or section placement if anything looks off. Thanks for maintaining this list! |
Collaborator
|
@Matheus-RR Thanks for the addition! But I think it fits better under the Security section :) |
Author
|
Closing — duplicate submission. We already have #486 open to this repo. Keeping the more recent one. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds ReleaseRun Vulnerability Scanner to the Monitoring section.
A free tool that checks PostgreSQL version health: EOL dates, known CVEs, support status, and upgrade recommendations. Covers all major versions from 10 through 18.
Useful alongside existing monitoring tools in the list. While most entries focus on runtime performance monitoring, this covers version lifecycle monitoring, which is a gap in the current list. Knowing your PostgreSQL version is approaching EOL or has unpatched CVEs is just as important as tracking query performance.
Also available as a CLI:
npx releaserun check(npm | GitHub).