@microsoft/1ds-post-js
Microsoft Application Insights JavaScript SDK - 1ds-post-channel-js
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Microsoft SDK package published by microsoft1es with 3559 approved packages; lack of Sigstore provenance is not a meaningful risk signal here. | ai | |
| dependencies | unvetted-dep:@microsoft/applicationinsights-core-js | AI (dependencies): First-party Microsoft ApplicationInsights SDK dependency; part of the same package family published by the same trusted publisher. | ai | |
| dependencies | unvetted-dep:@microsoft/applicationinsights-shims | AI (dependencies): First-party Microsoft ApplicationInsights SDK dependency; part of the same package family published by the same trusted publisher. | ai | |
| dependencies | unvetted-dep:@microsoft/dynamicproto-js | AI (dependencies): Microsoft-published utility library used across the ApplicationInsights SDK ecosystem; stable dependency. | ai | |
| dependencies | unvetted-dep:@nevware21/ts-utils | AI (dependencies): Well-known TypeScript utility library used across the ApplicationInsights SDK; consistent dependency across many versions. | ai | |
| dependencies | unvetted-dep:@nevware21/ts-async | AI (dependencies): Well-known TypeScript async utility library used across the ApplicationInsights SDK; consistent dependency across many versions. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.4.1 | 5 / 16 | |
| 4.3.11 | 5 / 16 | |
| 4.3.10 | 5 / 16 | |
| 4.3.9 | 5 / 16 | |
| 4.3.8 | 5 / 16 | |
| 4.3.7 | 5 / 16 |
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.