uri-js 4.4.1
- Source
- https://github.com/garycourt/uri-js
- Commit scanned
9a328873a212- Compared with
7cb6f9ccfa44(0 signals introduced since)- Files
- 45 scanned, 21 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 5 info
- Scan time
- 2.2 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 1 of 1 warn and critical signal; 1 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-14 20:09
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
-
UNRESERVED$$ = , SCHEME$ = , USERINFO$ = , DEC_OCTET$ = -
REG_NAME$ = , HOST$ = , PORT$ = , AUTHORITY$ = , PCHAR$ = su -
PATH_EMPTY$ = "(?!" + PCHAR$ + ")", PATH$ = , QUERY$ = , FRAGMENT$ = , HIER_PART$ =likely benign Minified/generated build output assembling RFC 3986 URI regular expressions from string fragments.Reasoning
A long line in a bundled/distributed build of a URI regex library (uri.js-style). The snippet shows concatenation of regex fragments building RFC 3986 URI patterns, which is a standard, legitimate technique for constructing long regexes. Long-line flag in a dist file from a raw pass is a known high-false-positive signal; no dynamic execution, encoding blobs, or malicious behavior is present.
-
// Initialize the configuration options init:
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.
&&