@azure/msal-common
Microsoft Authentication Library for js
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:rollup-msal | AI (npm-metadata): Monorepo file: reference in devDependencies only; not shipped to consumers. | ai | |
| npm-metadata | url-dep:msal-test-utils | AI (npm-metadata): Monorepo file: reference in devDependencies only; not shipped to consumers. | ai | |
| npm-metadata | url-dep:eslint-config-msal | AI (npm-metadata): Monorepo file: reference in devDependencies only; not shipped to consumers. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 169.254.169.254 is the Azure IMDS link-local endpoint, a documented and expected Azure SDK pattern. Not malicious. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @azure/msal-common is a well-established Microsoft library; inflated semver reflects real version history, not spam inflation. | ai |
Versions (showing 100 of 143)
| Version | Deps | Published |
|---|---|---|
| 16.6.2 | 0 / 28 | |
| 16.6.1 | 0 / 28 | |
| 16.6.0 | 0 / 28 | |
| 16.5.2 | 0 / 28 | |
| 16.5.1 | 0 / 28 | |
| 16.5.0 | 0 / 28 | |
| 16.4.1 | 0 / 28 | |
| 16.4.0 | 0 / 28 | |
| 16.3.0 | 0 / 28 | |
| 16.2.1 | 0 / 28 | |
| 16.2.0 | 0 / 28 | |
| 16.1.0 | 0 / 28 | |
| 16.0.4 | 0 / 28 | |
| 16.0.3 | 0 / 28 | |
| 16.0.2 | 0 / 28 | |
| 16.0.1 | 0 / 28 | |
| 15.17.0 | 0 / 27 | |
| 15.16.1 | 0 / 27 | |
| 15.16.0 | 0 / 27 | |
| 15.15.0 | 0 / 27 | |
| 15.14.2 | 0 / 27 | |
| 15.14.1 | 0 / 27 | |
| 15.14.0 | 0 / 27 | |
| 15.13.3 | 0 / 27 | |
| 15.13.2 | 0 / 27 | |
| 15.13.1 | 0 / 27 | |
| 15.13.0 | 0 / 27 | |
| 15.12.0 | 0 / 27 | |
| 15.11.0 | 0 / 27 | |
| 15.10.0 | 0 / 27 | |
| 15.9.0 | 0 / 27 | |
| 15.8.1 | 0 / 27 | |
| 15.8.0 | 0 / 27 | |
| 15.7.1 | 0 / 27 | |
| 15.7.0 | 0 / 27 | |
| 15.6.0 | 0 / 27 | |
| 15.5.2 | 0 / 26 | |
| 15.5.1 | 0 / 26 | |
| 15.5.0 | 0 / 26 | |
| 15.4.0 | 0 / 26 | |
| 15.3.0 | 0 / 26 | |
| 15.2.1 | 0 / 26 | |
| 15.2.0 | 0 / 26 | |
| 15.1.1 | 0 / 26 | |
| 15.1.0 | 0 / 26 | |
| 15.0.2 | 0 / 26 | |
| 15.0.1 | 0 / 26 | |
| 14.16.1 | 0 / 26 | |
| 14.16.0 | 0 / 26 | |
| 14.15.0 | 0 / 28 | |
| 14.14.2 | 0 / 26 | |
| 14.14.1 | 0 / 26 | |
| 14.14.0 | 0 / 26 | |
| 14.13.1 | 0 / 26 | |
| 14.13.0 | 0 / 26 | |
| 14.12.0 | 0 / 26 | |
| 14.11.0 | 0 / 26 | |
| 14.10.0 | 0 / 25 | |
| 14.9.0 | 0 / 25 | |
| 14.8.1 | 0 / 25 | |
| 14.8.0 | 0 / 25 | |
| 14.7.1 | 0 / 25 | |
| 14.7.0 | 0 / 25 | |
| 14.6.1 | 0 / 25 | |
| 14.6.0 | 0 / 25 | |
| 14.5.0 | 0 / 25 | |
| 14.4.0 | 0 / 24 | |
| 14.3.0 | 0 / 24 | |
| 14.2.0 | 0 / 24 | |
| 14.1.0 | 0 / 24 | |
| 14.0.3 | 0 / 24 | |
| 14.0.2 | 0 / 23 | |
| 14.0.1 | 0 / 23 | |
| 14.0.0 | 0 / 23 | |
| 13.3.3 | 0 / 23 | |
| 13.3.1 | 0 / 23 | |
| 13.3.0 | 0 / 23 | |
| 13.2.1 | 0 / 23 | |
| 13.2.0 | 0 / 22 | |
| 13.1.0 | 0 / 22 | |
| 13.0.0 | 0 / 22 | |
| 12.1.0 | 0 / 22 | |
| 12.0.0 | 0 / 22 | |
| 11.0.0 | 0 / 22 | |
| 10.0.0 | 0 / 22 | |
| 9.1.1 | 0 / 22 | |
| 9.1.0 | 0 / 22 | |
| 9.0.3 | 0 / 22 | |
| 9.0.2 | 0 / 22 | |
| 9.0.1 | 0 / 22 | |
| 9.0.0 | 0 / 22 | |
| 8.0.0 | 0 / 22 | |
| 7.6.0 | 0 / 22 | |
| 7.5.0 | 0 / 22 | |
| 7.4.1 | 0 / 22 | |
| 7.4.0 | 0 / 22 | |
| 7.3.0 | 0 / 22 | |
| 7.2.0 | 0 / 23 | |
| 7.1.0 | 0 / 23 | |
| 7.0.0 | 0 / 20 |
v16.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.