dulwich 1.2.19
- Source
- https://github.com/dulwich/dulwich
- Tag scanned
dulwich-1.2.19- Compared with
dulwich-1.2.18(0 signals introduced since)- Files
- 280 scanned, 105 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 51 info
- Scan time
- 32.8 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 43 of 43 warn and critical signals; 43 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-22 12:30
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
return : =likely benign Decompresses cached bytes with zlib and parses the result as JSON.Reasoning
zlib.decompress of a bytes object followed by json.loads looks like ordinary cache or object-store deserialization. Decompression alone is not a payload-delivery pattern, and nothing in the snippet is hidden or executed.
-
----- ----- //1jGXXkQmQ2xtmKVlR+ ++ +likely benign A PEM-encoded RSA private key block in a paramiko vendor test file.Reasoning
The raw base64 blob is an RSA private key in PEM form inside a test module. This is a committed test fixture rather than obfuscation, though a real key in a repo is worth noting.
-
----- ----- /0z/+ ++/ //2l3zmLKJlt3jnOHLczP24CBlikely benign A second PEM-encoded RSA private key block in the same paramiko test file.Reasoning
Same pattern as the other key block: a PEM RSA key in a test file, consistent with test fixture material rather than hidden payload.
-
}likely benign exec of a compiled literal snippet that prints the current version.Reasoning
The exec/compile argument is a literal string defining a small __main__ block for a release script. The unusual exec is odd, but the code is static and does nothing hidden or malicious.
-
}likely benign Second exec of the same literal version-printing snippet.Reasoning
Repeats the same literal exec/compile snippet. It is static code in a release helper, not a runtime-determined payload.
-
= =likely benign Launches the user's configured pager command through a shell.Reasoning
Popen with shell=True runs the pager command from git configuration or environment. Running a configured pager through the shell is a conventional git-tool pattern, and the snippet shows no obfuscation.
-
= =likely benign Imports a named dependency module to read its version for diagnostics.Reasoning
__import__ on a dependency name inside a version-reporting routine. The names come from a known dependency list, so this is a common diagnostic pattern, not obfuscated execution.
-
=likely benign Runs a configured filter command through the shell with extra environment variables.Reasoning
subprocess.run with shell=True executes a filter command with extra env, which is the standard way git filter/driver commands run. The command comes from repository configuration, which is expected for this tool.
-
# Decompress and parse the object = # Parse headerlikely benign Decompresses and parses a git object fetched over dumb HTTP.Reasoning
zlib.decompress of a fetched git object followed by header parsing is the normal way to read git loose objects. Nothing suggests a hidden payload.
-
=likely benign Starts a configured filter process through the shell.Reasoning
Popen with shell=True runs a configured process filter command, as git's clean/smudge filter mechanism does. The command is supplied by config, and the snippet shows no obfuscation.
-
=likely benign Runs a configured merge driver command through the shell.Reasoning
subprocess.run with shell=True executes a configured merge driver command, a documented git feature. The snippet is consistent with normal tool behavior.
-
""" dcomp = zlib.decompressobj() # +1 so overrun surfaces as unconsumed_tail rather than being truncated. dcomped = dcomp.decompress(string, max_size + 1)likely benign Bounded zlib decompression of git object data with overrun detection.Reasoning
zlib.decompressobj with a max_size limit is a careful bounded decompression of git object data, a legitimate parsing pattern with explicit overrun handling.
-
= =likely benign Streaming zlib decompression of pack file data.Reasoning
zlib.decompressobj streaming decompression of pack data is standard git pack-file reading, with no hidden payload or execution.
-
=likely benign Decompresses base85-encoded git binary patch data inside a patch parser.Reasoning
zlib.decompress applied to git binary patch data via git_base85_decode is the standard way git binary diffs are stored. The error handling is ordinary. Nothing suggests a hidden payload.
-
# Command failed, pause rebaselikely benign Runs the user's rebase exec command through the shell.Reasoning
Interactive rebase 'exec' todo entries are user-authored commands that git itself runs through a shell, so shell=True mirrors designed behavior. It is an injection-prone pattern, but the command source is the local user's rebase file, not a remote or hidden source.
-
# Run the default key command to get the key =likely benign Runs the configured default-key command through the shell to fetch a signing key.Reasoning
The shell command comes from the user's configured default GPG key command, as with git's gpg.program setting. It is a designed feature rather than a hidden or obfuscated invocation.
-
info
warn→ info by reviewdynamic-executionfuzzing/oss-fuzz-scripts/container-environment-bootstrap.sh:79:1# Install the Rust toolchain so the Rust extensions can be built in build.sh. | # The OSS-Fuzz base image has outdated dependencies by default so we upgrade them below.likely benign Installs the Rust toolchain by piping the rustup bootstrap script to sh.Reasoning
Piping the official rustup installer from sh.rustup.rs into sh is the documented install method for Rust. It is a supply-chain trust risk in principle, but it is visible, expected, and targets the legitimate Rust vendor domain.
-
-
-
= -
= -
= # Get both quoted and unquoted results from dulwich -
= # Get both quoted and unquoted results from dulwich -
# Verify unquoted paths contain the expected files = -
# Verify unquoted paths contain the expected files = -
= passlikely benign Decodes a basic-auth credential in a test client.Reasoning
base64.decodestring is a deprecated but ordinary call used to parse HTTP basic auth in a compatibility test. There is no payload execution, and the binascii.Error handler is routine.
-
+ +/9BHCXAr8xQAtp/+/ //+/likely benign Base64 OpenPGP-style key or signature fixture in a test module.Reasoning
The blob starts with lQ, the typical header of an OpenPGP packet, and sits in a test package that exercises git signing or porcelain features. It is test fixture data, not an obfuscated payload.
-
+ /4eLYIR7FmpdbFPcDThFNHbXJzBi00L1mp0XQE2l50h/2bDAAgREdZ+/likely benign Base64 OpenPGP-style key fixture in a test module.Reasoning
Same structure as the other fixture in this file, with the lQ OpenPGP header. It is test data for signing or key handling.
-
=likely benign Hex-escaped zlib-compressed git object fixture for object-parsing tests.Reasoning
The byte sequence begins with 0x48 0x89, which is zlib-compressed data, and the variable name small_buffer_zlib_object says it is a test vector for git object parsing. Hex escapes are the normal way to write binary fixtures.
-
// ++ /+++likely benign Base64 PGP signature fixture in an object test.Reasoning
The iQIc header is an OpenPGP signature packet, and the file is a test for signature handling. The 0.79 compression ratio fits base64 of binary test data.
-
// ++ /+++likely benign Repeated base64 PGP signature fixture in an object test.Reasoning
This is the same PGP signature fixture as at line 450, indented into a different test. It is test data.
-
/ = =likely benign ASCII-armored PGP signature fixture in an object test.Reasoning
The iD8DBQ header and =ivrA armor checksum mark a standard ASCII-armored PGP signature. It is a test fixture for signature parsing.
-
/ = =likely benign Repeated ASCII-armored PGP signature fixture in an object test.Reasoning
Identical armored PGP signature fixture to the one at line 529, used in another test. It is test data.
-
/ = =likely benign Repeated ASCII-armored PGP signature fixture in an object test.Reasoning
Identical armored PGP signature fixture again, in a further test. It is test data.
-
// ++ /+++likely benign Base64-encoded PGP key/signature material used as test fixture data.Reasoning
The blob is a PGP public key block (base64 with 'iQIcBAAB...' header typical of PGP signatures/keys) inside a test fixture file for a git library; this is test data, not obfuscation.
-
// ++ /+++likely benign Duplicate PGP base64 fixture in a test module.Reasoning
Same PGP base64 fixture repeated in the objects test file; legitimate test data for signature handling.
-
likely benign PGP base64 fixture for signed-commit tests.
Reasoning
Another PGP key/signature block in a test of a git object library; expected for testing commit signature parsing.
-
likely benign Repeated PGP base64 fixture in test file.
Reasoning
Duplicate of the PGP fixture block; legitimate test data.
-
// ++ /+++likely benign PGP signature base64 fixture in test code.Reasoning
PGP base64 signature fixture with standard armor structure; test data for a git library.
-
= blikely benign SSH signature fixture in a test file.Reasoning
Armored SSH signature block (BEGIN SSH SIGNATURE) inside a test for signed tag/commit handling; standard format test data.
-
/ = =likely benign Armored PGP fixture fragment in tests.Reasoning
Short PGP base64 block with checksum line (=ivrA) is a standard armored fixture; benign test data.
-
/ = =likely benign Repeated armored PGP fixture in tests.Reasoning
Duplicate of the armored PGP fixture; benign test data.
-
----- ----- ----- -----likely benign Repeated SSH signature fixture in tests.Reasoning
Duplicate SSH signature armor fixture; benign test data.
-
=likely benign PNG header bytes used to construct a binary test blob.Reasoning
A PNG file header (\x89PNG\r\n\x1a\n, IHDR) written as bytes literal to build a test blob for diff/patch handling of binary files; legitimate test data.
-
=likely benign PNG bytes literal for binary diff test.Reasoning
Same PNG byte fixture used for a second test blob in patch tests; benign.
-
=likely benign PNG bytes literal in patch test.Reasoning
Repeated PNG binary fixture in patch tests; legitimate binary-file test data.
-
=likely benign PNG bytes literal in patch test.Reasoning
Repeated PNG binary fixture for blob comparison in tests; benign.
-
=likely benign PNG bytes literal in patch test.Reasoning
Repeated PNG binary fixture in patch tests; benign test data.
-
=likely benign Test fixture embedding PNG header bytes as a blob for a patch test.Reasoning
The bytes literal begins with the PNG file signature (\x89PNG\r\n\x1a\n) followed by IHDR chunk bytes, which is a test fixture for creating a PNG blob in a dulwich-style Git patch test. Binary test data is expected in this context and there is no execution or hidden behavior.
-
=likely benign Unit test decompressing a small known fixture to verify git base85 decoding.Reasoning
zlib.decompress is applied to a literal expected value in a unit test, asserting that the decoded git base85 output equals b'a\0c\0d'. The data is a small known fixture, not a runtime-embedded payload being executed; this is ordinary test code in a Git library.
-
= = =likely benign Test fixture containing an SSH ed25519 public key in an allowed_signers file.Reasoning
The base64-like blob is an ssh-ed25519 public key string inside an allowed_signers test fixture, with the key type and standard base64 encoding of the key blob. It is a legitimate test input for parsing allowed signers files.
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.
&&