Skip to content

Create SECURITY.md - #844

Open
trewc456-ai wants to merge 1 commit into
dbpedia:masterfrom
trewc456-ai:patch-4
Open

Create SECURITY.md#844
trewc456-ai wants to merge 1 commit into
dbpedia:masterfrom
trewc456-ai:patch-4

Conversation

@trewc456-ai

@trewc456-ai trewc456-ai commented Jul 23, 2026

Copy link
Copy Markdown

Summary by CodeRabbit

  • Documentation
    • Added a security policy outlining supported versions.
    • Included guidance for reporting security vulnerabilities.

@sonarqubecloud

Copy link
Copy Markdown

@trewc456-ai trewc456-ai left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Added SECURITY.md with a supported-versions table and vulnerability-reporting guidance.

Changes

Security Policy Documentation

Layer / File(s) Summary
Security policy document
SECURITY.md
Adds supported-version information and placeholder guidance for reporting vulnerabilities.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and accurately summarizes the main change: adding a new SECURITY.md file.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@SECURITY.md`:
- Around line 5-21: Replace the placeholder support table in SECURITY.md with
the project’s actual supported versions and security-update status. Rewrite the
Reporting a Vulnerability section with the repository-specific reporting
channel, expected response timeline, triage and acceptance/decline outcomes, and
disclosure expectations; remove all GitHub template placeholder text.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4dff0b92-d564-4f4b-9e70-869d57e05baa

📥 Commits

Reviewing files that changed from the base of the PR and between e3dfe8b and fb4dd8b.

📒 Files selected for processing (1)
  • SECURITY.md

Comment thread SECURITY.md
Comment on lines +5 to +21
Use this section to tell people about which versions of your project are
currently being supported with security updates.

| Version | Supported |
| ------- | ------------------ |
| 5.1.x | :white_check_mark: |
| 5.0.x | :x: |
| 4.0.x | :white_check_mark: |
| < 4.0 | :x: |

## Reporting a Vulnerability

Use this section to tell people how to report a vulnerability.

Tell them where to go, how often they can expect to get an update on a
reported vulnerability, what to expect if the vulnerability is accepted or
declined, etc.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'Repository files relevant to version/release/security:\n'
git ls-files | rg '(^SECURITY\.md$|(^|/)(package\.json|Cargo\.toml|pyproject\.toml|composer\.json|pubspec\.yaml|setup\.py|README\.md|CHANGELOG|HISTORY|NEWS|VERSION|version\.|release\.|Releases|releases\.md)$|(^|/)github/workflows/)' || true

printf '\nSECURITY.md:\n'
if [ -f SECURITY.md ]; then cat -n SECURITY.md; else echo 'SECURITY.md not found'; fi

printf '\nPackage/version indicators:\n'
for f in package.json Cargo.toml pyproject.toml composer.json pubspec.yaml setup.py setup.cfg; do
  if [ -f "$f" ]; then
    echo "--- $f ---"
    sed -n '1,120p' "$f"
  fi
done

printf '\nREADME/Changelog version mentions (first matching files):\n'
for f in README.md CHANGELOG.md HISTORY.md NEWS.md; do
  if [ -f "$f" ]; then
    echo "--- $f top lines ---"
    sed -n '1,120p' "$f" | rg -n -C 2 'version|Version|5\.1|5\.0|4\.0|release|Release|support|supported|SECURITY|security' || true
  fi
done

Repository: dbpedia/extraction-framework

Length of output: 2963


🏁 Script executed:

#!/bin/bash
set -euo pipefail

python3 - <<'PY'
from pathlib import Path
p=Path('SECURITY.md')
if not p.exists():
    print('SECURITY.md missing')
    raise SystemExit
s=p.read_text().splitlines()
checks={}
checks['has_report_section']='Reporting a Vulnerability' in s[0:25] or any('report' in line.lower() for line in s)
checks['has_email_or_url']=any('e-mail' in line.lower() or '@' in line or 'https://' in line or 'http://' in line for line in s)
checks['has_timeline_word']=any(t in s[-25:] or 'timeline' in line.lower() for line in s[:35])
print(checks)
print('lines:')
for i,l in enumerate(s,1):
    print(f'{i}: {l}')
PY

Repository: dbpedia/extraction-framework

Length of output: 315


Replace the template placeholders with an actionable security policy.

SECURITY.md still uses GitHub’s default template text in Reporting a Vulnerability, so researchers have no repository-specific reporting channel, response timeline, triage outcomes, or disclosure expectations. Replace the placeholder version table with the project’s real supported versions before merging.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@SECURITY.md` around lines 5 - 21, Replace the placeholder support table in
SECURITY.md with the project’s actual supported versions and security-update
status. Rewrite the Reporting a Vulnerability section with the
repository-specific reporting channel, expected response timeline, triage and
acceptance/decline outcomes, and disclosure expectations; remove all GitHub
template placeholder text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant