keyv 6.1.0
- Source
- https://github.com/jaredwray/keyv
- Artifact scanned
keyv-6.1.0.tgz- Compared with
keyv-5.6.0.tgz(6 signals introduced since)- Files
- 6 scanned, 1 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 6 info
- Scan time
- 2.6 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 2 of 2 warn and critical signals; 2 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-23 22:06
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
binary += String.; return ; } -
return buffer.; const binary = ; const bytes = ; bytes = binary.;likely benign Bundled base64 decoding helper that falls back from Buffer to atob to produce a Uint8Array.Reasoning
The snippet is a standard base64-to-bytes helper: it uses Buffer when available and falls back to atob, then copies chars into a Uint8Array. The decoded bytes are not passed to eval, Function, or a process spawn. This is a common polyfill pattern in bundled libraries and the flagged step is only data conversion.
-
-
-
binary += String.; return ; } -
return buffer.; const binary = ; const bytes = ; bytes = binary.;likely benign ESM bundle copy of a base64-to-bytes helper using Buffer with an atob fallback.Reasoning
This is the ESM build of the same base64 decoding helper, with identical logic: Buffer if present, otherwise atob into a Uint8Array. Nothing in the snippet executes or fetches the decoded data, and the pattern is typical of compiled dependencies.
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.
|
&&