filelock 4.2.4
- Source
- https://github.com/tox-dev/py-filelock
- Artifact scanned
filelock-4.2.4-py3-none-any.whl- Compared with
filelock-4.2.3-py3-none-any.whl(0 signals introduced since)- Files
- 23 scanned, 5 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 4 info
- Scan time
- 4.4 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 4 of 4 warn and critical signals; 4 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-23 01:18
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
= = returnlikely benign Lazy attribute resolution in filelock's package __init__ that caches imported names in globals().Reasoning
This is the standard lazy-import pattern for a package: a module-level __getattr__ resolves names like AsyncFileLock from submodules and caches them in globals(). The name lookup is bounded to the package's own attribute set and has no decoding, execution or network behavior.
-
return =likely benign Stores the current call frame on lock state during release for bookkeeping.Reasoning
inspect.currentframe() is stored on the lock state to record which code is releasing the lock, a common diagnostic for re-entrancy and debugging. It is used with a logger debug call and does nothing malicious.
-
= 0 = # Created once, so a directory that disappears while the acquisition waits fails it, not builds a secondlikely benign Records the acquiring call frame on the lock context during acquisition.Reasoning
Storing the current frame on the context object while acquiring a lock is the same legitimate diagnostic/bookkeeping pattern used in the release path of filelock's own API. No exfiltration or dynamic execution is present.
-
return False = =likely benign Walks the call stack via f_back to locate a specific caller frame.Reasoning
Walking f_back from the current frame to locate a caller frame is a benign utility for finding the calling context, here used to locate a frame in the stack. It is ordinary introspection with no malicious effect.
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.
|