Potential fix for code scanning alert no. 2: Workflow does not contain permissions

[ELMOURABEA]

Potential fix for https://github.com/ELMOURABEA/pharmaintel-api/security/code-scanning/2

To resolve this problem, we need to limit the permissions available to the build job to the minimum required. The build job only needs to check out code and run tests, so contents: read is sufficient. The best way to fix this is to add a permissions block under the build job, specifically before or after runs-on: ubuntu-latest, setting contents: read. No changes are necessary elsewhere, as the publish-gpr job already assigns correct permissions. No new methods, imports, or definitions are needed—just a workflow YAML field update.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

[Copilot]

Pull Request Overview

This PR addresses a GitHub code scanning alert by adding explicit permissions to the build job in the npm-publish-github-packages workflow. The change implements the principle of least privilege by restricting the job to only contents: read permission, which is sufficient for checking out code and running tests.

Key Changes:

• Added a permissions block to the build job with contents: read as the only permission

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
23540111	Triggered	Company Email Password	f233156	.env.example	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}