</>PackageGraphPackageGraph

base64-js

npmv1.5.1TypeScript

Base64 encoding/decoding in pure JS

Not recommended for new projects

No — base64-js should not be adopted for new projects. Last published 2128 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 2128 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 9.4 KB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 2 maintainers, and a contained dependency surface.

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding base64-js to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

9.4 KB
Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
Types included
Install scripts
None

base64-js vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
base64-jsthis page03MIT5 years ago
vlq9.5M2MIT1 day ago
@exodus/bytes05MIT1 day ago
js-base6405BSD-3-Clause1 day ago

Dependencies

Declared by base64-js v1.5.1. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (5)

babel-minify ^0.5.1benchmark ^2.1.4browserify ^16.3.0standard *tape 4.x

Used by

Popular packages that depend on base64-js.

Relationship graph

Dependencies (left) and dependents (right) of base64-js.

@exodus/bytesreact-native@expo/plistbase64-js
base64-js dependencies dependents

Frequently installed together

Release history

No releases in the last two years, typically about 61 days apart.

Recent versions of base64-js
VersionPublishedSizeLicense
1.5.1latest5 years ago9.4 KBMIT
1.5.05 years ago9.5 KBMIT
1.3.17 years ago9.0 KBMIT
1.3.08 years ago13 KBMIT
1.2.38 years ago12 KBMIT
1.2.28 years ago12 KBMIT
1.2.19 years agoMIT
1.2.010 years agoMIT
1.1.210 years agoMIT
1.1.110 years agoMIT
1.1.010 years agoMIT
1.0.410 years agoMIT
1.0.310 years agoMIT
1.0.210 years agoMIT
1.0.110 years agoMIT

Overview

base64-js is an npm package that base64 encoding/decoding in pure JS. It has 3 known dependents in the graph. The latest version is 1.5.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need base64 encoding/decoding in pure JS and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.

Pros

  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Funding

Frequently asked questions

Should I use base64-js?

No — base64-js should not be adopted for new projects. Last published 2128 days ago.

How do I install base64-js?

Run `npm install base64-js` to add base64-js to your npm project.

What license is base64-js released under?

base64-js is distributed under the MIT license.

How popular is base64-js?

npm does not publish download counts. Within PackageGraph's crawl, 3 known packages depend on base64-js.

Is base64-js still maintained?

The most recent release of base64-js (v1.5.1) was published 5 years ago.

Does base64-js run install scripts?

No. base64-js does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.