← Home

@segment/analytics-browser-actions-1flow

npm Repository Homepage
62
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

twilio-supply-chainsegmentiosegment-admin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Org-wide migration to GitHub Actions CI/CD publishing with SLSA provenance; not compromise. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer is part of Segment/Twilio org transition to automated publishing. ai
maintainer-change maintainer-removed AI (maintainer-change): Bulk removal reflects consolidation to CI bot publisher across the monorepo, not takeover. ai
bogus-package bogus-package AI (bogus-package): Scoped monorepo package under @segment; missing metadata is a known pattern for this package family. ai
npm-metadata no-description AI (npm-metadata): Consistent across all @segment/analytics-browser-actions-* packages; not a malware signal. ai

Versions (showing 62 of 62)

Version Deps Published
1.83.0 1 / 0
1.82.0 1 / 0
1.81.0 1 / 0
1.80.0 1 / 0
1.79.0 1 / 0
1.78.0 1 / 0
1.77.0 1 / 0
1.76.0 1 / 0
1.75.0 1 / 0
1.74.0 1 / 0
1.73.0 1 / 0
1.72.0 1 / 0
1.71.0 1 / 0
1.70.0 1 / 0
1.69.0 1 / 0
1.68.0 1 / 0
1.67.0 1 / 0
1.66.0 1 / 0
1.65.0 1 / 0
1.64.0 1 / 0
1.63.0 1 / 0
1.62.0 1 / 0
1.61.0 1 / 0
1.60.0 1 / 0
1.59.0 1 / 0
1.58.0 1 / 0
1.57.0 1 / 0
1.56.0 1 / 0
1.55.0 1 / 0
1.54.0 1 / 0
1.53.0 1 / 0
1.52.1 1 / 0
1.52.0 1 / 0
1.51.0 1 / 0
1.50.0 1 / 0
1.49.0 1 / 0
1.48.0 1 / 0
1.47.0 1 / 0
1.46.0 1 / 0
1.45.0 1 / 0
1.44.0 1 / 0
1.43.0 1 / 0
1.42.0 1 / 0
1.41.0 1 / 0
1.40.0 1 / 0
1.39.0 1 / 0
1.38.0 1 / 0
1.37.0 1 / 0
1.36.0 1 / 0
1.35.0 1 / 0
1.34.0 1 / 0
1.33.0 1 / 0
1.32.0 1 / 0
1.30.0 1 / 0
1.29.0 1 / 0
1.28.0 1 / 0
1.26.0 1 / 0
1.25.0 1 / 0
1.24.0 1 / 0
1.23.0 1 / 0
1.22.0 1 / 0
1.21.0 1 / 0

v1.83.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.82.0

2 findings
HIGH Publisher changed: varadarajan-tw → GitHub Actions (on 2026-07-09) provenance

This version was published by a different npm account than previous versions on 2026-07-09. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.63.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.62.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.61.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.60.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.59.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.58.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.57.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.56.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.55.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.54.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.53.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.52.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.52.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.51.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.50.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.49.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.48.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.47.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.46.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.45.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.44.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.43.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.42.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.41.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.40.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.39.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.38.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.37.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.36.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: marinhero → forgetfulfellow (on 2024-07-23, known maintainer) provenance

This version was published by a different npm account (forgetfulfellow) than the most recent previously approved version (marinhero) on 2024-07-23, but forgetfulfellow 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.

v1.34.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: marinhero → forgetfulfellow (on 2024-07-09, known maintainer) provenance

This version was published by a different npm account (forgetfulfellow) than the most recent previously approved version (marinhero) on 2024-07-09, but forgetfulfellow 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.

v1.33.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: varadarajan-tw → marinhero (on 2024-07-03, known maintainer) provenance

This version was published by a different npm account (marinhero) than the most recent previously approved version (varadarajan-tw) on 2024-07-03, but marinhero 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.

v1.32.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: varadarajan-tw → joe.ayoub.segment (on 2024-07-02, known maintainer) provenance

This version was published by a different npm account (joe.ayoub.segment) than the most recent previously approved version (varadarajan-tw) on 2024-07-02, but joe.ayoub.segment 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.

v1.30.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: forgetfulfellow → varadarajan-tw (on 2024-07-02, known maintainer) provenance

This version was published by a different npm account (varadarajan-tw) than the most recent previously approved version (forgetfulfellow) on 2024-07-02, but varadarajan-tw 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.

v1.29.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.28.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.26.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.25.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.24.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.23.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.22.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.21.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.