@azure/logger
Microsoft Azure SDK for JavaScript - Logger
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@typespec/ts-http-runtime | AI (dependencies): @typespec/ts-http-runtime is a Microsoft-owned package in the Azure SDK ecosystem; its use in @azure/logger is expected and low-risk. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from azure-sdk to microsoft1es is a routine Microsoft internal account rotation; microsoft1es is a well-established Microsoft publishing account. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft1es is Microsoft's established publishing account (3148 approved packages); legitimate org-level maintainer transition. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are tshy multi-dialect build outputs (esm/cjs/browser/react-native); expected for this package's build system. | 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 packages across the Azure SDK. | ai | |
| provenance | no-provenance | AI (provenance): microsoft1es is a well-established Microsoft publisher; lack of Sigstore provenance is common and not a meaningful risk signal for this publisher. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 2 / 10 | |
| 1.2.0 | 2 / 10 | |
| 1.1.4 | 1 / 13 | |
| 1.1.3 | 1 / 13 | |
| 1.1.2 | 1 / 14 | |
| 1.1.1 | 1 / 14 | |
| 1.1.0 | 1 / 14 | |
| 1.0.4 | 1 / 31 | |
| 1.0.3 | 1 / 34 | |
| 1.0.2 | 1 / 40 | |
| 1.0.1 | 1 / 40 | |
| 1.0.0 | 1 / 45 |
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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.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.4
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.