Bump minimist from 1.2.5 to 1.2.7 in /research-hub-web

[dependabot]

Bumps minimist from 1.2.5 to 1.2.7.

Changelog

Sourced from minimist's changelog.

v1.2.7 - 2022-10-10

Commits

• [meta] add auto-changelog 0ebf4eb
• [actions] add reusable workflows e115b63
• [eslint] add eslint; rules to enable later are warnings f58745b
• [Dev Deps] switch from covert to nyc ab03356
• [readme] rename and add badges 236f4a0
• [meta] create FUNDING.yml; add funding in package.json 783a49b
• [meta] use npmignore to autogenerate an npmignore file f81ece6
• Only apps should have lockfiles 56cad44
• [Dev Deps] update covert, tape; remove unnecessary tap 49c5f9f
• [Tests] add aud in posttest 228ae93
• [meta] add safe-publish-latest 01fc23f
• [meta] update repo URLs 6b164c7

v1.2.6 - 2022-03-21

Commits

• test from prototype pollution PR bc8ecee
• isConstructorOrProto adapted from PR c2b9819
• security notice for additional prototype pollution issue ef88b93

Commits

• c590d75 v1.2.7
• 0ebf4eb [meta] add auto-changelog
• e115b63 [actions] add reusable workflows
• 01fc23f [meta] add safe-publish-latest
• f58745b [eslint] add eslint; rules to enable later are warnings
• 228ae93 [Tests] add aud in posttest
• 236f4a0 [readme] rename and add badges
• ab03356 [Dev Deps] switch from covert to nyc
• 49c5f9f [Dev Deps] update covert, tape; remove unnecessary tap
• 783a49b [meta] create FUNDING.yml; add funding in package.json
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by ljharb, a new releaser for minimist since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

In general, the fix is to add an explicit permissions block that grants only the minimal required scopes for this workflow. Since this workflow just checks out the code and runs linters, it only needs read access to repository contents.

The best minimal fix without changing functionality is to add permissions: contents: read at the workflow root level (right after name: Lint), so all jobs inherit these read-only contents permissions. No additional scopes (like pull-requests: write or issues: write) appear necessary from the shown steps. This change is limited to .github/workflows/linting.yml, and no imports or method definitions are needed because this is pure YAML configuration.

Concretely, in .github/workflows/linting.yml, insert:

permissions:
  contents: read

between the existing name: Lint line and the on: block. This will satisfy the CodeQL rule and enforce least-privilege access for GITHUB_TOKEN in this workflow.

In general, the fix is to add an explicit permissions block to the workflow or to the specific job, restricting the GITHUB_TOKEN to the least privileges needed. If the workflow only needs to read code (and not push, create releases, or modify issues/PRs), contents: read is an appropriate minimal starting point.

For this specific workflow in .github/workflows/sentry.yml, the safest change without altering functionality is to add a job‑level permissions block under sentry-release. The Sentry action communicates with Sentry via SENTRY_AUTH_TOKEN, so the GitHub token likely does not need write scopes. We will therefore set:

permissions:
  contents: read

This will limit the GITHUB_TOKEN used in the job to read‑only repository contents. No additional methods, imports, or dependencies are needed. The change should be added immediately under the runs-on: ubuntu-latest line (line 15–16 region) in the sentry-release job.

In general, to fix log injection issues, sanitize any user-controlled data before writing it to logs. For plain-text logs, this typically means removing or normalizing newline (\n, \r) and other control characters, and optionally truncating very long inputs. The functional behavior of the application should not change; only how data is represented in logs should be adjusted.

For this specific case in hub-search-proxy/handler.js, we should avoid logging event.body as-is. The best minimal fix is:

• Derive a sanitized representation of event.body for logging only:
  • If it is a string, remove \r and \n characters.
  • Optionally, truncate to a reasonable length (e.g., 1000 characters) to avoid log flooding, but truncation is not strictly required for injection prevention.
• Use that sanitized value in the console.log statement instead of the raw event.body.
• Keep the rest of the function unchanged, particularly the JSON.parse(event.body); line, to avoid impacting request handling.

Concretely:

• In module.exports.search near line 53 in hub-search-proxy/handler.js, replace the direct console.log(Received query: ${event.body}); call with a small block that builds a sanitized string (e.g., sanitizedBody) by calling String(event.body).replace(/[\r\n]/g, '') and then logs that sanitized value. No new imports or external dependencies are needed.

---