@segment/analytics-browser-actions-friendbuy
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): Large Segment/Twilio org package; maintainer rotations are routine across this publisher family. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added; consistent with org-level team rotation, not a takeover. | ai | |
| dependencies | unvetted-dep:@segment/actions-core | AI (dependencies): First-party Segment monorepo dependency; stable pattern across all @segment/analytics-browser-actions-* packages. | ai | |
| dependencies | unvetted-dep:@segment/browser-destination-runtime | AI (dependencies): First-party Segment runtime dep; consistent across the entire destination plugin family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @segment browser-actions packages; not a spam indicator here. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across this package family; low risk given established publisher org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the @segment monorepo; sparse metadata is consistent across all versions of this package family. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.104.0 | 3 / 0 | |
| 1.103.0 | 3 / 0 | |
| 1.102.0 | 3 / 0 | |
| 1.101.0 | 3 / 0 | |
| 1.100.0 | 3 / 0 | |
| 1.99.0 | 3 / 0 | |
| 1.98.0 | 3 / 0 | |
| 1.97.0 | 3 / 0 | |
| 1.96.0 | 3 / 0 | |
| 1.95.0 | 3 / 0 | |
| 1.94.0 | 3 / 0 | |
| 1.93.0 | 3 / 0 | |
| 1.92.0 | 3 / 0 | |
| 1.91.0 | 3 / 0 | |
| 1.90.0 | 3 / 0 | |
| 1.89.0 | 3 / 0 | |
| 1.88.0 | 3 / 0 | |
| 1.87.0 | 3 / 0 | |
| 1.86.0 | 3 / 0 | |
| 1.85.0 | 3 / 0 | |
| 1.84.0 | 3 / 0 | |
| 1.83.0 | 3 / 0 |
v1.104.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.102.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.
v1.101.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.
v1.100.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.99.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.
v1.98.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.97.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.95.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.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.
v1.92.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.
v1.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.90.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.89.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.88.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.86.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.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.
v1.84.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.
v1.83.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.