Skip to content

chore(deps): Update#52

Open
williaby wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance
Open

chore(deps): Update#52
williaby wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@williaby

Copy link
Copy Markdown
Contributor

Summary

Why

Scheduled patch update, bug fixes and security patches with no API changes.

Changes

This PR contains the following updates:

Change Update
All locks refreshed lockFileMaintenance

Impact

  • ✅ Patch update: bug fixes and security patches only
  • ✅ No breaking changes

Acceptance Criteria

  • All CI checks pass

Testing

  • CI gates pass (tests, lint, type checking, security scan)

Notes

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • "before 5am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

Copilot AI review requested due to automatic review settings June 15, 2026 05:13

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock, !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1280c399-e9eb-4445-b2a4-7ee30d4967cb

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

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/lock-file-maintenance

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

Copy link
Copy Markdown

Dependency Review

The following issues were found:
  • ✅ 0 vulnerable package(s)
  • ❌ 1 package(s) with incompatible licenses
  • ✅ 0 package(s) with invalid SPDX license definitions
  • ⚠️ 79 package(s) with unknown licenses.
  • ⚠️ 1 packages with OpenSSF Scorecard issues.
See the Details below.

License Issues

uv.lock

PackageVersionLicenseIssue Type
regex2026.5.9CNRI-Python AND Apache-2.0Incompatible License
backrefs7.0NullUnknown License
basedpyright1.39.8NullUnknown License
beautifulsoup44.15.0NullUnknown License
cloudflare5.3.0NullUnknown License
cryptography49.0.0NullUnknown License
cyclonedx-python-lib11.10.0NullUnknown License
debugpy1.8.21NullUnknown License
distlib0.4.3NullUnknown License
fastapi0.137.0NullUnknown License
filelock3.29.4NullUnknown License
google-api-core2.31.0NullUnknown License
google-auth2.54.0NullUnknown License
google-cloud-storage3.12.0NullUnknown License
google-genai2.8.0NullUnknown License
googleapis-common-protos1.75.0NullUnknown License
griffe-pydantic1.3.1NullUnknown License
griffelib2.0.2NullUnknown License
hypothesis6.155.2NullUnknown License
idna3.18NullUnknown License
ipykernel7.3.0NullUnknown License
ipython8.39.0NullUnknown License
ipython9.14.1NullUnknown License
joserfc1.7.1NullUnknown License
jupyter-client8.9.1NullUnknown License
jupyter-lsp2.3.1NullUnknown License
jupyter-server2.19.0NullUnknown License
jupyterlab4.5.8NullUnknown License
matplotlib-inline0.2.2NullUnknown License
mistune3.2.1NullUnknown License
mkdocs-autorefs1.4.4NullUnknown License
mkdocs-gen-files0.6.1NullUnknown License
mkdocs-get-deps0.2.2NullUnknown License
mkdocs-git-revision-date-localized-plugin1.5.3NullUnknown License
mkdocs-material9.7.6NullUnknown License
mkdocs-section-index0.3.12NullUnknown License
mkdocstrings1.0.4NullUnknown License
mkdocstrings-python2.0.4NullUnknown License
msgpack1.2.0NullUnknown License
nbclient0.11.0NullUnknown License
nbconvert7.17.1NullUnknown License
nodejs-wheel-binaries24.16.0NullUnknown License
notebook7.5.7NullUnknown License
nox2026.4.10NullUnknown License
nox-uv0.8.0NullUnknown License
pathspec1.1.1NullUnknown License
pip26.1.2NullUnknown License
pip-audit2.10.1NullUnknown License
platformdirs4.10.0NullUnknown License
properdocs1.6.7NullUnknown License
proto-plus1.28.0NullUnknown License
protobuf7.35.1NullUnknown License
pydoclint0.8.6NullUnknown License
pymdown-extensions10.21.3NullUnknown License
pytest9.1.0NullUnknown License
pytest-asyncio1.4.0NullUnknown License
python-discovery1.4.2NullUnknown License
python-frontmatter1.3.0NullUnknown License
python-json-logger4.1.0NullUnknown License
pywinpty3.0.5NullUnknown License
redis8.0.0NullUnknown License
respx0.23.1NullUnknown License
rpds-py2026.5.1NullUnknown License
ruamel-yaml0.19.1NullUnknown License
ruff0.15.17NullUnknown License
safety3.8.1NullUnknown License
soupsieve2.8.4NullUnknown License
starlette1.3.1NullUnknown License
stevedore5.8.0NullUnknown License
structlog26.1.0NullUnknown License
tomlkit0.15.0NullUnknown License
tornado6.5.7NullUnknown License
tqdm4.68.2NullUnknown License
traitlets5.15.1NullUnknown License
virtualenv21.5.0NullUnknown License
vulture2.16NullUnknown License
wcwidth0.8.1NullUnknown License
bleach6.4.0NullUnknown License
jedi0.20.0NullUnknown License
parso0.8.7NullUnknown License
Allowed Licenses: MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0, LGPL-2.1, LGPL-3.0, Python-2.0, Unlicense, CC0-1.0, GPL-3.0-or-later

OpenSSF Scorecard

Scorecard details
PackageVersionScoreDetails
pip/anyio 4.13.0 UnknownUnknown
pip/async-lru 2.3.0 🟢 6.9
Details
CheckScoreReason
Code-Review🟢 7Found 6/8 approved changesets -- score normalized to 7
Maintained🟢 1022 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts🟢 10no binaries found in the repo
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases🟢 85 out of the last 5 releases have a total of 5 signed artifacts.
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Security-Policy🟢 10security policy file detected
Packaging🟢 10packaging workflow detected
SAST🟢 10SAST tool is run on all commits
pip/attrs 26.1.0 UnknownUnknown
pip/authlib 1.7.2 UnknownUnknown
pip/babel 2.18.0 UnknownUnknown
pip/backrefs 7.0 UnknownUnknown
pip/bandit 1.9.4 UnknownUnknown
pip/basedpyright 1.39.8 UnknownUnknown
pip/beautifulsoup4 4.15.0 UnknownUnknown
pip/bleach 6.4.0 🟢 6
Details
CheckScoreReason
Code-Review⚠️ 0Found 0/17 approved changesets -- score normalized to 0
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Security-Policy🟢 10security policy file detected
Maintained🟢 1015 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies🟢 4dependency not pinned by hash detected -- score normalized to 4
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing🟢 10project is fuzzed
License🟢 9license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
pip/certifi 2026.5.20 🟢 5.9
Details
CheckScoreReason
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Security-Policy🟢 10security policy file detected
Maintained🟢 89 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
Binary-Artifacts🟢 10no binaries found in the repo
Code-Review⚠️ 0Found 0/2 approved changesets -- score normalized to 0
Token-Permissions🟢 10GitHub workflow tokens follow principle of least privilege
Pinned-Dependencies🟢 5dependency not pinned by hash detected -- score normalized to 5
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 9license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
Packaging🟢 10packaging workflow detected
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
pip/charset-normalizer 3.4.7 UnknownUnknown
pip/click 8.4.1 UnknownUnknown
pip/cloudflare 5.3.0 UnknownUnknown
pip/coverage 7.14.1 UnknownUnknown
pip/cryptography 49.0.0 UnknownUnknown
pip/cyclonedx-python-lib 11.10.0 UnknownUnknown
pip/debugpy 1.8.21 UnknownUnknown
pip/decorator 5.3.1 UnknownUnknown
pip/distlib 0.4.3 UnknownUnknown
pip/fastapi 0.137.0 UnknownUnknown
pip/filelock 3.29.4 UnknownUnknown
pip/gitpython 3.1.50 🟢 7.7
Details
CheckScoreReason
Code-Review🟢 6Found 4/6 approved changesets -- score normalized to 6
Security-Policy🟢 10security policy file detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Maintained🟢 1030 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Token-Permissions🟢 9detected GitHub workflow tokens with excessive permissions
Binary-Artifacts🟢 10no binaries found in the repo
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Fuzzing🟢 10project is fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection🟢 3branch protection is not maximal on development and all release branches
SAST🟢 10SAST tool is run on all commits
pip/google-api-core 2.31.0 UnknownUnknown
pip/google-auth 2.54.0 UnknownUnknown
pip/google-cloud-core 2.6.0 🟢 6.9
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Security-Policy🟢 10security policy file detected
License🟢 10license file detected
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
Signed-Releases⚠️ -1no releases found
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
Fuzzing🟢 10project is fuzzed
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
pip/google-cloud-storage 3.12.0 UnknownUnknown
pip/google-crc32c 1.8.0 🟢 7.2
Details
CheckScoreReason
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Security-Policy🟢 10security policy file detected
Token-Permissions🟢 10GitHub workflow tokens follow principle of least privilege
Code-Review🟢 10all changesets reviewed
Packaging⚠️ -1packaging workflow not detected
Maintained⚠️ 0project is archived
Binary-Artifacts🟢 10no binaries found in the repo
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies⚠️ 2dependency not pinned by hash detected -- score normalized to 2
Fuzzing🟢 10project is fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
SAST⚠️ 2SAST tool is not run on all commits -- score normalized to 2
pip/google-genai 2.8.0 UnknownUnknown
pip/google-resumable-media 2.10.0 🟢 6.9
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Security-Policy🟢 10security policy file detected
License🟢 10license file detected
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
Signed-Releases⚠️ -1no releases found
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
Fuzzing🟢 10project is fuzzed
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
pip/googleapis-common-protos 1.75.0 UnknownUnknown
pip/griffe-pydantic 1.3.1 UnknownUnknown
pip/griffelib 2.0.2 UnknownUnknown
pip/hiredis 3.4.0 🟢 5
Details
CheckScoreReason
Maintained🟢 79 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Binary-Artifacts🟢 10no binaries found in the repo
Code-Review🟢 3Found 10/28 approved changesets -- score normalized to 3
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Security-Policy⚠️ 0security policy file not detected
Packaging⚠️ -1packaging workflow not detected
Fuzzing🟢 10project is fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
pip/humanize 4.15.0 UnknownUnknown
pip/hypothesis 6.155.2 UnknownUnknown
pip/identify 2.6.19 🟢 5.9
Details
CheckScoreReason
Packaging⚠️ -1packaging workflow not detected
Code-Review🟢 8Found 12/15 approved changesets -- score normalized to 8
Maintained🟢 1015 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Fuzzing⚠️ 0project is not fuzzed
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Security-Policy🟢 10security policy file detected
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
pip/idna 3.18 UnknownUnknown
pip/ipykernel 7.3.0 UnknownUnknown
pip/ipython 8.39.0 UnknownUnknown
pip/ipython 9.14.1 UnknownUnknown
pip/jedi 0.20.0 🟢 5
Details
CheckScoreReason
Maintained🟢 1030 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
Code-Review⚠️ 0Found 0/4 approved changesets -- score normalized to 0
Security-Policy🟢 10security policy file detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts🟢 9binaries present in source code
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Fuzzing🟢 10project is fuzzed
Signed-Releases⚠️ -1no releases found
License🟢 9license file detected
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
pip/joblib 1.5.3 UnknownUnknown
pip/joserfc 1.7.1 UnknownUnknown
pip/json5 0.14.0 UnknownUnknown
pip/jsonpointer 3.1.1 🟢 4.6
Details
CheckScoreReason
Code-Review🟢 5Found 4/7 approved changesets -- score normalized to 5
Maintained🟢 1013 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Packaging⚠️ -1packaging workflow not detected
Binary-Artifacts🟢 10no binaries found in the repo
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Security-Policy⚠️ 0security policy file not detected
Fuzzing⚠️ 0project is not fuzzed
Signed-Releases⚠️ -1no releases found
License🟢 9license file detected
Branch-Protection🟢 3branch protection is not maximal on development and all release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
pip/jsonschema 4.26.0 UnknownUnknown
pip/jupyter-client 8.9.1 UnknownUnknown
pip/jupyter-events 0.12.1 UnknownUnknown
pip/jupyter-lsp 2.3.1 UnknownUnknown
pip/jupyter-server 2.19.0 UnknownUnknown
pip/jupyter-server-terminals 0.5.4 UnknownUnknown
pip/jupyterlab 4.5.8 UnknownUnknown
pip/markdown 3.10.2 UnknownUnknown
pip/markdown-it-py 4.2.0 UnknownUnknown
pip/marshmallow 4.3.0 UnknownUnknown
pip/matplotlib-inline 0.2.2 UnknownUnknown
pip/mistune 3.2.1 UnknownUnknown
pip/mkdocs-autorefs 1.4.4 UnknownUnknown
pip/mkdocs-gen-files 0.6.1 UnknownUnknown
pip/mkdocs-get-deps 0.2.2 UnknownUnknown
pip/mkdocs-git-revision-date-localized-plugin 1.5.3 UnknownUnknown
pip/mkdocs-material 9.7.6 UnknownUnknown
pip/mkdocs-section-index 0.3.12 UnknownUnknown
pip/mkdocstrings 1.0.4 UnknownUnknown
pip/mkdocstrings-python 2.0.4 UnknownUnknown
pip/msgpack 1.2.0 UnknownUnknown
pip/nbclient 0.11.0 UnknownUnknown
pip/nbconvert 7.17.1 UnknownUnknown
pip/nest-asyncio2 1.7.2 UnknownUnknown
pip/nltk 3.9.4 UnknownUnknown
pip/nodeenv 1.10.0 ⚠️ 2.8
Details
CheckScoreReason
Maintained⚠️ 00 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts🟢 10no binaries found in the repo
Packaging⚠️ -1packaging workflow not detected
Code-Review⚠️ 1Found 5/30 approved changesets -- score normalized to 1
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Security-Policy⚠️ 0security policy file not detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 9license file detected
Signed-Releases⚠️ -1no releases found
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
pip/nodejs-wheel-binaries 24.16.0 UnknownUnknown
pip/notebook 7.5.7 UnknownUnknown
pip/nox 2026.4.10 UnknownUnknown
pip/nox-uv 0.8.0 UnknownUnknown
pip/packaging 26.2 UnknownUnknown
pip/parso 0.8.7 🟢 4.9
Details
CheckScoreReason
Maintained🟢 33 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Security-Policy🟢 10security policy file detected
Packaging⚠️ -1packaging workflow not detected
Code-Review🟢 5Found 7/13 approved changesets -- score normalized to 5
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing🟢 10project is fuzzed
License🟢 9license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
pip/pathspec 1.1.1 UnknownUnknown
pip/pip 26.1.2 UnknownUnknown
pip/pip-audit 2.10.1 UnknownUnknown
pip/platformdirs 4.10.0 UnknownUnknown
pip/pre-commit 4.6.0 🟢 4.6
Details
CheckScoreReason
Packaging⚠️ -1packaging workflow not detected
Code-Review⚠️ 1Found 1/7 approved changesets -- score normalized to 1
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Maintained🟢 1019 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Binary-Artifacts🟢 10no binaries found in the repo
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing⚠️ 0project is not fuzzed
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
License🟢 10license file detected
Signed-Releases⚠️ 0Project has not signed or included provenance with any releases.
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Security-Policy🟢 10security policy file detected
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
pip/prometheus-client 0.25.0 UnknownUnknown
pip/properdocs 1.6.7 UnknownUnknown
pip/proto-plus 1.28.0 UnknownUnknown
pip/protobuf 7.35.1 UnknownUnknown
pip/psutil 7.2.2 UnknownUnknown
pip/pyasn1 0.6.3 UnknownUnknown
pip/pycparser 3.0 UnknownUnknown
pip/pydantic 2.13.4 UnknownUnknown
pip/pydantic-core 2.46.4 🟢 7.4
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Maintained🟢 1030 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Binary-Artifacts🟢 10no binaries found in the repo
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies🟢 8dependency not pinned by hash detected -- score normalized to 8
License🟢 10license file detected
Fuzzing🟢 10project is fuzzed
Signed-Releases⚠️ -1no releases found
Branch-Protection🟢 4branch protection is not maximal on development and all release branches
Security-Policy🟢 10security policy file detected
Packaging🟢 10packaging workflow detected
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
pip/pydantic-settings 2.14.1 UnknownUnknown
pip/pydoclint 0.8.6 UnknownUnknown
pip/pygments 2.20.0 UnknownUnknown
pip/pyjwt 2.13.0 UnknownUnknown
pip/pymdown-extensions 10.21.3 UnknownUnknown
pip/pyparsing 3.3.2 UnknownUnknown
pip/pytest 9.1.0 UnknownUnknown
pip/pytest-asyncio 1.4.0 UnknownUnknown
pip/pytest-cov 7.1.0 UnknownUnknown
pip/python-discovery 1.4.2 UnknownUnknown
pip/python-dotenv 1.2.2 UnknownUnknown
pip/python-frontmatter 1.3.0 UnknownUnknown
pip/python-json-logger 4.1.0 UnknownUnknown
pip/pywinpty 3.0.5 UnknownUnknown
pip/redis 8.0.0 UnknownUnknown
pip/regex 2026.5.9 UnknownUnknown
pip/requests 2.34.2 UnknownUnknown
pip/respx 0.23.1 UnknownUnknown
pip/rich 15.0.0 UnknownUnknown
pip/rpds-py 2026.5.1 UnknownUnknown
pip/ruamel-yaml 0.19.1 UnknownUnknown
pip/ruff 0.15.17 UnknownUnknown
pip/safety 3.8.1 UnknownUnknown
pip/send2trash 2.1.0 UnknownUnknown
pip/setuptools 82.0.1 UnknownUnknown
pip/smmap 5.0.3 🟢 5.2
Details
CheckScoreReason
Code-Review🟢 6Found 6/10 approved changesets -- score normalized to 6
Packaging⚠️ -1packaging workflow not detected
Binary-Artifacts🟢 10no binaries found in the repo
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Maintained⚠️ 00 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Security-Policy🟢 9security policy file detected
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Token-Permissions🟢 10GitHub workflow tokens follow principle of least privilege
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST🟢 3SAST tool is not run on all commits -- score normalized to 3
pip/soupsieve 2.8.4 UnknownUnknown
pip/starlette 1.3.1 UnknownUnknown
pip/stevedore 5.8.0 UnknownUnknown
pip/structlog 26.1.0 UnknownUnknown
pip/tabulate 0.10.0 UnknownUnknown
pip/tenacity 9.1.4 🟢 5.9
Details
CheckScoreReason
Code-Review🟢 10all changesets reviewed
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Maintained🟢 33 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
Token-Permissions🟢 9detected GitHub workflow tokens with excessive permissions
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Packaging🟢 10packaging workflow detected
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Security-Policy⚠️ 0security policy file not detected
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
pip/tinycss2 1.5.1 UnknownUnknown
pip/tomli 2.4.1 UnknownUnknown
pip/tomlkit 0.15.0 UnknownUnknown
pip/tornado 6.5.7 UnknownUnknown
pip/tqdm 4.68.2 UnknownUnknown
pip/traitlets 5.15.1 UnknownUnknown
pip/truststore 0.10.4 UnknownUnknown
pip/typer 0.25.1 UnknownUnknown
pip/tzdata 2026.2 🟢 7.3
Details
CheckScoreReason
Maintained🟢 1014 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Code-Review🟢 7Found 18/23 approved changesets -- score normalized to 7
Token-Permissions🟢 9detected GitHub workflow tokens with excessive permissions
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies🟢 4dependency not pinned by hash detected -- score normalized to 4
License🟢 9license file detected
Fuzzing⚠️ 0project is not fuzzed
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Security-Policy🟢 10security policy file detected
Packaging🟢 10packaging workflow detected
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
pip/urllib3 2.7.0 UnknownUnknown
pip/virtualenv 21.5.0 UnknownUnknown
pip/vulture 2.16 UnknownUnknown
pip/wcwidth 0.8.1 UnknownUnknown
pip/websockets 16.0 UnknownUnknown

Scanned Files

  • uv.lock

@sonarqubecloud

Copy link
Copy Markdown

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: pypi jupyterlab is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/jupyter@1.1.1pypi/jupyterlab@4.5.8

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/jupyterlab@4.5.8. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nltk is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/safety@3.8.1pypi/nltk@3.9.4

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nltk@3.9.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nltk is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/safety@3.8.1pypi/nltk@3.9.4

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nltk@3.9.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi nodejs-wheel-binaries is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/basedpyright@1.39.8pypi/nodejs-wheel-binaries@24.16.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/nodejs-wheel-binaries@24.16.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi pycparser is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/ipykernel@7.3.0pypi/cryptography@49.0.0pypi/jupyter@1.1.1pypi/pycparser@3.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pycparser@3.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: pypi pycparser is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: uv.lockpypi/ipykernel@7.3.0pypi/cryptography@49.0.0pypi/jupyter@1.1.1pypi/pycparser@3.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pycparser@3.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@codecov

codecov Bot commented Jun 15, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants