@azure/monitor-opentelemetry
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): microsoft-oss-releases is Microsoft's OSS release automation account; expected for Azure SDK packages. | ai | |
| dependencies | unvetted-dep:@azure/monitor-opentelemetry-exporter | AI (dependencies): Official Azure SDK package from Microsoft; core dependency of this Azure Monitor distro. | ai | |
| dependencies | unvetted-dep:@microsoft/applicationinsights-web-snippet | AI (dependencies): Official Microsoft Application Insights package; expected dependency for Azure Monitor integration. | ai | |
| dependencies | unvetted-dep:@opentelemetry/winston-transport | AI (dependencies): Legitimate OpenTelemetry ecosystem package; expected dependency for Azure Monitor OpenTelemetry distro. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-trace-node | AI (phantom-deps): Declared in dependencies and referenced in config; common pattern in SDK monorepo packages. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/winston-transport | AI (phantom-deps): Declared in dependencies and referenced in config; common pattern in SDK monorepo packages. | ai | |
| dependencies | unvetted-dep:@azure/opentelemetry-instrumentation-azure-sdk | AI (dependencies): Official Azure SDK OpenTelemetry instrumentation package; expected dependency for this distro. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.18.0 | 28 / 17 | |
| 1.17.0 | 28 / 17 | |
| 1.16.0 | 28 / 17 | |
| 1.15.0 | 28 / 17 | |
| 1.14.2 | 28 / 17 | |
| 1.14.1 | 28 / 17 | |
| 1.13.1 | 29 / 12 | |
| 1.12.0 | 29 / 11 | |
| 1.11.1 | 29 / 11 |
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.