@microsoft/applicationinsights-core-js
Microsoft Application Insights Core Javascript SDK
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:@nevware21/ts-async | AI (dependencies): Known dependency in the Application Insights SDK ecosystem; consistently used across many versions of this package. | ai | |
| dependencies | unvetted-dep:@nevware21/ts-utils | AI (dependencies): Known dependency in the Application Insights SDK ecosystem; consistently used across many versions of this package. | ai | |
| dependencies | unvetted-dep:@microsoft/dynamicproto-js | AI (dependencies): Microsoft-owned dependency used throughout the Application Insights SDK; stable and expected. | ai | |
| dependencies | unvetted-dep:@microsoft/applicationinsights-shims | AI (dependencies): First-party Microsoft Application Insights sibling package; expected dependency for this SDK. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package published without provenance attestation; consistent with prior versions and not a risk signal for this publisher. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.4.1 | 4 / 22 | |
| 3.3.11 | 4 / 22 | |
| 3.3.10 | 4 / 22 | |
| 3.3.9 | 4 / 22 | |
| 3.3.8 | 4 / 22 | |
| 3.3.7 | 4 / 23 |
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.