@azure/core-client
Core library for interfacing with AutoRest generated code
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Azure SDK packages legitimately have many README links (docs, changelogs, related packages) and publish at mature semver versions reflecting their history in the monorepo. Both signals are false positives for this package. | ai | |
| phantom-deps | phantom-dep:@azure/core-util | AI (phantom-deps): @azure/core-util is a framework-scoped Azure SDK package; phantom-dep detection is a false positive for convention-loaded Azure SDK dependencies. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.11.0 | 7 / 15 | |
| 1.10.2 | 7 / 15 | |
| 1.10.1 | 7 / 10 | |
| 1.10.0 | 7 / 10 | |
| 1.9.4 | 7 / 10 | |
| 1.9.3 | 7 / 10 |
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.