@azure/msal-node
Microsoft Authentication Library for Node
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Microsoft/AzureAD packages are published without Sigstore provenance; this is consistent across their npm releases and not a security risk for this well-known publisher. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is a standard utility in an authentication library (e.g., for JWT parsing). No obfuscation or malicious payload concern. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 169.254.169.254 is the standard Azure IMDS link-local endpoint, used by all Azure SDKs. Expected and documented behavior for this package. | ai |
Versions (showing 18 of 118)
| Version | Deps | Published |
|---|---|---|
| 1.9.1 | 3 / 9 | |
| 1.9.0 | 5 / 9 | |
| 1.8.0 | 5 / 9 | |
| 1.7.0 | 5 / 9 | |
| 1.6.0 | 5 / 9 | |
| 1.5.0 | 4 / 9 | |
| 1.4.0 | 4 / 9 | |
| 1.3.3 | 4 / 9 | |
| 1.3.2 | 4 / 9 | |
| 1.3.1 | 4 / 9 | |
| 1.3.0 | 4 / 9 | |
| 1.2.0 | 4 / 9 | |
| 1.1.0 | 4 / 9 | |
| 1.0.3 | 4 / 9 | |
| 1.0.2 | 4 / 9 | |
| 1.0.1 | 4 / 9 | |
| 1.0.0 | 4 / 9 | |
| 5.0.0-beta.0 | 3 / 17 |
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0-beta.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.