← Home

@segment/destinations-manifest

10
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
maintainer-change maintainer-added AI (maintainer-change): Trusted-publisher provenance confirms legitimate org-side maintainer consolidation. ai
maintainer-change maintainer-removed AI (maintainer-change): Large maintainer list pruning tied to CI/CD provenance switch, not compromise. ai
phantom-deps phantom-dep:@segment/analytics-browser-actions-cj AI (phantom-deps): Same-org packages dynamically required via index.ts destination registry. ai
phantom-deps phantom-dep:@segment/analytics-browser-actions-heap AI (phantom-deps): Same org scope; loaded dynamically. Stable false positive. ai
semgrep semgrep:dynamic-require AI (semgrep): Core design of this manifest package: loads destination plugins by name via dynamic require. Stable pattern across all versions. ai
phantom-deps phantom-dep:@segment/analytics-browser-actions-google-analytics-4 AI (phantom-deps): Same org scope; loaded dynamically. Stable false positive. ai
phantom-deps phantom-dep:@segment/analytics-browser-actions-braze AI (phantom-deps): Same org scope; loaded dynamically. Stable false positive. ai
phantom-deps phantom-dep:@segment/analytics-browser-hubble-web AI (phantom-deps): All @segment deps are loaded dynamically via require(destinationName); phantom-dep heuristic is a stable false positive for this package. ai
phantom-deps phantom-dep:@segment/analytics-browser-actions-vwo AI (phantom-deps): Same org scope; loaded dynamically. Stable false positive. ai

Versions (showing 10 of 10)

Version Deps Published
1.160.0 47 / 0
1.159.0 47 / 0
1.158.0 47 / 0
1.155.0 48 / 0
1.142.0 45 / 0
1.134.0 43 / 0
1.120.0 40 / 0
1.114.0 40 / 0
1.113.0 40 / 0
1.57.0 39 / 0

v1.160.0

2 findings
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.

INFO Publisher changed: varadarajan-tw → GitHub Actions (on 2026-07-09, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (varadarajan-tw) on 2026-07-09, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v1.57.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.