@segment/analytics-browser-actions-braze-cloud-plugins
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo plugin; missing metadata fields are normal for internal Segment packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across this package's 376 versions; not a malice indicator. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.113.0 | 2 / 0 | |
| 1.112.0 | 2 / 0 | |
| 1.111.0 | 2 / 0 | |
| 1.110.0 | 2 / 0 | |
| 1.109.0 | 2 / 0 | |
| 1.108.0 | 2 / 0 | |
| 1.107.0 | 2 / 0 | |
| 1.106.0 | 2 / 0 | |
| 1.105.0 | 2 / 0 | |
| 1.104.0 | 2 / 0 | |
| 1.103.0 | 2 / 0 | |
| 1.102.0 | 2 / 0 | |
| 1.101.0 | 2 / 0 | |
| 1.100.0 | 2 / 0 | |
| 1.99.0 | 2 / 0 | |
| 1.98.0 | 2 / 0 | |
| 1.97.0 | 2 / 0 | |
| 1.96.0 | 2 / 0 | |
| 1.95.0 | 2 / 0 | |
| 1.94.0 | 2 / 0 | |
| 1.93.0 | 2 / 0 | |
| 1.92.0 | 2 / 0 | |
| 1.91.0 | 2 / 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.111.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.107.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.106.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.103.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.102.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.99.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.98.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.92.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.