pako 3.0.3
- Source
- https://github.com/nodeca/pako
- Artifact scanned
pako-3.0.3.tgz- Compared with
pako-3.0.2.tgz(8 signals introduced since)- Files
- 8 scanned, 9 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 10 info
- Scan time
- 4.3 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-27 23:27
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
var e=4,t=0,n=1;var i=1,a=29,o=256,s=286,c=30,l=19,u=573,d=15,f=16,p=256,m=16,h=17,g=18,_=,v=,y=likely benign Minified browser build of the pako zlib/deflate/inflate JavaScript library.Reasoning
The raw pass flags a 45k-character line, but the snippet is ordinary minified zlib code (typed-array tables, deflate constants, reused short variable names). Minifiers emit long single lines by design, and this file is a distributed build of the pako library, so the length alone is not evidence of obfuscation or malice.
-
var e=4,t=0,n=1;var i=1,a=29,o=256,s=286,c=30,l=19,ee=573,u=15,d=16,f=256,p=16,m=17,h=18,g=,_=,te=likely benign Minified pako deflate-only browser bundle with standard compression lookup tables.Reasoning
The long line is a minified pako deflate bundle: single-letter identifiers and standard Huffman/deflate constant tables. This is the normal output of a minifier for a compression library, and the raw long-line signal has a high false-positive rate for minified code.
-
var e=4,t=0,n=1;var i=29,a=256,o=30,s=19,c=573,l=15,u=16,d=256,f=16,p=17,m=18,h=,g=;likely benign Minified pako inflate-only browser bundle with standard decompression tables.Reasoning
The snippet shows minified pako inflate code with standard length and distance tables, and no execution, network, or decoding-of-payload behaviour. A single long line is typical of a minified distributed bundle, so this is a benign legitimate pattern.
-
-
-
-
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.
|
&&