npm / convert-source-map / 2.0.0
convert-source-map 2.0.0
- Source
- https://github.com/thlorenz/convert-source-map
- Artifact scanned
convert-source-map-2.0.0.tgz- Compared with
convert-source-map-1.9.0.tgz(0 signals introduced since)- Files
- 3 scanned, 1 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 4 info
- Scan time
- 4.0 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-23 16:45
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
var json = convert . .;dismissed A base64 inline source map embedded in a README code example for convert-source-map.Reasoning
The blob is a standard inline source map (version 3, file build/foo.min.js, sources src/foo.js) inside a markdown code sample for a source-map conversion library. It is documentation of a legitimate pattern, not hidden code, and nothing in the snippet decodes it into execution.
-
var modified = convert . . .;dismissed A second README example reuses the same base64 inline source map while rewriting the sources field.Reasoning
This is the same base64 source-map comment as the previous finding, used in a second documentation example that calls setProperty on the sources list. It is a usage illustration in markdown with no executable payload.
-
likely benign A utility function that base64-decodes a string to UTF-8 text using atob, escape and decodeURIComponent.
Reasoning
The helper is the conventional UTF-8-aware base64 decoder, decodeURIComponent(escape(atob(x))). The snippet shows no eval, Function constructor, network fetch, or other downstream execution of the decoded value, and the function name matches its purpose. The residual doubt is that the decoded output's use is not visible.
-
var json = this.; return ; }
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.
|
&&