@azure/core-util
Core library for shared utility methods
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): Publisher changed from azure-sdk to microsoft1es, both long-standing Microsoft organizational npm accounts. Legitimate transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft1es is a well-established Microsoft publishing account (3148 approved packages). Legitimate org-level maintainer change. | ai | |
| dependencies | unvetted-dep:@azure/abort-controller | AI (dependencies): @azure/abort-controller is a legitimate Microsoft Azure SDK package; a stable dependency of this package across many versions. | ai | |
| dependencies | unvetted-dep:@typespec/ts-http-runtime | AI (dependencies): @typespec/ts-http-runtime is a legitimate Microsoft TypeSpec ecosystem package; expected dependency for Azure SDK core utilities. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used legitimately to decode an HMAC key before cryptographic signing — standard pattern in Azure SDK crypto utilities, not a malicious payload. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dependency used as a TypeScript compilation helper; phantom-dep detection is a known false positive for compiled TypeScript packages. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft Azure SDK packages published via microsoft1es consistently lack Sigstore provenance; this is a stable pattern for this publisher, not a risk indicator. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.13.1 | 3 / 10 | |
| 1.13.0 | 3 / 10 | |
| 1.12.0 | 3 / 10 | |
| 1.11.0 | 2 / 12 | |
| 1.10.0 | 2 / 13 | |
| 1.9.2 | 2 / 13 | |
| 1.9.1 | 2 / 13 | |
| 1.9.0 | 2 / 14 | |
| 1.8.1 | 2 / 14 | |
| 1.8.0 | 2 / 14 | |
| 1.7.0 | 2 / 11 | |
| 1.6.1 | 2 / 31 | |
| 1.6.0 | 2 / 31 | |
| 1.5.0 | 2 / 31 | |
| 1.4.0 | 2 / 30 | |
| 1.3.2 | 2 / 30 | |
| 1.3.1 | 2 / 30 | |
| 1.3.0 | 2 / 30 | |
| 1.2.0 | 2 / 32 | |
| 1.1.1 | 2 / 30 | |
| 1.1.0 | 1 / 30 | |
| 1.0.0 | 1 / 30 |
v1.13.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.12.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.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.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.9.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.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
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.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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.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.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.