@azure/monitor-query
Deprecated ⚠️: use @azure/monitor-query-logs, @azure/monitor-query-metrics and @azure/arm-monitor.
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:@azure/logger | AI (dependencies): Official Microsoft Azure SDK core package; unvetted status reflects approval graph gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@azure/core-auth | AI (dependencies): Official Microsoft Azure SDK core package; unvetted status reflects approval graph gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@azure/core-util | AI (dependencies): Official Microsoft Azure SDK core package; unvetted status reflects approval graph gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@azure/core-client | AI (dependencies): Official Microsoft Azure SDK core package; unvetted status reflects approval graph gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@azure/core-paging | AI (dependencies): Official Microsoft Azure SDK core package; unvetted status reflects approval graph gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@azure/core-tracing | AI (dependencies): Official Microsoft Azure SDK core package; unvetted status reflects approval graph gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@azure/core-rest-pipeline | AI (dependencies): Official Microsoft Azure SDK core package; unvetted status reflects approval graph gap, not a real risk. | ai | |
| phantom-deps | phantom-dep:@azure/core-rest-pipeline | AI (phantom-deps): Framework-scoped Azure SDK package loaded by convention; not a genuine phantom dependency risk. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft publisher (microsoft1es); lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.3.3 | 8 / 19 | |
| 1.3.2 | 8 / 19 | |
| 1.3.1 | 8 / 36 | |
| 1.3.0 | 8 / 36 | |
| 1.2.0 | 8 / 36 | |
| 1.1.1 | 7 / 39 | |
| 1.1.0 | 7 / 39 | |
| 1.0.4 | 7 / 41 | |
| 1.0.3 | 7 / 41 | |
| 1.0.2 | 7 / 41 | |
| 1.0.1 | 7 / 42 | |
| 1.0.0 | 7 / 44 |
v1.3.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.3.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.3.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.2.0
1 finding[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. 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.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.