kombu 5.7.0rc1
- Source
- https://github.com/celery/kombu
- Tag scanned
v5.7.0rc1- Compared with
v5.7.0b1(0 signals introduced since)- Files
- 316 scanned, 18 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 16 info
- Scan time
- 13.2 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 16 of 16 warn and critical signals; 16 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-19 03:10
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
= True = False # pragma: no cover # This is never executed, but tricks static analyzers (PyDev, PyCharm,likely benign Lazy-import/static-analyzer hack writing a globals entry via reversed string.Reasoning
This is the well-known Celery/kombu lazy-import pattern: the reversed-string key 'kcah_acitats' yields 'STATICA_HACK', set to False, and the branch is never executed; it only helps static analyzers. Obfuscated-looking but benign and documented.
-
=likely benign Lazy submodule import of package-internal modules via __import__ from a static mapping.Reasoning
This is the standard lazy module attribute loader (__getattr__-style) in which __import__ resolves a module name from a fixed mapping object_origins built within the package. The argument is not attacker-controlled input, so it is a legitimate dynamic import.
-
passlikely benign Test helper probing module availability via __import__.Reasoning
In a test conftest, __import__(module) is used in a try/except to probe whether optional modules are importable and skip otherwise. It is test scaffolding with no external input, so benign.
-
= yieldlikely benign Test fixture temporarily patches builtins.__import__ to simulate import errors.Reasoning
A test fixture temporarily replaces builtins.__import__ with a custom importer and restores it in finally. This is a common mocking technique for simulating import failures in tests. It is intrusive but confined to the test session and restored.
-
=likely benign Restores the original builtins.__import__ after the test patch.Reasoning
This is the restore step in the finally block of the same fixture, reinstating realimport. It is the cleanup half of a benign test mock.
-
assert ==likely benign Test verifying zlib-compressed message body decodes to the expected JSON.Reasoning
The zlib.decompress call in a unit test decompresses a payload the test itself just compressed to verify round-trip content-encoding behaviour. It is not a runtime dropper; the content is local test data.
-
=likely benign Base64-encoded msgpack test vector for serialization round-trip.Reasoning
This is a base64-encoded msgpack fixture used in serialization tests, with readable text (e.g. 'The quick brown fox') inside. Low compression ratio is expected for short data. Test fixture, benign.
-
+\ \ =\likely benign Continuation of base64 msgpack test vector.Reasoning
Continuation line of the same base64 msgpack test fixture; benign test data.
-
\ =\likely benign Final lines of base64 msgpack test vector.Reasoning
Final lines of the same base64 msgpack test fixture; benign test data.
-
:likely benign Mock AWS session token strings in SQS test fixtures.Reasoning
Fake AWS SessionToken and credential-like strings in SQS test fixtures, using the AWS documentation 'EXAMPLE' style. They are mock values for tests, not real secrets or encoded payloads.
-
likely benign Mock AWS session token fragment in SQS test.
Reasoning
Fragment of the same mock AWS session token in an SQS test file. Random-looking base64 is expected for fake credential values; benign.
-
,likely benign Mock AWS session token continuation in SQS test.Reasoning
Continuation of the same mock AWS session token fixture in the SQS test file; benign.
-
, }likely benign Mock AWS session token final fragment in SQS test.Reasoning
Final fragment of the same mock AWS session token fixture; benign test data.
-
= # noqa = # noqalikely benign Azurite emulator default account key embedded in a unit test connection string.Reasoning
The base64 blob is the publicly documented default account key for the Azurite storage emulator (account devstoreaccount1, localhost:10001). It is a well-known test credential, not a production secret. The file is a unit test, the value is used only against localhost or a docker-compose service, and the raw-pass base64 signal is a high-false-positive pattern. Nothing here is obfuscated.
-
= # noqa = # noqalikely benign Same Azurite emulator default key used in a docker-compose test connection string.Reasoning
This is the same public Azurite default key, used in a docker-compose connection string pointing at the 'azurite' service host. It is a documented emulator credential for test fixtures. The base64 match is a raw-pass heuristic hit on a known constant, with no decoding, execution, or concealment involved.
-
: , : # noqa } assert == f # noqalikely benign Azurite emulator default account key in a test configuration dictionary.Reasoning
The value is again the public Azurite default account key, set as 'account_key' in a test configuration dict alongside account_name 'devstoreaccount1' and an assertion on the localhost emulator URL. It is a well-known test fixture credential, and the code has no dynamic execution or encoded payload behaviour.
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.
&&