posthog 7.70.0

Source: https://github.com/posthog/posthog-python
Tag scanned: posthog-v7.70.0
Compared with: posthog-v7.69.0 (0 signals introduced since)
Files: 426 scanned, 272 skipped (binary, oversized, or unrecognised)
Signals: 0 critical · 0 warn · 10 info
Scan time: 10.7 s
LLM review: Reviewed by claude-haiku-5-5 (Anthropic): 9 of 9 warn and critical signals; 9 demoted to info.
Disclude version: 4.0.0
Scanned (UTC): 2026-10-15 18:12

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.70 A demo calculator tool evaluates an arithmetic expression with eval after a character check.
Reasoning
eval runs on an expression that comes from agent or user input. That is a real code-injection risk in a sample, but the snippet shows a character check ('Error: invalid characters') guarding it, and there is no obfuscation or hidden payload. It is an unsafe example pattern rather than malicious code.
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.70 A single-agent demo calculator evaluates an arithmetic expression with eval after a character check.
Reasoning
Same eval-on-input pattern as multi_agent.py, with the same validation guard visible in the snippet. It is an example-code risk, not evidence of 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.92 Exception utility code walks stack frames via sys._getframe to gather caller context.
Reasoning
Walking the call stack with sys._getframe(depth) inside a try/except ValueError is a standard way to inspect caller frames for module or context names in exception reporting. Nothing here hides behavior.
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.
```
likely benign LLM, confidence 0.93 A test fixture holds a base64url-encoded session token used to verify the wire format.
Reasoning
The string is a base64url-encoded JSON fixture (it begins with eyJ and decodes to a small session object with plain fields). It is a test fixture for a wire-format encode/decode check, 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))
```
likely benign LLM, confidence 0.94 A test decompresses a captured zlib request body to check its contents.
Reasoning
zlib.decompress is applied to a request body captured from a mocked call, then parsed as JSON to assert that the api_key is absent. This is ordinary test verification of compressed request payloads, not a runtime-embedded payload.
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"))
```
likely benign LLM, confidence 0.94 A test helper decompresses a captured gzip request body and parses the JSON.
Reasoning
gzip.decompress is applied to a mocked request body and parsed as JSON in a test helper. This is standard handling of compressed HTTP payloads in tests.
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)
```
likely benign LLM, confidence 0.94 A request test decompresses a captured gzip body to check its JSON fields.
Reasoning
The test decompresses a captured gzip body to assert on batch and api_key fields. This is ordinary test assertion code with no hidden or dynamic payload.
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
```
likely benign LLM, confidence 0.94 A tracing test helper decompresses a mocked gzip POST body and parses it.
Reasoning
A helper decompresses a mocked session POST body and parses it as JSON for trace assertions. This is routine test plumbing.
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):
```
likely benign LLM, confidence 0.94 A transport test decompresses the gzip body sent to a mocked post and compares it to the expected payload.
Reasoning
The test decompresses the gzip data passed to a mocked post and compares it with an expected payload. This is standard transport verification in a test.

info long-line references/public_api_snapshot.txt:1208: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.0.0
git clone https://github.com/posthog/posthog-python posthog-python && cd posthog-python
git checkout posthog-v7.70.0
disclude scan --severity info --diff posthog-v7.69.0 .