← Home

emailjs-base64

npm Repository Homepage

Safe Base64 de/encoding to and from strings and typed arrays

9
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

felixhammerl

Keywords

base64

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/base64-decode.js AI (source-diff): dist/base64-decode.js is Babel-transpiled ES5 output of a standard base64 decoder — fully readable, no malicious content. Long lines are minification artifacts, not obfuscation. ai
source-diff obfuscated-file:dist/base64-encode.js AI (source-diff): dist/base64-encode.js is Babel-transpiled ES5 output of a standard base64 encoder — fully readable, no malicious content. Long lines are minification artifacts, not obfuscation. ai
source-diff source-size-tripled AI (source-diff): Size increase is entirely explained by addition of compiled dist/ artifacts from the new build step. No injected payloads. ai

Versions (showing 9 of 9)

Version Deps Published
1.1.4 0 / 8
1.1.3 0 / 8
1.1.2 0 / 8
1.1.1 0 / 8
1.1.0 0 / 8
1.0.3 0 / 8
1.0.2 0 / 8
1.0.1 0 / 8
1.0.0 0 / 7

v1.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

3 findings
HIGH New obfuscated file: dist/base64-decode.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/base64-encode.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

3 findings
HIGH New obfuscated file: dist/base64-decode.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/base64-encode.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.