Setting up project info in repo

PR Type:

Documentation

PR Description:

This PR updates the project information and security details in the repository. It includes changes to the README.md, MAINTAINERS.md, SECURITY.md, SECURITY-INSIGHTS.yml, and SECURITY_CONTACTS files. The updates provide more detailed information about the project, its maintainers, and the security policies and contacts.

PR Main Files Walkthrough:

files:

`README.md`: Updated the project title and added a FOSSA Status badge. Also added a Changelog section with a link to the project's release page. `MAINTAINERS.md`: Added a section about the project maintainers and provided a link to the main Kubescape project's maintainers. `SECURITY.md`: Added a section on how to report security issues or vulnerabilities, including the steps to follow and the expected response time. `SECURITY-INSIGHTS.yml`: Added a comprehensive security insights file, detailing the project lifecycle, contribution policy, documentation, distribution points, security artifacts, security testing tools, security contacts, and vulnerability reporting process. `SECURITY_CONTACTS`: Removed the previous security contacts and replaced them with a reference to the SECURITY.md file for reporting security issues.

User Description:

Sorry, we do not accept changes directly against this repository. Please see CONTRIBUTING.md for information on where and how to contribute instead.

PR Analysis

🎯 Main theme: Updating project information and security details in the repository
📝 PR summary: This PR updates the project information and security details in the repository. It includes changes to the README.md, MAINTAINERS.md, SECURITY.md, SECURITY-INSIGHTS.yml, and SECURITY_CONTACTS files. The updates provide more detailed information about the project, its maintainers, and the security policies and contacts.
📌 Type of PR: Documentation
🧪 Relevant tests added: No
⏱️ Estimated effort to review [1-5]: 2, because the PR is primarily focused on documentation updates and doesn't involve complex code changes.
🔒 Security concerns: No security concerns found

PR Feedback
💡 General suggestions: The PR is well-structured and the changes are clearly explained. The updates to the project information and security details are comprehensive and well-documented. However, it would be beneficial to ensure that all links provided in the documentation are working as expected.
🤖 Code feedback:
- relevant file: README.md suggestion: Consider adding a brief description of the project at the beginning of the README file to provide context for new visitors. [medium] relevant line: Kubescape Storage
- relevant file: SECURITY-INSIGHTS.yml suggestion: It would be helpful to include a brief description of each security testing tool used, as well as the reasons for choosing them. [medium] relevant line: tool-name: Dependabot

How to use

To invoke the PR-Agent, add a comment using one of the following commands: /review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option. /describe: Modify the PR title and description based on the contents of the PR. /improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback. /ask \<QUESTION>: Pose a question about the PR. /update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value For example: /review --pr_reviewer.extra_instructions="focus on the file: ..." To list the possible configuration parameters, use the /config command.

kubescape / storage