Bump minimist from 1.2.5 to 1.2.7 in /subhub-link-checker

[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.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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.

In general, the fix is to add an explicit permissions section to the workflow or to the specific job so that the GITHUB_TOKEN is limited to the least privileges needed. For a linting-only workflow that only checks out code and runs local commands, read access to repository contents is sufficient.

The best minimal change here is to add permissions: contents: read at the workflow root (top level, alongside name and on). This will apply to all jobs in this workflow and document that they only need read access to the repository contents. No changes to steps or other behavior are required.

Concretely, in .github/workflows/linting.yml, add a permissions block after the name: Lint line and before the on: block. No imports or additional definitions are required, since this is pure YAML configuration.

In general, fix this by explicitly declaring a restrictive permissions block so the GITHUB_TOKEN has only the minimal access required. For this workflow, the job only needs to read the repository contents for actions/checkout, and the Sentry step uses Sentry credentials, not GitHub write access, so contents: read at the workflow level is sufficient.

Concretely, in .github/workflows/sentry.yml, add a permissions: section at the top level (alongside name and on) configuring contents: read. This will apply to all jobs (including sentry-release) because they do not define their own permissions block. No imports or additional methods are needed; this is a pure YAML configuration change.

To fix the problem, sanitize user-controlled data before including it in log messages. For plain-text logs, a minimal and effective approach is to strip carriage return and line feed characters from the value, then log the sanitized version. Additionally, it is good practice to clearly delimit user input in the log message so that it’s visually distinct from fixed log text.

In this file, the best targeted fix is to create a sanitized version of event.body on or before line 53, e.g. const safeBody = String(event.body).replace(/[\r\n]/g, '');, and then use safeBody in the log statement. This avoids changing any functional behavior of the handler (parsing and search logic still use the original event.body), while ensuring that the log output cannot be split or spoofed with control characters. No new external dependencies are needed; we rely only on built-in JavaScript string operations.

Concretely:

• In hub-search-proxy/handler.js, within module.exports.search, replace line 53 with two lines:
  • define safeBody by converting event.body to a string and removing \r and \n;
  • log using safeBody instead of the raw event.body.
• No imports or other structural changes are required.