Statsig

Latest version: v0.33.0

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

Scan your dependencies

Page 9 of 11

0.10.0

Typing input as StatsigUser instead of object, typing log events, the value of log events as number or string, and optional types for nullable fields across StatsigOptions, StatsigUser, and StatsigEvent

0.9.3

fixed "before" and "after" operator for Time based conditions

0.9.2

Now the SDK only requires either a userID or any customID

0.9.0

Previously exposures for Layers happen when you call `getLayer()`, but when you have multiple experiments running in parallel in the same Layer, this could be exposing more users than the actual number of users who were actually exposed to some of the experiments, so with this release we have moved the exposure logic to be happening when `Layer.get()` method is called, so that a user is only exposed to an experiment when the parameter for that experiment is fetched.

0.8.2

Add debug logging information, stringify user object more gracefully, add server session id header, copy user on normalization rather than modifying

0.8.1

- added a new API `get_layer`, which returns a layer object that would return the correct parameter value for the given user within the layer, no matter which experiment the user is allocated to within the layer;
- fixed a bug where `time` was not added to events;
- fixed a bug where `/get_config` fallback was not correctly called in the event that the SDK does not know how to evaluate a rule locally.

Page 9 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.