docs: add SECURITY.md - #420
Conversation
Points at security@pgedge.com as the single reporting route and at the pgEdge Vulnerability Disclosure Statement at docs.pgedge.com/security for scope, safe harbour and CVE handling. Identical across every pgEdge product repository, and byte-identical to the organisation default on pgEdge/.github.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe pull request adds ChangesSecurity Policy
Poem
Merge Risk: ⚪ Minimal · up to This adds a visible security reporting policy and disclosure reference without changing product behavior or runtime operation. No merge-readiness risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Up to standards ✅🟢 Issues
|
| Category | Results |
|---|---|
| Comprehensibility | 1 minor |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
Adds
SECURITY.mdto the repository root. It names security@pgedge.com asthe single reporting route and points at the pgEdge Vulnerability Disclosure
Statement at https://docs.pgedge.com/security for scope, safe harbour and CVE
handling.
The file is identical in every pgEdge product repository — nothing in it is
repo-specific — and byte-identical to the organisation default already merged
on
pgEdge/.github.Why an in-repo copy when there is an org default
pgEdge/.githubcarries the same file as an organisation default, which coversevery repository that has none of its own. Defaults do not appear in a
repository's file tree, git history, clones or release archives — only in the
Security tab. A product a customer clones or vendors should carry its own
policy, and OpenSSF Scorecard's security-policy check only looks in the
repository itself.
Ready to merge
The statement this file links to is live, and the same file is already on
mainin the other pgEdge product repositories. This repository is one of theseven that could not take the PR until push access was granted.