@azure/core-auth
Provides low-level interfaces and helper methods for authentication in Azure SDK
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft1es is Microsoft's publishing bot account with 3643 approved packages; legitimate org-level transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @azure/core-util is a first-party sibling package in the same Azure SDK monorepo. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Build system migrated to tshy with multi-dialect outputs (ESM/CJS/browser/react-native); new files are expected dist artifacts. | ai | |
| provenance | publisher-changed | AI (provenance): azure-sdk → microsoft1es is a known Microsoft CI/CD account migration within the Azure SDK org; both accounts are Microsoft-controlled. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 481 versions; gap is between vetted versions, not actual publish dormancy. | ai | |
| provenance | no-provenance | AI (provenance): microsoft1es is a well-established publisher; lack of Sigstore provenance is common and not a risk signal for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; its use as an implicit dependency is a well-known pattern in TypeScript-compiled Azure SDK packages. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.10.1 | 3 / 9 | |
| 1.10.0 | 3 / 9 | |
| 1.7.2 | 3 / 13 | |
| 1.3.2 | 2 / 25 | |
| 1.3.1 | 2 / 25 | |
| 1.3.0 | 2 / 25 | |
| 1.2.0 | 2 / 25 | |
| 1.1.4 | 2 / 25 | |
| 1.1.3 | 4 / 30 | |
| 1.1.2 | 4 / 30 | |
| 1.1.1 | 4 / 30 | |
| 1.1.0 | 4 / 29 | |
| 1.0.2 | 4 / 30 | |
| 1.0.0 | 3 / 30 |
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
2 findingsThis version was published by a different npm account than previous versions on 2024-04-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.