@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, so a manually published version cannot be tied back to a reviewed commit.
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 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 4.4.3 | 5 / 27 | |
| 4.4.2 | 5 / 27 | |
| 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 | |
| 4.3.6 | 5 / 16 | |
| 4.3.5 | 5 / 16 | |
| 4.3.4 | 5 / 16 | |
| 4.3.3 | 5 / 15 | |
| 4.3.2 | 5 / 15 | |
| 4.3.1 | 5 / 15 | |
| 4.3.0 | 5 / 15 | |
| 4.2.2 | 5 / 15 | |
| 4.2.1 | 5 / 15 | |
| 4.2.0 | 5 / 15 | |
| 4.1.2 | 5 / 15 | |
| 4.1.1 | 5 / 15 | |
| 4.1.0 | 5 / 15 | |
| 4.0.7 | 5 / 15 | |
| 4.0.6 | 5 / 15 | |
| 4.0.5 | 5 / 15 | |
| 4.0.4 | 5 / 15 | |
| 4.0.3 | 5 / 15 | |
| 4.0.2 | 5 / 15 | |
| 4.0.1 | 5 / 4 | |
| 4.0.0 | 5 / 4 |
v4.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
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.2.1
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.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (microsoft1es) than the most recent previously approved version (msftapplicationinsights) on 2024-03-21, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (microsoft1es) than the most recent previously approved version (msftapplicationinsights) on 2024-03-13, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
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.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.