@segment/analytics-browser-actions-ripe
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Segment org package with large team; maintainer rotation is expected across 348 versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added in a large org; consistent with internal team changes, not takeover. | ai | |
| dependencies | unvetted-dep:@segment/actions-core | AI (dependencies): Internal @segment ecosystem dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@segment/browser-destination-runtime | AI (dependencies): Internal @segment ecosystem dependency; stable pattern across all versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo-published Segment action package; missing description is a consistent pattern across the suite, not a malware signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Segment monorepo package; missing metadata is a consistent pattern across all versions, not a spam indicator. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 1.90.0 | 2 / 0 | |
| 1.89.0 | 2 / 0 | |
| 1.88.0 | 2 / 0 | |
| 1.87.0 | 2 / 0 | |
| 1.86.0 | 2 / 0 | |
| 1.85.0 | 2 / 0 | |
| 1.84.0 | 2 / 0 | |
| 1.83.0 | 2 / 0 |
v1.97.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. 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. Consider requesting the maintainer enable provenance via CI/CD.
v1.90.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.