@segment/analytics-browser-actions-utils
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Org-wide migration to CI/CD publishing (GitHub Actions bot) with SLSA provenance. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consolidation to twilio-supply-chain reflects org-wide publishing process change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Mass maintainer removal is org-wide cleanup coinciding with CI/CD migration, not a takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo utility package; missing metadata is expected, not indicative of spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this internal utility package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all versions; low risk for this established scoped package. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 1.100.0 | 1 / 0 | |
| 1.99.0 | 1 / 0 | |
| 1.98.0 | 1 / 0 | |
| 1.97.0 | 1 / 0 | |
| 1.96.0 | 1 / 0 | |
| 1.95.0 | 1 / 0 | |
| 1.94.0 | 1 / 0 | |
| 1.93.0 | 1 / 0 | |
| 1.92.0 | 1 / 0 | |
| 1.91.0 | 1 / 0 | |
| 1.90.0 | 1 / 0 | |
| 1.89.0 | 1 / 0 | |
| 1.88.0 | 1 / 0 | |
| 1.87.0 | 1 / 0 | |
| 1.86.0 | 1 / 0 | |
| 1.85.0 | 1 / 0 | |
| 1.84.0 | 1 / 0 | |
| 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.1 | 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.0 | 1 / 0 | |
| 1.51.0 | 1 / 0 |
v1.100.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.99.0
2 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.81.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.80.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.79.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.78.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.77.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.75.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.67.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (forgetfulfellow) than the most recent previously approved version (joe.ayoub.segment) 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.51.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marinhero) than the most recent previously approved version (joe.ayoub.segment) 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.