Merge pull request #725 from evemonk/updates

Updates

.github/workflows/codeql.yml

@@ -13,12 +13,13 @@ name: "CodeQL"
 
 on:
   push:
-    branches: ["main"]
+    branches:
+      - main
   pull_request:
-    # The branches below must be a subset of the branches above
-    branches: ["main"]
+    branches:
+      - main
   schedule:
-    - cron: "0 0 * * 1"
+    - cron: "0 21 * * 6"
 
 permissions:
   contents: read

.github/workflows/hadolint.yml

@@ -10,6 +10,9 @@ on:
   schedule:
     - cron: "0 21 * * 6"
 
+permissions:
+  contents: read
+
 jobs:
   hadolint:
     runs-on: ubuntu-latest

.github/workflows/mdl.yml

@@ -10,6 +10,9 @@ on:
   schedule:
     - cron: "0 21 * * 6"
 
+permissions:
+  contents: read
+
 jobs:
   mdl:
     runs-on: ubuntu-latest

.github/workflows/rspec.yml

@@ -10,6 +10,9 @@ on:
   schedule:
     - cron: "0 21 * * 6"
 
+permissions:
+  contents: read
+
 env:
   POSTGRES_HOST_AUTH_METHOD: "trust"
   POSTGRES_USER: "runner"
@@ -18,9 +21,6 @@ env:
   SECRET_KEY_BASE: "919650e468e29e897a53ef239b6e0228f8b71ec6ed353b691d140945e98d0c6a63731811afc27b61b9094523740962499afabc6d7ad0c872f1d5b62472083a08"
   CI: "yes"
 
-permissions:
-  contents: read
-
 jobs:
   rspec:
     runs-on: ubuntu-latest

.github/workflows/scorecards.yml

@@ -6,13 +6,14 @@ name: Scorecard supply-chain security
 on:
   # For Branch-Protection check. Only the default branch is supported. See
   # https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection
-  branch_protection_rule:
+  branch_protection_rule: {}
   # To guarantee Maintained check is occasionally updated. See
   # https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained
-  schedule:
-    - cron: '20 7 * * 2'
   push:
-    branches: ["main"]
+    branches:
+      - main
+  schedule:
+    - cron: "0 21 * * 6"
 
 # Declare default permissions as read only.
 permissions: read-all

Dockerfile

@@ -1,4 +1,4 @@
-FROM registry.docker.com/library/ruby:3.3.0-slim as base
+FROM registry.docker.com/library/ruby:3.3.0-slim@sha256:763422273a15e307b044fcb3ad6b1ef6c290d2043ac73596842aba5659dc7318 as base
 
 LABEL maintainer="Igor Zubkov <[email protected]>"
 
@@ -44,8 +44,7 @@ COPY . .
 RUN bundle exec bootsnap precompile app/ lib/
 
 # Workaround for nokogiri and trivy
-RUN rm -f /usr/local/bundle/ruby/3.3.0/gems/nokogiri-1.15.5-x86_64-linux/dependencies.yml
-RUN rm -f /usr/local/bundle/ruby/3.3.0/gems/nokogiri-1.15.5/dependencies.yml
+RUN rm -f /usr/local/bundle/ruby/3.3.0/gems/nokogiri-1.16.0-x86_64-linux/dependencies.yml
 
 # Final stage for app image
 FROM base

LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2016-2024 Ihor Zubkov
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

SECURITY.md

@@ -0,0 +1,17 @@
+# EveMonk Security Policy
+
+## Supported Versions
+
+We release patches for security vulnerabilities against the following versions
+of EveMonk:
+
+| Version | Supported          |
+|---------| ------------------ |
+| main    | :white_check_mark: |
+
+## Reporting a Vulnerability
+
+Please report security vulnerabilities to [email protected]. You should
+receive a response within 72 hours. If the issue is confirmed, we will release
+a patch as soon as possible depending on complexity but historically within a
+few days.