@segment/actions-shared
Shared destination action methods and definitions.
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): Move to CI/CD publisher with SLSA attestation; org-wide automation, not compromise. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired removals with additions reflect org team changes, not a hostile takeover signal for this package. | ai | |
| dependencies | unvetted-dep:@segment/actions-core | AI (dependencies): First-party Segment dependency; stable sibling package in the same monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Segment monorepo package; provenance not enabled for this publisher; stable pattern across versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Active Segment org package with frequent releases; team member additions are routine for this package. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Declared in package.json deps; monorepo shared lib pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@amplitude/ua-parser-js | AI (phantom-deps): Declared in package.json deps; monorepo shared lib pattern. | ai | |
| phantom-deps | phantom-dep:escape-goat | AI (phantom-deps): Declared in package.json deps; monorepo shared lib pattern. | ai | |
| phantom-deps | phantom-dep:liquidjs | AI (phantom-deps): Declared in package.json deps; monorepo shared lib pattern. | ai | |
| phantom-deps | phantom-dep:cheerio | AI (phantom-deps): Declared in package.json deps; monorepo shared lib pattern. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 1.156.0 | 7 / 3 | |
| 1.155.0 | 7 / 3 | |
| 1.154.0 | 7 / 3 | |
| 1.153.0 | 7 / 3 | |
| 1.152.0 | 7 / 3 | |
| 1.151.0 | 7 / 3 | |
| 1.150.0 | 7 / 3 | |
| 1.149.0 | 7 / 3 | |
| 1.148.0 | 7 / 3 | |
| 1.147.0 | 7 / 3 | |
| 1.146.0 | 7 / 3 | |
| 1.145.0 | 7 / 3 | |
| 1.144.0 | 7 / 3 | |
| 1.143.0 | 7 / 3 | |
| 1.142.0 | 7 / 3 | |
| 1.141.0 | 7 / 3 | |
| 1.140.0 | 7 / 3 | |
| 1.139.0 | 7 / 3 | |
| 1.138.0 | 7 / 3 | |
| 1.137.0 | 7 / 3 | |
| 1.136.0 | 7 / 3 | |
| 1.135.0 | 7 / 3 | |
| 1.134.0 | 7 / 3 | |
| 1.133.0 | 7 / 3 | |
| 1.132.0 | 7 / 3 | |
| 1.131.0 | 7 / 3 | |
| 1.130.0 | 7 / 3 | |
| 1.129.0 | 7 / 3 | |
| 1.128.0 | 7 / 3 | |
| 1.127.0 | 7 / 3 | |
| 1.126.0 | 7 / 3 | |
| 1.125.0 | 7 / 3 | |
| 1.124.0 | 7 / 3 | |
| 1.123.0 | 7 / 3 | |
| 1.122.0 | 7 / 3 | |
| 1.121.1 | 7 / 3 | |
| 1.121.0 | 7 / 3 | |
| 1.120.0 | 7 / 3 | |
| 1.119.0 | 7 / 3 | |
| 1.118.0 | 7 / 3 | |
| 1.117.0 | 7 / 3 | |
| 1.116.0 | 7 / 3 | |
| 1.115.0 | 7 / 3 | |
| 1.114.0 | 7 / 3 | |
| 1.113.0 | 7 / 3 | |
| 1.112.0 | 7 / 3 | |
| 1.111.0 | 7 / 3 | |
| 1.110.0 | 7 / 3 | |
| 1.109.0 | 7 / 3 | |
| 1.108.0 | 7 / 3 | |
| 1.107.0 | 7 / 3 | |
| 1.106.0 | 7 / 3 | |
| 1.105.0 | 7 / 3 | |
| 1.104.0 | 7 / 3 | |
| 1.103.0 | 7 / 3 | |
| 1.102.0 | 7 / 3 | |
| 1.101.0 | 7 / 3 | |
| 1.99.0 | 7 / 3 | |
| 1.98.0 | 7 / 3 | |
| 1.97.0 | 7 / 3 | |
| 1.95.0 | 7 / 3 | |
| 1.94.0 | 7 / 3 | |
| 1.93.0 | 7 / 3 | |
| 1.92.0 | 7 / 3 | |
| 1.91.0 | 7 / 3 | |
| 1.90.0 | 7 / 3 | |
| 1.89.0 | 7 / 3 |
v1.156.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.155.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.132.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.131.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.130.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.129.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.128.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.127.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.126.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.125.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.124.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.123.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.122.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.121.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.121.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.119.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.118.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.117.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.116.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.115.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.114.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.113.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.112.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.111.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.110.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.109.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.107.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.106.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.105.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.104.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 (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.103.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 (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.102.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 (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.101.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 (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.99.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 (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.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.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.