applicationinsights 2.4.2
Microsoft Application Insights module for Node.js
applicationinsights@2.4.2 was published on 2023-02-08. Its manifest declares 11 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.0.0.
All applicationinsights versions · Permanent reference to 2.4.2 · Latest release
Package specifications
| Version | 2.4.2 |
|---|---|
| License declaration | MIT |
| Published | 2023-02-08T20:47:18.985Z |
| Node.js requirement | >=8.0.0 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 11 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 1534.95 KiB |
| Published file count | 373 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./out/applicationinsights.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 32 |
| Repository stars | 334 |
| Repository forks | 149 |
Install applicationinsights 2.4.2
npm install applicationinsights@2.4.2 pnpm add applicationinsights@2.4.2 yarn add applicationinsights@2.4.2
Runtime dependencies
- cls-hooked ^4.2.2
- @azure/core-auth ^1.4.0
- @opentelemetry/api ^1.0.4
- diagnostic-channel 1.1.0
- @opentelemetry/core ^1.0.1
- @azure/core-rest-pipeline ^1.10.0
- continuation-local-storage ^3.2.1
- @opentelemetry/sdk-trace-base ^1.0.1
- diagnostic-channel-publishers 1.0.5
- @opentelemetry/semantic-conventions ^1.0.1
- @microsoft/applicationinsights-web-snippet ^1.0.1
Peer requirements
- applicationinsights-native-metrics * (optional peer)
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- @azure/core-auth@1.11.0 — direct
- @azure/core-rest-pipeline@1.25.0 — direct
- @microsoft/applicationinsights-web-snippet@1.2.3 — direct
- @opentelemetry/api@1.10.0 — direct
- @opentelemetry/core@1.30.1 — direct
- @opentelemetry/sdk-trace-base@1.30.1 — direct
- @opentelemetry/semantic-conventions@1.43.0 — direct
- cls-hooked@4.2.2 — direct
- continuation-local-storage@3.2.1 — direct
- diagnostic-channel@1.1.0 — direct
- diagnostic-channel-publishers@1.0.5 — direct
- @azure/abort-controller@2.2.0 — indirect
- @azure/core-util@1.14.0 — indirect
- tslib@2.8.1 — indirect
- @azure/core-tracing@1.4.0 — indirect
- @azure/logger@1.4.0 — indirect
- @typespec/ts-http-runtime@0.3.9 — indirect
- @opentelemetry/semantic-conventions@1.28.0 — indirect
- @opentelemetry/resources@1.30.1 — indirect
- @opentelemetry/semantic-conventions@1.28.0 — indirect
- async-hook-jl@1.7.6 — indirect
- emitter-listener@1.1.2 — indirect
- semver@5.7.2 — indirect
- async-listener@0.6.10 — indirect
- http-proxy-agent@7.0.2 — indirect
- https-proxy-agent@7.0.6 — indirect
- @opentelemetry/semantic-conventions@1.28.0 — indirect
- stack-chain@1.3.7 — indirect
- shimmer@1.2.1 — indirect
- agent-base@7.1.4 — indirect
- debug@4.4.3 — indirect
- ms@2.1.3 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 10/10 — 20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
|---|---|
| Code-Review | 10/10 — all changesets reviewed |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 10/10 — security policy file detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 5/10 — dependency not pinned by hash detected -- score normalized to 5 |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Branch-Protection | 1/10 — branch protection is not maximal on development and all release branches |
| SAST | 3/10 — SAST tool is not run on all commits -- score normalized to 3 |
Evidence and freshness
- https://registry.npmjs.org/applicationinsights/2.4.2 — retrieved 2026-10-29T14:36:16.003Z
- https://api.deps.dev/v3/projects/github.com%2Fmicrosoft%2FApplicationInsights-node.js — retrieved 2026-10-29T13:02:44.179Z
- https://api.deps.dev/v3/systems/npm/packages/applicationinsights/versions/2.4.2 — retrieved 2026-10-29T14:36:16.531Z
- https://api.deps.dev/v3/systems/npm/packages/applicationinsights/versions/2.4.2:dependencies — retrieved 2026-10-29T14:36:16.563Z