@segment/analytics-browser-actions-braze
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@braze/web-sdk-v3 | AI (dependencies): Aliased Braze SDK dependency for multi-version support; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Segment has not enabled Sigstore provenance for this package family; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata is structural, not indicative of spam/malware. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Segment monorepo sub-package; missing description is a consistent pattern, not a risk signal. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.113.0 | 4 / 0 | |
| 1.112.0 | 4 / 0 | |
| 1.110.0 | 4 / 0 | |
| 1.109.0 | 4 / 0 | |
| 1.104.0 | 4 / 0 | |
| 1.101.0 | 4 / 0 | |
| 1.100.0 | 4 / 0 | |
| 1.96.0 | 4 / 0 | |
| 1.95.0 | 4 / 0 | |
| 1.94.0 | 4 / 0 | |
| 1.91.0 | 4 / 0 |
v1.112.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.110.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.109.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.104.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.101.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.91.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.