Repository navigation
docs: clarify security support and private reporting - #411
Merged
Merged
Conversation
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
Seddryck
force-pushed
the
docs/review-security-policy
branch
from
November 2, 2026 20:27
14f40c4 to
ebff638
Compare
|
This was referenced Nov 3, 2026
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
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.
SECURITY.md still contained template instructions, obsolete release lines, and a reference to Expressif. Replace these with the agreed policy: security fixes target the latest stable release of each PocketCsvReader package, with no backports or guaranteed response or resolution time.
Link directly to GitHub's private vulnerability reporting form and explain how to prepare a private report and coordinate disclosure. Private vulnerability reporting was enabled with maintainer approval and verified through the GitHub API (
enabled: true).Validation:
git diff --checkpassed; confirmed stale template text and unrelated project references were removed.dotnet build PocketCsvReader.sln --configuration Release --verbosity quiet -clp:ErrorsOnlypassed (7 warnings, 0 errors). A subsequent no-restore build passed with 3 existing assembly-reference conflict warnings in PocketCsvReader.Profiler.dotnet format PocketCsvReader.full.sln analyzers --verify-no-changes --no-restore.close #410