Sentry

Latest version: v23.7.1

Safety actively analyzes 682532 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 39 of 223

7.5.5

------

- [Security] An XSS vulnerability was addressed with low cardinality tags and the stream filter box:
https://github.com/getsentry/sentry/commit/364b959811561de83f29893e105cc590224edbee

7.5.4

Not secure
------

- Yet another case where valid team membership was being excluded.

7.5.3

Not secure
------

- Fix another case where valid team membership was being excluded

7.5.2

Not secure
------

- Correctly support SENTRY_PROJECT.

7.5.1

Not secure
This release removes the `user_id` and the `transaction` field from the dynamic sampling context data that is attached to outgoing requests as well as sent to Relay.

- ref(tracing): Remove transaction name and user_id from DSC (5363)

7.5.0

Not secure
This release adds the `sendDefaultPii` flag to the `Sentry.init` options.
When using performance monitoring capabilities of the SDK, it controls whether user IDs (set via `Sentry.setUser`) are propagated in the `baggage` header of outgoing HTTP requests.
This flag is set to `false` per default, and acts as an opt-in mechanism for sending potentially sensitive data.
If you want to attach user IDs to Sentry transactions and traces, set this flag to `true` but keep in mind that this is potentially sensitive information.

- feat(sdk): Add sendDefaultPii option to the JS SDKs (5341)
- fix(remix): Sourcemaps upload script is missing in the tarball (5356)
- fix(remix): Use cjs for main entry point (5352)
- ref(tracing): Only add `user_id` to DSC if `sendDefaultPii` is `true` (5344)

Work in this release contributed by jkcorrea and nfelger. Thank you for your contributions!

Page 39 of 223

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.