@microsoft/1ds-core-js
Microsoft Application Insights JavaScript SDK - 1ds-core-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 with 1866-day history; lack of Sigstore provenance is common and not a risk signal for this publisher. | ai | |
| phantom-deps | phantom-dep:@nevware21/ts-async | AI (phantom-deps): Declared in both dependencies and devDependencies; used in bundled output rather than direct ES module imports. Normal for this SDK package. | ai | |
| phantom-deps | phantom-dep:@microsoft/dynamicproto-js | AI (phantom-deps): Same Microsoft org scope; used in bundled output. Phantom detection is a false positive for this SDK package. | ai | |
| phantom-deps | phantom-dep:@microsoft/applicationinsights-shims | AI (phantom-deps): Same Microsoft org scope; used in bundled output. Phantom detection is a false positive for this SDK package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.4.1 | 5 / 22 | |
| 4.3.11 | 5 / 22 | |
| 4.3.10 | 5 / 22 | |
| 4.3.9 | 5 / 22 | |
| 4.3.8 | 5 / 22 | |
| 4.3.7 | 5 / 23 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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.