Added caching actions

[DomPeliniAerospike]

No description provided.

To fix this issue, we should add a top-level permissions block to the workflow YAML, directly after the name: section and before on:. The contents of the block should be set to the minimal required privileges for the workflow. If unsure about the exact needs (since we do not see what is done in the invoked/reusable workflows), the safest default is to set all permissions to read. You can then open up specific writes (e.g., contents: write, pull-requests: write) if required by the workflow logic. For now, following the CodeQL recommendation, we will start with:

permissions:
  contents: read

Place this block as line 2, shifting subsequent lines down. This minimal change does not affect workflow functionality and enforces the least privilege principle.

The fix is to explicitly add a permissions key at the root of the workflow file (.github/workflows/master-workflow.yml). This will apply to all jobs defined in the workflow unless those jobs define their own more restrictive or permissive settings. The ideal permissions block should minimally include only what is required for the jobs to run. Since most jobs in this workflow delegate using the uses: syntax to other workflow files—and the actual commands performed are unknown from the snippet—it is safest to use a starting point of contents: read (the standard minimal permissions), which allows jobs to access repository contents but not perform any write operations. If jobs in the called workflow files require additional permissions (such as pull-requests: write), those can be granted there, but defaulting to read-only here reduces risk.

To implement this, add the following block immediately below the workflow name: at the start of the file:

permissions:
  contents: read

No imports or dependencies are required for this change.

To fix the issue, add a permissions block at the top level of the workflow (directly under name: and before on:), or to each job as appropriate. Since all jobs are workflow calls and likely inherit GITHUB_TOKEN unless overridden, set the minimum required permissions. As a safe starting point, set contents: read (to enable Git operations) and, if writing to packages or creating releases, set packages: write. Since the jobs mention publishing to npm and uploading to JFrog, contents: read may be sufficient unless you know the jobs require wider privileges. If further privilege is needed, you can extend the block later.

Make this change in .github/workflows/master-workflow.yml by adding, for example:

permissions:
  contents: read

directly after line 1.
No new dependencies or imports are required.