| Warn |
 |
Obfuscated code: cargo hyper-util is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → cargo/pyroscope@2.0.6 → cargo/hyper-util@0.1.20
ℹ 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 cargo/hyper-util@0.1.20. 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 |
|
Obfuscated code: cargo libc is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → cargo/chrono@0.4.44 → cargo/tokio@1.50.0 → cargo/pyroscope@2.0.6 → cargo/warp@0.3.7 → cargo/pretty_env_logger@0.5.0 → cargo/libc@0.2.184
ℹ 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 cargo/libc@0.2.184. 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 |
|
Obfuscated code: cargo tokio is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: examples/language-sdk-instrumentation/rust/rideshare/server/Cargo.lock → cargo/tokio@1.50.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 cargo/tokio@1.50.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 |
|
Obfuscated code: cargo writeable is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → cargo/pyroscope@2.0.6 → cargo/warp@0.3.7 → cargo/writeable@0.6.2
ℹ 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 cargo/writeable@0.6.2. 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 |
|
Obfuscated code: cargo zerocopy is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → cargo/pyroscope@2.0.6 → cargo/warp@0.3.7 → cargo/zerocopy@0.8.48
ℹ 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 cargo/zerocopy@0.8.48. 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 |
|
Obfuscated code: gem activerecord is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: examples/language-sdk-instrumentation/ruby/rideshare_rails/Gemfile.lock → gem/rails@7.2.3.1 → gem/activestorage@7.2.3.1 → gem/activerecord@7.2.3.1
ℹ 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 gem/activerecord@7.2.3.1. 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 |
|
Obfuscated code: gem activesupport is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: examples/language-sdk-instrumentation/ruby/rideshare_rails/Gemfile.lock → gem/rails@7.2.3.1 → gem/activestorage@7.2.3.1 → gem/sprockets-rails@3.5.2 → gem/activesupport@7.2.3.1
ℹ 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 gem/activesupport@7.2.3.1. 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 |
|
Obfuscated code: gem erb is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: examples/language-sdk-instrumentation/ruby/rideshare_rails/Gemfile.lock → gem/debug@1.11.1 → gem/rails@7.2.3.1 → gem/erb@6.0.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 gem/erb@6.0.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 |
|
Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → golang/github.com/prometheus/prometheus@v0.311.3 → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 |
|
Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → golang/github.com/prometheus/prometheus@v0.311.3 → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 |
|
Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → golang/github.com/prometheus/prometheus@v0.311.3 → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 |
|
Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → golang/github.com/prometheus/prometheus@v0.311.3 → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 |
|
Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → golang/github.com/prometheus/prometheus@v0.311.3 → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 |
|
Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → golang/github.com/prometheus/prometheus@v0.311.3 → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.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 |
|
Obfuscated code: golang github.com/googleapis/enterprise-certificate-proxy is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → golang/github.com/prometheus/prometheus@v0.311.3 → golang/github.com/grafana/dskit@v0.0.0-20260616135346-e96eda8260cd → golang/github.com/thanos-io/objstore@v0.0.0-20250813080715-4e5fd4289b50 → golang/github.com/googleapis/enterprise-certificate-proxy@v0.3.14
ℹ 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 golang/github.com/googleapis/enterprise-certificate-proxy@v0.3.14. 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 |
|
Obfuscated code: golang github.com/modern-go/reflect2 is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → golang/github.com/prometheus/prometheus@v0.311.3 → golang/github.com/grafana/dskit@v0.0.0-20260616135346-e96eda8260cd → golang/github.com/hashicorp/raft@v1.7.3 → golang/github.com/prometheus/client_golang@v1.23.2 → golang/github.com/modern-go/reflect2@v1.0.3-0.20250322232337-35a7c28c31ee
ℹ 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 golang/github.com/modern-go/reflect2@v1.0.3-0.20250322232337-35a7c28c31ee. 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 |
|
Obfuscated code: golang github.com/planetscale/vtprotobuf is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: api/go.mod → golang/github.com/planetscale/vtprotobuf@v0.6.1-0.20250313105119-ba97887b0a25
ℹ 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 golang/github.com/planetscale/vtprotobuf@v0.6.1-0.20250313105119-ba97887b0a25. 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 |
|
Obfuscated code: golang go.uber.org/automaxprocs is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: go.mod → golang/go.uber.org/automaxprocs@v1.6.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 golang/go.uber.org/automaxprocs@v1.6.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 |
|
Obfuscated code: golang golang.org/x/tools is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → golang/golang.org/x/exp@v0.0.0-20260410095643-746e56fc9e2f → golang/github.com/minio/minio-go/v7@v7.1.0 → golang/github.com/grafana/pyroscope/api@v1.5.0 → golang/github.com/prometheus/prometheus@v0.311.3 → golang/golang.org/x/mod@v0.37.0 → golang/github.com/grafana/dskit@v0.0.0-20260616135346-e96eda8260cd → golang/golang.org/x/text@v0.39.0 → golang/github.com/hashicorp/raft@v1.7.3 → golang/golang.org/x/tools@v0.47.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 golang/golang.org/x/tools@v0.47.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 |
|
Obfuscated code: golang k8s.io/client-go is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → golang/github.com/prometheus/prometheus@v0.311.3 → golang/k8s.io/client-go@v0.35.3
ℹ 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 golang/k8s.io/client-go@v0.35.3. 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 |
|
Obfuscated code: npm js-yaml is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: ? → npm/eslint@9.39.4 → npm/js-yaml@4.2.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 npm/js-yaml@4.2.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 |
|
Obfuscated code: pypi flask is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: examples/language-sdk-instrumentation/python/rideshare/flask/requirements.txt → pypi/flask@3.1.3
ℹ 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/flask@3.1.3. 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 |
|
Obfuscated code: pypi pycparser is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: examples/language-sdk-instrumentation/python/rideshare/django/app/requirements.txt → pypi/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 |
|
Obfuscated code: pypi pycparser is 90.0% likely obfuscated
Confidence: 0.90
Location: Package overview
From: examples/language-sdk-instrumentation/python/rideshare/django/app/requirements.txt → pypi/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.
|
