@azure-rest/core-client
Core library for interfacing with Azure Rest Clients
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 | publisher-changed | AI (provenance): azure-sdk → microsoft1es is a documented Microsoft internal npm account transition for Azure SDK packages; not a compromise signal. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft1es is Microsoft's engineering systems npm account; addition is part of the same organizational transition, not a hostile takeover. | ai | |
| phantom-deps | phantom-dep:@azure/core-util | AI (phantom-deps): @azure/core-util is a peer/framework-scoped Azure SDK dependency; phantom-dep finding is a stable false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.6.0 | 6 / 12 | |
| 2.5.1 | 6 / 9 | |
| 2.5.0 | 6 / 9 | |
| 2.4.0 | 6 / 9 | |
| 2.3.5 | 6 / 9 | |
| 2.3.4 | 6 / 9 | |
| 2.3.3 | 6 / 9 | |
| 2.3.2 | 6 / 9 | |
| 2.3.1 | 6 / 11 | |
| 2.3.0 | 6 / 11 | |
| 2.2.0 | 6 / 12 | |
| 2.1.0 | 6 / 12 | |
| 2.0.0 | 6 / 12 | |
| 1.4.0 | 6 / 13 | |
| 1.3.1 | 6 / 13 | |
| 1.3.0 | 6 / 13 | |
| 1.2.0 | 6 / 25 | |
| 1.1.7 | 6 / 25 | |
| 1.1.6 | 6 / 27 | |
| 1.1.5 | 6 / 27 | |
| 1.1.4 | 6 / 26 | |
| 1.1.3 | 4 / 26 | |
| 1.1.2 | 4 / 26 | |
| 1.1.1 | 4 / 28 | |
| 1.1.0 | 4 / 28 | |
| 1.0.1 | 4 / 28 | |
| 1.0.0 | 4 / 28 |
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.