posthog 7.75.1
- Source
- https://github.com/posthog/posthog-python
- Tag scanned
posthog-v7.75.1- Compared with
posthog-v7.75.0(0 signals introduced since)- Files
- 441 scanned, 283 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 2 warn · 8 info
- Scan time
- 10.6 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 9 of 9 warn and critical signals; 7 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+…⟩.
-
return return flikely benign A calculator tool in an OpenAI Agents example evaluates a character-filtered expression with eval.Reasoning
eval is applied to an expression that has been filtered for invalid characters just above, and the code is example calculator-tool code. Still, eval on model-supplied input is a known code-injection hazard, and the character filter is not a sandbox, so this is a poor pattern rather than evidence of malicious intent.
-
return return flikely benign A single-agent calculator example evaluates a character-filtered expression with eval.Reasoning
This is the same calculator-tool eval pattern as the multi-agent example, with the same character pre-filter. It is an insecure example pattern, not an obfuscated or malicious payload.
-
= += 1likely benign Exception-reporting utility walks stack frames via sys._getframe to gather context.Reasoning
Walking the call stack with sys._getframe(depth) in a loop that catches ValueError is the standard way exception-reporting libraries collect frame information. The context is legitimate.
-
) = # Encode side: our output is byte-identical to the shared wire format.likely benign Test fixture containing a base64url-encoded JSON session token.Reasoning
The blob is a short base64url JSON fixture (session id, client name, version, timestamp) used as a shared wire-format test vector in a test file. It is not hidden or executed.
-
# zlib header =dismissed Test round-trips and inspects a zlib-compressed request body.Reasoning
The test decompresses a zlib payload it just generated, checks the zlib header, and asserts that the API key is absent from the round-tripped JSON. This is a normal test assertion, not a runtime-dropped payload.
-
= returndismissed Test helper decompresses a gzip request body captured from a mock.Reasoning
The helper gunzips the mocked HTTP request body to inspect the JSON that was sent. This is test-side verification of the client's own output.
-
=dismissed Test decompresses a gzip request body to check its contents.Reasoning
The test gunzips the request body and checks the batch and API key fields. This is ordinary assertion code on the library's own output.
-
info
warn→ info by reviewdecoder-decompress-payloadposthog/test/tracing/test_client_traces.py:60:23, = return , ,dismissed Test helper decompresses a gzip POST body from a mock session.Reasoning
The helper gunzips the mocked session.post data so the test can compare the JSON payload. This is standard test plumbing.
-
assert == assert ==dismissed Transport test decompresses a gzip body and compares it with the expected payload.Reasoning
The assertion gunzips the outgoing request body and compares it to the expected PAYLOAD. This is a test checking transport output.
-
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.
&&