Skip to content

docs: add SECURITY-INSIGHTS.yml security metadata#637

Open
mesutoezdil wants to merge 2 commits into
Project-HAMi:masterfrom
mesutoezdil:docs/security-insights
Open

docs: add SECURITY-INSIGHTS.yml security metadata#637
mesutoezdil wants to merge 2 commits into
Project-HAMi:masterfrom
mesutoezdil:docs/security-insights

Conversation

@mesutoezdil

@mesutoezdil mesutoezdil commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

What

Adds security-insights.yml following the OpenSSF Security Insights spec v2.2.0, which LFX Insights explicitly recommends generating for this repository. Filename, location and structure follow the spec's example-minimum.yml.

It declares:

  • The project's subproject repositories with a one-line intent for each (also feeds OSPS-QA-04.01, "Insights does not contain a list of repositories")
  • Project administrators and the repository core team, taken from the approvers in OWNERS
  • The vulnerability reporting channel (GitHub Security Advisories, consistent with the policy in docs: add security policy and code of conduct files #621 and the main HAMi repo)
  • Repository status, license (CC-BY-4.0) and contributing guide
  • A short self-assessment for this static documentation site

Why

LFX Insights and other automated assessment tools read this file to answer security questions about the repo without guessing. Two currently failed or recommended items on the Insights security page point at it directly.

Part of #627

Copilot AI review requested due to automatic review settings July 22, 2026 12:53
@hami-robot

hami-robot Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mesutoezdil
Once this PR has been reviewed and has the lgtm label, please assign windsonsea for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@netlify

netlify Bot commented Jul 22, 2026

Copy link
Copy Markdown

Deploy Preview for project-hami ready!

Name Link
🔨 Latest commit cbdc8dd
🔍 Latest deploy log https://app.netlify.com/projects/project-hami/deploys/6a639910ab50eb0009f964ef
😎 Deploy Preview https://deploy-preview-637--project-hami.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@mesutoezdil, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e574c144-af52-4c49-805f-d36011e8b41d

📥 Commits

Reviewing files that changed from the base of the PR and between bf4e9cf and cbdc8dd.

📒 Files selected for processing (1)
  • security-insights.yml
✨ 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.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR adds a Security Insights metadata file to the repository root so automated security assessment tools (e.g., LFX Insights) can discover project/repository security posture and key links without inference.

Changes:

  • Added SECURITY-INSIGHTS.yml describing the HAMi project repositories and vulnerability reporting channel.
  • Declared this repo’s status/license/contributing guide and a short self-assessment.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread SECURITY-INSIGHTS.yml Outdated
Comment thread security-insights.yml
Comment thread SECURITY-INSIGHTS.yml Outdated
@mesutoezdil
mesutoezdil force-pushed the docs/security-insights branch from d217b13 to a3a5140 Compare July 22, 2026 13:01
Copilot AI review requested due to automatic review settings July 22, 2026 13:01

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

Comment thread security-insights.yml
Comment thread security-insights.yml Outdated
Machine-readable security metadata per the OpenSSF Security
Insights spec v2.2.0, recommended by LFX Insights. Includes the
subproject repository list, core team, vulnerability reporting
channel and license information.

Signed-off-by: mesutoezdil <mesudozdil@gmail.com>
Copilot AI review requested due to automatic review settings July 22, 2026 13:06
@mesutoezdil
mesutoezdil force-pushed the docs/security-insights branch from a3a5140 to a4979fd Compare July 22, 2026 13:06

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

security-insights.yml:74

  • The self-assessment claims dependency updates are "driven by npm audit", but there’s no in-repo automation/configuration (e.g., GitHub workflow, Dependabot/Renovate config) to support that statement. To avoid publishing potentially inaccurate process claims, please remove or reword this sentence to reflect the actual maintenance practice.
    assessments:
      self:
        comment: Static documentation site built with Docusaurus and deployed via Netlify. No user data is collected or stored by this repository. Dependencies are updated through maintenance pull requests driven by npm audit.

@mesutoezdil
mesutoezdil requested a review from windsonsea July 23, 2026 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants