Bump sha.js from 2.4.11 to 2.4.12 in /quiz-app

[dependabot]

Bumps sha.js from 2.4.11 to 2.4.12.

Changelog

Sourced from sha.js's changelog.

v2.4.12 - 2025-07-01

Commits

• [eslint] switch to eslint 7acadfb
• [meta] add auto-changelog b46e711
• [eslint] fix package.json indentation df9d521
• [Tests] migrate from travis to GHA c43c64a
• [Fix] support multi-byte wide typed arrays f2a258e
• [meta] reorder package.json d8d77c0
• [meta] add npmignore 35aec35
• [Tests] avoid console logs 73e33ae
• [Tests] fix tests run in batch 2629130
• [Tests] drop node requirement to 0.10 00c7f23
• [Dev Deps] update buffer, hash-test-vectors, standard, tape, typedarray 92b5de5
• [Tests] drop node requirement to v3 9b5eca8
• [meta] set engines to >= 4 807084c
• Only apps should have lockfiles c72789c
• [Deps] update inherits, safe-buffer 5428cfc
• [Dev Deps] update @ljharb/eslint-config 2dbe0aa
• update README to reflect LICENSE 8938256
• [Dev Deps] add missing peer dep d528896
• [Dev Deps] remove unused buffer dep 94ca724

Commits

• eb4ea2f v2.4.12
• d8d77c0 [meta] reorder package.json
• df9d521 [eslint] fix package.json indentation
• 35aec35 [meta] add npmignore
• d528896 [Dev Deps] add missing peer dep
• b46e711 [meta] add auto-changelog
• 94ca724 [Dev Deps] remove unused buffer dep
• 2dbe0aa [Dev Deps] update @ljharb/eslint-config
• 73e33ae [Tests] avoid console logs
• f2a258e [Fix] support multi-byte wide typed arrays
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by ljharb, a new releaser for sha.js 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 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.

[code-companion-ai]

Processing PR updates...

[amazon-q-developer]

⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done

[prplex]

Review completed. No issues found.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codara-ai-code-review]

Potential issues, bugs, and flaws that can introduce unwanted behavior.

1. Inconsistency in package versions:

   • The package-lock.json file shows updated versions of several packages (e.g. call-bind updating from 1.0.0 to 1.0.8), but it doesn't appear to specify if these newer versions have been tested or if they are known to be compatible with the existing codebase. This could lead to unpredictable behavior if breaking changes exist in the newer versions.
   • /quiz-app/package-lock.json

2. Dev dependency inclusion in production:

   • Multiple dependencies marked as dev: true (e.g. available-typed-arrays, call-bind, etc.) may lead to accidentally bundling development dependencies into production if the right configuration is not set. It's crucial to ensure different environments are correctly segregated.
   • /quiz-app/package-lock.json

3. Dependency versioning issues:

   • The use of versions like "^1.0.0" could lead to unexpected major version changes if any patches introduce backward-incompatible changes. It is often safer to pin versions explicitly.
   • /quiz-app/package-lock.json

Code suggestions and improvements for better exception handling, logic, standardization, and consistency.

1. Consider specifying exact dependency versions for production:

   • Rather than using caret ^ for versioning in critical operations, consider using exact versions in your main application dependencies to avoid unintentional upgrades.
   • /quiz-app/package-lock.json

2. Consolidating frequent dependencies:

   • Several packages (like function-bind, es-errors, and call-bind) appear to have overlapping functionality in different modules. Consider checking if some dependencies can be consolidated to reduce bloat and possible duplication in functionality.
   • /quiz-app/package-lock.json

3. Document any major updates:

   • When updating packages and dependencies, especially in package-lock.json, it's good practice to document the rationale behind the updates in your project's changelog. This helps future maintainers understand the history of changes, especially if unexpected issues arise from these updates.
   • /quiz-app/package-lock.json

4. Regularly audit dependencies:

   • Encourage running an audit tool such as npm audit or yarn audit regularly to identify and address potential vulnerabilities in the dependencies updated.
   • /quiz-app/package-lock.json

5. Normalization of funding URLs:

   • Consider a consistent format for specifying funding URLs in the dependencies. This will ensure all dependencies follow the same pattern, enhancing maintainability and readability.
   • /quiz-app/package-lock.json

[amazon-q-developer]

✅ I finished the code review, and didn't find any security or code quality issues.

[llamapreview]

Auto Pull Request Review from LlamaPReview

Review Status: Automated Review Skipped

Dear contributor,

Thank you for your Pull Request. LlamaPReview has analyzed your changes and determined that this PR does not require an automated code review.

Analysis Result:

All 1 files are skipped files

Technical Context:

All files in this PR were marked as skipped, which typically includes:

• Generated files
• Build artifacts
• Pre-filtered content
• Files marked with [SKIPPED] tag

We're continuously improving our PR analysis capabilities. Have thoughts on when and how LlamaPReview should perform automated reviews? Share your insights in our GitHub Discussions.

Best regards,
LlamaPReview Team