fix: Titles capitalization (#100)

* fix capitalization

* fix CR

policies/github/actions.rego

@@ -43,7 +43,7 @@ all_github_actions_are_allowed {
 
 # METADATA
 # scope: rule
-# title: Default workflow token permission is not read only
+# title: Default Workflow Token Permission Is Not Read Only
 # description: Your default GitHub Action workflow token permission is set to read-write. When creating workflow tokens, it is highly recommended to follow the Principle of Least Privilege and force workflow authors to specify explicitly which permissions they need.
 # custom:
 #   requiredEnrichers: [organizationId]

policies/github/member.rego

@@ -2,7 +2,7 @@ package member
 
 # METADATA
 # scope: rule
-# title: Organization has too many owners
+# title: Organization Has Too Many Owners
 # description: Organization owners are highly privileged and could create great damage if being compromised, it's recommended to limit them to the minimum needed (recommended maximum 3 owners).
 # custom:
 #   remediationSteps: [Make sure you have admin permissions, Go to the organization People page, Select the unwanted owners, Using the "X members selected" - change role to member]

policies/github/repository.rego

@@ -4,7 +4,7 @@ import data.common.webhooks as webhookUtils
 
 # METADATA
 # scope: rule
-# title: Repository not maintained
+# title: Repository Not Maintained
 # description: There hasn't been any commits in tha last 3 months. A project which is not active might not be patched against security issues within its code and dependencies, and is therefore at higher risk of including unpatched vulnerabilities.
 # custom:
 #   remediationSteps: [Make sure you have admin permissions, Either Delete or Archive the repository]
@@ -427,7 +427,7 @@ ghas_dependency_review_not_enabled {
 
 # METADATA
 # scope: rule
-# title: Low scorecard score for repository indicates poor security posture
+# title: Low Scorecard Score for Repository Indicates Poor Security Posture
 # description: Scorecard is an open-source tool from OSSF that helps to asses the security posture of repositories, Low scorecard score means your repository may be under risk.
 # custom:
 #    requiredEnrichers: [scorecard]
@@ -444,7 +444,7 @@ scorecard_score_too_low {
 
 # METADATA
 # scope: rule
-# title: Default workflow token permission is not read only
+# title: Default Workflow Token Permission Is Not Read Only
 # description: Your default GitHub Action workflow token permission is set to read-write. When creating workflow tokens, it is highly recommended to follow the Principle of Least Privilege and force workflow authors to specify explicitly which permissions they need.
 # custom:
 #   requiredEnrichers: [organizationId]

policies/github/runner_group.rego

@@ -2,7 +2,7 @@ package runner_group
 
 # METADATA
 # scope: rule
-# title: Runner group is not limited to private repositories
+# title: Runner Group Is Not Limited to Private Repositories
 # description: |
 #       Workflows from public repositories are allowed to run on GitHub Hosted Runners.
 #       When using GitHub Hosted Runners, it is recommended to allow only workflows from private repositories to run on these runners to avoid being vulnerable
@@ -31,7 +31,7 @@ runner_group_can_be_used_by_public_repositories {
 
 # METADATA
 # scope: rule
-# title: Runner group is not limited to selected repositories
+# title: Runner Group Is Not Limited to Selected Repositories
 # description: |
 #       Not limiting the runner group to selected repositories allows any user in the organization to execute workflows
 #       on the group's runners.

policies/gitlab/member.rego

@@ -41,7 +41,7 @@ two_factor_authentication_is_disabled_for_an_external_collaborator {
 
 # METADATA
 # scope: rule
-# title: Stale admin detected
+# title: Stale Admin Detected
 # description: A collaborator with global admin permissions didn't do any action in the last 6 months. Admin users are extremely powerful and common compliance standards demand keeping the number of admins at minimum. Consider revoking this collaborator admin credentials (downgrade to regular user), or remove the user completely.
 # custom:
 #   severity: MEDIUM

policies/gitlab/organization.rego

@@ -61,7 +61,7 @@ organization_webhook_doesnt_require_ssl[violation] = true {
 
 # METADATA
 # scope: rule
-# title: Group does not enforce branch protection by default
+# title: Group Does Not Enforce Branch Protection by Default
 # description: You do not have a default full branch protection for a specific group, which means any new repository will be created without it. In fully protected level, developers cannot push new commits, and no one can force push or delete the branch. Protecting branches ensures new code changes must go through a controlled merge process and it allows enforcement of code review and other security tests.
 # custom:
 #   severity: MEDIUM

policies/gitlab/repository.rego

@@ -2,7 +2,7 @@ package repository
 
 # METADATA
 # scope: rule
-# title: Project not maintained
+# title: Project Not Maintained
 # description: The project was not active in the last 3 months. A project which is not active might not be patched against security issues within its code and dependencies, and is therefore at higher risk of including unpatched vulnerabilities.
 # custom:
 #   remediationSteps: [Make sure you have admin permissions, Either Delete or Archive the project]
@@ -93,7 +93,7 @@ missing_default_branch_protection_force_push {
 
 # METADATA
 # scope: rule
-# title: Code review is not limited to code-owners only in default branch
+# title: Code Review Is Not Limited to Code-Owners Only in Default Branch
 # description: It is recommended to require code review only from designated individuals specified in CODEOWNERS file. Turning this option on enforces that only the allowed owners can approve a code change. This option is found in the branch protection setting of the project.
 # custom:
 #   remediationSteps: [Make sure you have owner permissions, Go to the projects's settings -> Repository page, Enter "Protected branches" tab, select the default branch. Check the "Code owner approval"]