posthog 7.74.0

Source: https://github.com/posthog/posthog-python
Tag scanned: posthog-v7.74.0
Compared with: posthog-v7.73.3 (0 signals introduced since)
Files: 435 scanned, 281 skipped (binary, oversized, or unrecognised)
Signals: 0 critical · 0 warn · 10 info
Scan time: 10.3 s
LLM review: Reviewed by claude-haiku-5-5 (Anthropic): 9 of 9 warn and critical signals; 9 demoted to info.
Disclude version: 4.1.0
Scanned (UTC): 2026-10-22 13:44

Signals

Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.

info ~~warn~~ → info by review dynamic-execution examples/example-ai-openai-agents/multi_agent.py:29:23

`eval` called on a non-literal expression (ast pass, confidence 0.70)
```
        return "Error: invalid characters"
    return f"Result: {eval(expression.replace('^', '**'))}"
```
likely benign LLM, confidence 0.72 An example calculator tool evaluates a filtered arithmetic expression with eval.
Reasoning
eval is applied to a user-supplied expression after a character check and a ^ to ** substitution, which is a calculator tool in an example. Eval on agent-controlled input is an unsafe pattern, but nothing suggests hidden or malicious intent.
info ~~warn~~ → info by review dynamic-execution examples/example-ai-openai-agents/single_agent.py:29:23

`eval` called on a non-literal expression (ast pass, confidence 0.70)
```
        return "Error: invalid characters"
    return f"Result: {eval(expression.replace('^', '**'))}"
```
likely benign LLM, confidence 0.72 An example single-agent calculator evaluates a filtered arithmetic expression with eval.
Reasoning
Same calculator pattern as multi_agent.py: eval on a character-filtered arithmetic expression in an example file. Unsafe but not evidence of obfuscation or malicious intent.
info ~~warn~~ → info by review frame-introspection posthog/exception_utils.py:1060:21

`sys._getframe` — call-stack frame introspection (ast pass, confidence 0.70)
```
        try:
            frame = sys._getframe(depth)
            depth += 1
        except ValueError:
```
likely benign LLM, confidence 0.90 Exception utility walks the call stack via sys._getframe to collect frames.
Reasoning
sys._getframe in a loop with depth increments and a ValueError fallback is the standard way an exception reporter walks the stack. This is ordinary SDK behaviour.
info ~~warn~~ → info by review encoding-base64 posthog/test/mcp/test_session_token.py:68:15

base64-like blob (95 bytes, compression ratio 1.12) (raw pass, confidence 0.60)
```
    )
    frozen = "eyJzaWQiOiJzZXNfZml4dHVyZSIsImNuIjoiQ2xhdWRlIENvZGUiLCJjdiI6IjEuMi4zIiwicHYiOiIyMDI1LTA2LTE4In0"

    # Encode side: our output is byte-identical to the shared wire format.
```
dismissed LLM, confidence 0.93 A base64url-encoded session token fixture in a unit test.
Reasoning
The base64 string is a fixed test fixture encoding a small JSON session object, and the surrounding comment describes a wire-format encode check. This is a test vector, not a hidden payload.
info ~~warn~~ → info by review decoder-decompress-payload posthog/test/test_capture_v1.py:456:24

file imports decoder module(s) zlib and calls `.decompress()` — embedded payload decompressed at runtime (ast pass, confidence 0.75)
```
        self.assertEqual(call["data"][0], 0x78)  # zlib header
        roundtripped = zlib.decompress(call["data"]).decode("utf-8")
        self.assertNotIn("api_key", json.loads(roundtripped))
```
dismissed LLM, confidence 0.93 Test decompresses a captured zlib request body to verify its contents.
Reasoning
zlib.decompress is used in a test to round-trip a captured request body and assert that the API key is absent. The test checks the payload rather than running an embedded one.
info ~~warn~~ → info by review decoder-decompress-payload posthog/test/test_metrics.py:55:23

file imports decoder module(s) gzip and calls `.decompress()` — embedded payload decompressed at runtime (ast pass, confidence 0.75)
```
    body = kwargs.get("data")
    return json.loads(gzip.decompress(body).decode("utf-8"))
```
dismissed LLM, confidence 0.93 Test helper decompresses a gzip request body to inspect JSON.
Reasoning
gzip.decompress is used in a test helper to parse a captured request body as JSON. This is a standard test assertion path.
info ~~warn~~ → info by review decoder-decompress-payload posthog/test/test_request.py:227:27

file imports decoder module(s) gzip, zlib and calls `.decompress()` — embedded payload decompressed at runtime (ast pass, confidence 0.75)
```
        self.assertEqual(headers["Content-Encoding"], "gzip")
        body = json.loads(gzip.decompress(data))
        self.assertEqual(body["batch"], [])
        self.assertEqual(body["api_key"], TEST_API_KEY)
```
dismissed LLM, confidence 0.93 Test decompresses gzip request data and asserts on its JSON fields.
Reasoning
gzip.decompress on captured request data followed by JSON assertions on batch and api_key. This is normal test verification of an SDK request.
info ~~warn~~ → info by review decoder-decompress-payload posthog/test/tracing/test_client_traces.py:60:23

file imports decoder module(s) gzip and calls `.decompress()` — embedded payload decompressed at runtime (ast pass, confidence 0.75)
```
    args, kwargs = session.post.call_args
    return json.loads(gzip.decompress(kwargs["data"])), args[0], kwargs
```
dismissed LLM, confidence 0.93 Tracing test helper decompresses a mocked POST body for assertions.
Reasoning
gzip.decompress of a mocked session.post payload to compare against expected data. It is a test helper with no runtime payload execution.
info ~~warn~~ → info by review decoder-decompress-payload posthog/test/tracing/test_transport.py:71:27

file imports decoder module(s) gzip and calls `.decompress()` — embedded payload decompressed at runtime (ast pass, confidence 0.75)
```
        assert kwargs["headers"]["Content-Type"] == "application/json"
        assert json.loads(gzip.decompress(kwargs["data"])) == PAYLOAD

    def test_falls_back_to_the_default_timeout(self):
```
dismissed LLM, confidence 0.93 Transport test decompresses a mocked gzip body to compare with the expected payload.
Reasoning
gzip.decompress of mocked request data compared against a fixed PAYLOAD. This is ordinary transport testing.

info long-line references/public_api_snapshot.txt:1279:1

line length 1545 characters (raw pass, confidence 0.50)

class posthog.client.Client(project_api_key: str, host=None, debug=False, max_queue_size=10000, send=True, on_error=None, flush_at=100, flush_interval=5.0, gzip=False, max_retries=3, sync_mode=False, timeout=15, thread=1, poll_interval=30, personal_api_key=None, disabled=False, disable_geoip=True, is_server=True, histo

Reproduce This Scan

Run disclude locally to verify. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.

cargo install disclude --version 4.1.0
git clone https://github.com/posthog/posthog-python posthog-python && cd posthog-python
git checkout posthog-v7.74.0
disclude scan --severity info --diff posthog-v7.73.3 .