feat: add @scalar

[aoaostar]

Summary by CodeRabbit

• New Features
  • Expanded the scope of allowed packages by adding @scalar to the project.
• Version Update
  • Incremented project version to 1.136.0.

[coderabbitai]

Walkthrough

The changes in this pull request involve an update to the package.json file of the unpkg-white-list project. The version number has been increased to 1.136.0, and a new scope, @scalar, has been added to the allowScopes array. This allows the inclusion of additional packages within the project. No other fields in the package.json file were modified.

Changes

File	Change Summary
package.json	Version updated to 1.136.0; added @scalar to allowScopes.

Possibly related PRs

• feat: add @yuzhang134562 #56: Adds a new scope @yuzhang134562 to the allowScopes array in package.json.
• feat: add @wangeditor-next #163: Introduces a new scope @wangeditor-next to the allowScopes array in package.json.
• feat: add @scent scope #286: Adds two new scopes, @pubinfo and @scent, to the allowScopes array in package.json.
• feat: add @wuxh scope & allow refined-antd-changelog #297: Includes a new scope @wuxh in the allowScopes array in package.json.

🐇 In the garden where changes bloom,
A new scope joins, dispelling gloom.
Version rises, a leap so bright,
@scalar hops in, a joyful sight!
With each update, our project grows,
In the world of code, creativity flows! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 07ec42f and fc33f1e.

📒 Files selected for processing (1)

• package.json (1 hunks)

🧰 Additional context used

🔇 Additional comments (3)

package.json (3)

Line range hint 3-3: Version bump to 1.136.0

The package version has been incremented to 1.136.0. This change is in line with semantic versioning practices for feature additions.

---

Line range hint 1-1163: Summary of changes

The changes in this PR are minimal and focused:

1. The package version has been bumped to 1.136.0.
2. A new scope "@scalar" has been added to the allowScopes array.

These changes are consistent with the PR objectives and don't introduce any apparent issues. However, it's recommended to verify the security implications of adding the new "@scalar" scope.

---

183-183: New scope "@scalar" added to allowScopes

A new scope "@scalar" has been added to the allowScopes array. This addition expands the list of allowed packages that can be utilized within the project.

To ensure this change doesn't introduce any security risks, let's verify if this scope is commonly used and doesn't contain any known malicious packages:

✅ Verification successful

Verification Successful: "@scalar" Scope is Safe to Add

• The @scalar scope is present in package.json and appears to be used for internal packages.
• No known public packages exist under the @scalar scope in the npm registry.
• No security issues detected with the current configuration.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if @scalar is a commonly used scope and if it has any known security issues
npm info @scalar
npm audit @scalar

Length of output: 180

---

Script:

#!/bin/bash
# Search for @scalar scope in package.json and package-lock.json
rg '"@scalar' package.json package-lock.json

# Retrieve information about @scalar scope from npm registry
curl -s https://registry.npmjs.org/-/v1/search?text=scope:@scalar > scalar_scope_info.json

Length of output: 202

---

Script:

#!/bin/bash
# Display the contents of scalar_scope_info.json in a readable format
jq '.' scalar_scope_info.json

# Check for the existence of alternative lock files
fd -e yarn.lock -e pnpm-lock.yaml

Length of output: 175

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

Documentation and Community

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