-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update README to change the note about support. #438
Conversation
WalkthroughThe pull request modifies the documentation in the Changes
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
DryRun Security SummaryThe pull request updates the Bulwark project's documentation to remove references to commercial support and services, signaling a shift towards a more community-driven, open-source approach. Expand for full summarySummary: The code changes made in this pull request are focused on updating the documentation for the Bulwark project, specifically the README file located at From an application security perspective, these changes do not directly impact the security of the Bulwark application itself. However, they do indicate a change in the project's direction and support model, which could have indirect implications for the project's long-term sustainability and the availability of commercial support options for users who may require them. While the move towards a more community-driven, open-source approach could be beneficial for the project's adoption and growth, it may also mean that certain commercial support options are no longer available. Files Changed:
Code AnalysisWe ran |
DryRun Security SummaryThe pull request updates the README's "Supported" section to remove commercial references, highlight community involvement, and emphasize the project's ongoing development by its primary maintainer. Expand for full summarySummary: The code changes in this pull request update the "Supported" section of the README file for the Bulwark project. The key changes include the removal of the "Commercially Supported" mention and the cloud admin application reference, as well as the addition of information about the freely available community ruleset and the invitation for anyone to contribute to it. From an application security perspective, these changes do not raise any immediate concerns. The shift towards a more community-driven approach could be positive for the project's security posture if it leads to increased transparency and involvement from the broader security community. The addition of the community ruleset information is also a positive step, as it encourages contributions and collaboration, which can help improve the quality and security of the detection rules over time. Overall, these updates seem reasonable and in line with the project's goals, as long as the Bulwark project continues to maintain its focus on security. Files Changed:
Code AnalysisWe ran |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
docs/README.md (1)
41-44
: LGTM! Clear and transparent support information.The updated support section effectively communicates the transition while maintaining a positive, community-oriented tone. The inclusion of direct links to both the maintainer and community ruleset provides clear paths for user engagement.
Consider adding a brief mention of how users can get support (e.g., through GitHub issues/discussions) to make the support channels more explicit. For example:
- **Supported.** Bulwark is actively developed and supported by [Bob Aman](https://github.com/sporkmonger). There is a freely available [community ruleset](https://github.com/bulwark-security/bulwark-community-ruleset) which anyone is welcome - to contribute to. + to contribute to. Support is provided through GitHub issues and discussions.
The company is shutting down, but the project will remain supported in a personal capacity.
Summary by CodeRabbit