disclude.ioPyPI / databricks-sdk / 0.157.0
databricks-sdk 0.157.0
- Source
- https://github.com/databricks/databricks-sdk-py
- Artifact scanned
databricks_sdk-0.157.0-py3-none-any.whl- Compared with
databricks_sdk-0.156.0-py3-none-any.whl(0 signals introduced since)- Files
- 98 scanned, 6 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 4 info
- Scan time
- 6.6 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 3 of 3 warn and critical signals; 3 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-24 17:42
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
= None # The next few try-except blocks are for initialising globals in a best effortlikely benign Pre-declares Databricks runtime global names as None by writing into globals() from a list.Reasoning
The loop assigns None to names in dbruntime_objects via globals(), and the following comment says the try-except blocks initialise globals on a best-effort basis. This is a common way to pre-declare optional runtime names in a Databricks SDK module. It is reflective but has no decoding, execution, or network use, so it reads as a legitimate pattern.
-
"""Serializes the ModelProviderServiceConfigCustomProviderApiKeyHeaderAuth into a dictionary suitable for use as a JSON request body.""" = -
| :--- | :--- ``=`` | in . ``=+/==`` | or .dismissed Example etag value in an API docstring table, flagged as a base64-like blob.Reasoning
The raw pass flagged a base64-like string inside a docstring. It is an illustrative etag value in a markdown table documenting SCIM API usage, not executable code or a payload. Raw findings have a high false-positive rate, and this one matches a documentation example.
-
| :--- | :--- ``=`` | in . ``=+/==`` | or .dismissed Repeated example etag in another API docstring, flagged as a base64-like blob.Reasoning
This is the same docstring example etag appearing in another method's documentation in the same generated SDK file. It is documentation text with no decoding or execution path, so it is a false positive from the raw pass.
Reproduce This Scan
Run disclude locally to verify. These commands scan the published file; the "new in this release" marks come from comparing it with the previous release's file, which they don't repeat. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
|