Togoder security

npm package security report

@scure/base npm package: is it safe?

No malicious code found.

No issues Version 1.2.6 Files reviewed 3 Size 76.0 KB Scanned

Summary

Togoder Security scanned the npm package @scure/base@1.2.6 on Oct 4, 2026. An AI review of 3 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.

0
critical
0
high
0
medium
0
low

Findings

No findings. The reviewer saw nothing malicious or risky in this version.

Files reviewed

FileVerdictWhat the reviewer saw
index.ts safe No malicious patterns detected; the code is a legitimate base encoding library with no exfiltration, dynamic execution, or lifecycle hooks.
lib/esm/index.js safe No malicious patterns detected; this is a legitimate base encoding/decoding utility library with no network, filesystem, process, or dynamic code execution activity.
lib/index.js safe No malicious patterns detected; the code is a legitimate base encoding library with no data exfiltration, credential harvesting, obfuscation, or suspicious behaviors.

Affected version ranges

None of the 2 scanned versions of @scure/base are flagged high or critical. The latest scanned version, 1.2.6, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.

1.1.91.2.6
VersionsVerdictCountRangeTop findings
1.1.9 โ€“ 1.2.6 No issues 2 >=1.1.9 <=1.2.6

Full list, including published versions not scanned yet: version ranges API.

Scanned versions of @scure/base

VersionVerdictFilesScanned
1.2.6 No issues 3 Oct 4, 2026
1.1.9 No issues 3 Oct 4, 2026

Frequently asked questions

Is @scure/base safe to use?

Our AI source review of @scure/base@1.2.6 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.

Does @scure/base contain malware?

No malware was identified in @scure/base@1.2.6 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.

How was @scure/base checked?

Togoder Security downloaded the published npm package and had an AI model read its 3 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.

How do I scan @scure/base together with the rest of my dependencies?

Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in @scure/base@1.2.6, cost nothing.

Related security reports