@segment/destinations-manifest
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 |
|---|---|---|---|---|
| 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-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 | |
| phantom-deps | phantom-dep:@segment/analytics-browser-actions-heap | 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-actions-google-analytics-4 | AI (phantom-deps): Same org scope; loaded dynamically. Stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.159.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.155.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.142.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.134.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.114.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.113.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.