applicationinsights
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@opentelemetry/exporter-metrics-otlp-http | AI (phantom-deps): Config-referenced OpenTelemetry exporter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-metrics | AI (phantom-deps): Config-referenced OpenTelemetry package; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@azure/core-rest-pipeline | AI (phantom-deps): Framework-scoped Azure package; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@azure/opentelemetry-instrumentation-azure-sdk | AI (dependencies): First-party Microsoft/Azure OpenTelemetry instrumentation package; unvetted status is a pipeline artifact, not a security risk. | ai | |
| dependencies | unvetted-dep:@azure/functions-old | AI (dependencies): This is a deliberate npm alias for @azure/[email protected] used for backward compatibility — a first-party Microsoft package, not a security concern. | ai | |
| dependencies | unvetted-dep:@azure/monitor-opentelemetry-exporter | AI (dependencies): First-party Microsoft/Azure OpenTelemetry exporter package; unvetted status is a pipeline artifact, not a security risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in etwWriter.js loads an optional native ETW module after filesystem access check — standard pattern for optional native bindings, not arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:@azure/opentelemetry-instrumentation-azure-sdk | AI (phantom-deps): OpenTelemetry instrumentation packages are registered by convention rather than directly imported; this is expected behavior for this SDK type. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.15.0 | 23 / 16 | |
| 3.14.0 | 23 / 16 | |
| 3.13.0 | 23 / 16 | |
| 3.12.1 | 23 / 16 | |
| 3.12.0 | 23 / 16 | |
| 3.11.0 | 23 / 16 | |
| 3.10.0 | 22 / 16 | |
| 3.9.0 | 24 / 16 |
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.