PyPI / sentry-sdk / 3.0.0b1
sentry-sdk 3.0.0b1
- Source
- https://github.com/getsentry/sentry-python
- Artifact scanned
sentry_sdk-3.0.0b1-py3-none-any.whl- Compared with
sentry_sdk-3.0.0a7-py2.py3-none-any.whl(3 signals introduced since)- Files
- 198 scanned, 5 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 3 info
- Scan time
- 3.9 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 3 of 3 warn and critical signals; 3 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-23 09:51
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
in . : """likely benign A base64-like example AWS request ID appears in a docstring.Reasoning
The flagged string is an AWS extended request ID example inside a docstring. It is documentation text, not an encoded payload, and the raw pass has a high false-positive rate on base64-looking strings.
-
info
warn→ info by reviewframe-introspectionsentry_sdk/tracing_utils.py:284:39new in this release# Find the correct frame : = =likely benign sys._getframe is used to locate the correct stack frame for module path resolution.Reasoning
Walking the call stack with sys._getframe to find the first frame outside the SDK is a standard technique in Sentry's tracing code for determining the caller's module path. It is not malicious and is not obfuscation.
-
: =likely benign sys._getframe walks the call stack to filter frames for error reporting.Reasoning
Stack walking with sys._getframe to skip hidden frames when building an error stack trace is legitimate error-reporting behavior in an SDK, with no decoding, execution, or network activity.
Reproduce This Scan
Run disclude locally to verify. These commands scan the published file; the "new in this release" marks come from comparing it with the previous release's file, which they don't repeat. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
|