@azure/msal-browser 4.0.1

Microsoft Authentication Library for js

@azure/msal-browser@4.0.1 was published on 2025-01-15. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=0.8.0.

Deprecated: A bug was identified in this release that coule be production impacting. Use 4.0.2 or later.

All @azure/msal-browser versions · Permanent reference to 4.0.1 · Latest release

Package specifications

Version4.0.1
License declarationMIT
Published2025-01-15T05:38:14.760Z
Node.js requirement>=0.8.0
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size6010.86 KiB
Published file count645
Package typemodule
ES module entry./dist/index.mjs
Default entry./lib/msal-browser.cjs
Side effects declarationfalse
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars4145
Repository forks2719

Install @azure/msal-browser 4.0.1

npm install @azure/msal-browser@4.0.1
pnpm add @azure/msal-browser@4.0.1
yarn add @azure/msal-browser@4.0.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Code-Review10/10 — all changesets reviewed
Security-Policy9/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Branch-Protection9/10 — branch protection is not maximal on development and all release branches
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness