← Home

base64-encode

npm Repository Homepage

Encode base-64 strings with JavaScript

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

forbeslindesay

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:utf8-encode AI (dependencies): utf8-encode is pinned to ForbesLindesay/utf8-encode#1.0.0 — the same author's own GitHub repo at a fixed tag. This is a deliberate, trusted self-dependency, not a third-party risk. ai
source-diff source-size-tripled AI (source-diff): Absolute size remains under 1KB; the growth reflects legitimate addition of server.js alongside index.js. No malicious payload indicators present. ai

Versions (showing 3 of 3)

Version Deps Published
2.0.1 1 / 3
2.0.0 1 / 3
1.0.1 0 / 3

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.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.1

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.