@segment/action-destinations
Destination Actions engine and definitions.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Large established org package; lack of provenance is consistent across all versions of this package. | ai | |
| dependencies | unvetted-dep:@segment/actions-core | AI (dependencies): First-party Segment monorepo package; stable dependency across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is intentionally listed as a runtime dep for Node.js type definitions; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.494.0 | 21 / 7 | |
| 3.493.0 | 21 / 7 | |
| 3.492.0 | 21 / 7 | |
| 3.491.0 | 21 / 7 | |
| 3.490.0 | 21 / 7 | |
| 3.489.0 | 21 / 7 | |
| 3.488.0 | 21 / 7 | |
| 3.487.0 | 21 / 7 | |
| 3.486.0 | 21 / 7 |
v3.494.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.493.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.491.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.490.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.489.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.488.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.487.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.486.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.