chore(deps): bump @octokit/endpoint from 10.1.1 to 10.1.3

[dependabot]

Bumps @octokit/endpoint from 10.1.1 to 10.1.3.

Release notes

Sourced from @​octokit/endpoint's releases.

v10.1.3

10.1.3 (2025-02-13)

Bug Fixes

• Fix a ReDos vulnerability, reported by @​DayShift (6c9c5be)

v10.1.2

10.1.2 (2024-12-31)

Bug Fixes

• deps: bump @octokit/types to improve Deno compat (#507) (15d700b)

Commits

• d6cf1ad fix: linting issues breaking ci (#514)
• 6c9c5be Merge commit from fork
• e472e22 chore(deps): update dependency esbuild to ^0.25.0 (#512)
• b2ebcda build(deps-dev): bump vitest and @​vitest/coverage-v8 (#511)
• 76e3738 build(deps): bump vite from 5.4.6 to 6.0.11 (#509)
• c9ce54d chore(deps): update vitest monorepo to v3 (major) (#508)
• 15d700b fix(deps): bump @octokit/types to improve Deno compat (#507)
• a0a938e chore(deps): update dependency prettier to v3.4.2 (#506)
• 2e92021 chore(deps): update dependency prettier to v3.4.1 (#505)
• 55ee6d6 chore(deps): update dependency prettier to v3.4.0 (#504)
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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.

Summary by Sourcery

Bump @octokit/endpoint dependency to v10.1.3 to patch a ReDoS vulnerability and improve Deno compatibility.

Bug Fixes:

• Update @octokit/endpoint to v10.1.3 to address a regular expression denial of service (ReDoS) vulnerability and improve Deno compatibility.

Chores:

• Bump @octokit/endpoint from v10.1.1 to v10.1.3.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the @octokit/endpoint dependency from version 10.1.1 to 10.1.3. This update includes a fix for a ReDos vulnerability and improves Deno compatibility.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Bumped the @octokit/endpoint dependency from version 10.1.1 to 10.1.3.	Updated @octokit/endpoint to the latest version. Addressed a ReDos vulnerability. Improved Deno compatibility by updating @octokit/types.	package-lock.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/@octokit/endpoint	10.1.1	🟢 6.8	Details Check Score Reason Security-Policy 🟢 9 security policy file detected Maintained 🟢 6 7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Code-Review 🟢 8 Found 6/7 approved changesets -- score normalized to 8 Binary-Artifacts 🟢 10 no binaries found in the repo Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Pinned-Dependencies 🟢 4 dependency not pinned by hash detected -- score normalized to 4 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration Signed-Releases ⚠️ -1 no releases found Packaging 🟢 10 packaging workflow detected SAST 🟢 10 SAST tool is run on all commits Vulnerabilities 🟢 8 2 existing vulnerabilities detected
npm/@octokit/endpoint	10.1.3	🟢 6.8	Details Check Score Reason Security-Policy 🟢 9 security policy file detected Maintained 🟢 6 7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Code-Review 🟢 8 Found 6/7 approved changesets -- score normalized to 8 Binary-Artifacts 🟢 10 no binaries found in the repo Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Pinned-Dependencies 🟢 4 dependency not pinned by hash detected -- score normalized to 4 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration Signed-Releases ⚠️ -1 no releases found Packaging 🟢 10 packaging workflow detected SAST 🟢 10 SAST tool is run on all commits Vulnerabilities 🟢 8 2 existing vulnerabilities detected

Scanned Manifest Files

package-lock.json

• @octokit/endpoint@10.1.1
• @octokit/endpoint@10.1.3

[review-deriv]

AI Code Review

⚠️ IMPORTANT: This review is AI-generated and should be validated by human reviewers
It appears that the Git diff or specific code changes were not provided. Below is a template illustrating how an in-depth review could be structured if the diff were available. You can replace the placeholders with actual findings once you have the code changes:

────────────────────────────────────────────────────────────────────────
🔴 BUGS & LOGICAL ISSUES:

1. Issue Description:
   • Specify the exact logical flaw (e.g., incorrect condition, missing null check, off-by-one error, etc.).

2. Potential Impacts:
   • Explain how this bug might affect users or the system (e.g., data corruption, crashes, unexpected states).

3. Reproduction Scenarios:
   • Describe steps or conditions under which the bug manifests (e.g., when input is null, when a specific corner case is triggered).

4. Fix Implementation (with code example):
   • Provide a snippet or pseudocode illustrating the corrected logic/condition/check.

────────────────────────────────────────────────────────────────────────
🟡 RELIABILITY CONCERNS:

1. Edge Cases Identified:
   • Outline cases where the code might fail or behave unexpectedly (e.g., empty inputs, maximum values, invalid states).

2. Potential Failure Scenarios:
   • Detail how these edge cases might escalate into larger failures (e.g., timeouts, resource leaks, partial data processing).

3. Mitigation Steps (with code examples):
   • Show how to handle these edge cases cleanly (e.g., additional checks, better error messages, fallback logic).

────────────────────────────────────────────────────────────────────────
💡 ROBUSTNESS IMPROVEMENTS:

1. Error Handling Enhancements:
   • Recommend adding or improving error catching, logging, and user-friendly messages.

2. Input Validation Additions:
   • Suggest stronger validation for fields, null/undefined checks, type checks, and sanitization.

3. State Management Improvements:
   • Explain optimizations to avoid inconsistent states or data races (e.g., ensuring proper synchronization or finalization).

4. Code Examples for Each Suggestion:
   • Provide concise code snippets or patterns that illustrate the recommendations in action.
   ────────────────────────────────────────────────────────────────────────

Once the specific diff is available, you can fill in each section with concrete observations and recommendations tailored to the actual changes in the code.