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
- 317 scanned, 17 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 17 info
- Scan time
- 16.6 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 17 of 17 warn and critical signals; 17 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-22 09:00
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
likely benign A PayPal donation form's encrypted button parameter embedded as a hidden input.
Reasoning
The long line is a PayPal encrypted-button PKCS7 blob embedded in a hidden form field, a standard donation-button pattern. It is a long line of ordinary payment markup, not a payload.
-
= True = False # pragma: no cover # This is never executed, but tricks static analyzers (PyDev, PyCharm,likely benign A never-executed block that uses a reversed-string globals assignment to placate static analyzers in the kombu package init.Reasoning
This is the known kombu idiom that tricks static analyzers into seeing a name (STATICA_HACK) that is never executed at runtime. The reversed-and-uppercased name is an odd obfuscation, but it is a deliberate, documented, benign hack in a well-known library, and it is not a dropper.
-
=likely benign Lazy submodule import inside kombu's attribute-access fallback, using a module name from an internal mapping.Reasoning
This is kombu's lazy-loading __getattr__ pattern: the module name comes from a fixed internal mapping (object_origins) populated by the package itself, not from untrusted input. Dynamic import here is a legitimate lazy-loading mechanism.
-
passlikely benign Test helper that attempts to import a module and silently ignores import failures.Reasoning
The try/except around __import__(module) with ImportError handling is a test helper that probes whether a module is available. The module name comes from test configuration, so this is ordinary test scaffolding.
-
= yieldlikely benign Test fixture that swaps in a custom import function to simulate import behavior, then restores it.Reasoning
Temporarily replacing builtins.__import__ within a pytest fixture (paired with a restore in finally) is a standard mocking technique for simulating import failures or version mismatches in tests. It is confined to the test session.
-
=likely benign Restores the original builtins.__import__ after a test fixture finishes.Reasoning
This is the restore half of the same test fixture, reassigning the saved real __import__ in a finally block. It is a clean-up step, not an attack.
-
assert ==likely benign Unit test that decompresses a locally compressed message to verify JSON round-tripping.Reasoning
zlib.decompress here round-trips a test message that the test itself compressed, then checks it against the expected value. It is an ordinary serialization test, not a runtime-embedded payload.
-
=likely benign Base64-encoded msgpack test fixture in a serialization test.Reasoning
The base64 blob is msgpack-encoded fixture data that decodes to plain readable test values (strings, floats, lists). It is a serialization test vector, not a hidden payload.
-
+\ \ =\likely benign Continuation of the base64 msgpack serialization test vector.Reasoning
This is a continuation of the same msgpack test fixture, which contains readable test strings in the encoded data.
-
\ =\likely benign Final lines of the base64 msgpack serialization test vector.Reasoning
This is the final continuation of the same msgpack test fixture, with no sign of executable or obfuscated content.
-
:likely benign Mock AWS session-token strings used as test fixtures for the SQS transport.Reasoning
The strings are a fake AWS session token and related credential-like values built from the 'EXAMPLE' placeholder pattern. They are test fixture data in a mock SQS setup, not live credentials or code.
-
likely benign Fragment of placeholder AWS-style token data in an SQS unit test.
Reasoning
These are fragments of the same placeholder AWS-style token strings used in SQS transport tests. They are high-entropy test data, not an encoded dropper.
-
,likely benign Continuation of placeholder AWS-style token data in an SQS unit test.Reasoning
This continues the same placeholder token string split across lines in an SQS unit test. It is test data with no execution path.
-
, }likely benign Multi-line base64-like string literal in an SQS transport unit test.Reasoning
Raw-pass base64 heuristic on a multi-line string literal in a unit test for the SQS transport. The blob is a test fixture with no decoding, execution, or dropper pipeline in the snippet, and raw findings have a high false-positive rate. Nothing indicates obfuscation.
-
= # noqa = # noqalikely benign Azurite local-emulator storage account key embedded in a connection-string test constant.Reasoning
The key is the publicly documented Azurite emulator account key (devstoreaccount1) used in the test suite to connect to a local emulator at localhost:10001. It is a well-known non-secret, and the file is a unit test with no decoding or execution behaviour.
-
= # noqa = # noqalikely benign Azurite emulator key used in a docker-compose connection string for tests.Reasoning
Same well-known Azurite devstoreaccount1 emulator key as the neighbouring constant, used for a docker-compose hostname variant in a test. It is a public default, not a live credential, and there is no obfuscation.
-
: , : # noqa } assert == f # noqalikely benign Public Azurite emulator account key in a unit-test channel configuration.Reasoning
The account_key is the public Azurite emulator key for devstoreaccount1, assigned in a test config dict and asserted against a localhost URL. This is a documented default, with no real secret and no obfuscated execution.
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.
&&