← Home

@segment/actions-shared

npm Repository

Shared destination action methods and definitions.

22
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

harksinghfhalim-segmentcfreeldelossantoshjoonpmceline-segmentpmcanseco-segmentmasiraamillet89cholt002av-segmentaghotikarvikrant-segmentlarryatsegmentscruwys1kyliepedersenjinaparkcdignam-segmentsegmentiojrupasinghelateefatyash-twiliosowjanyasegmentebru.odokryanligonlpediredlabrookstaylorjrnithan-twiliodean-huynhwdbettsn2parkojayakrishnannairrhall-twiliokarimkeshwanityson_segmentjgabe13bgamwellpoojasegmentmaryam.sharifwally.tgsalolivareserikdwchenxiangzhangjusteenmericssonprayansh-segmenttjeremylarkinbsneeddanieljackinssegment-sethsayan-das-injames9446priscilla.giattinlsundrew-thompsonsegment-jsinghmcoulibaliandrius-segmentvalerieernstnithin-bennyainatancincoskondamuriclintz.segreplateroslenin-twiliocsayusoseanhan-segmentnevermore2022ama0223gilomerandrew.hoylemarcelopveric.rognerkdharaiyajon.anderson-at-segment.comstacy.songrexatsegmentnickaguilarbradenbeckerreneewangdan.laskysam.tapialnambavikramkumar19mpriyad25jeremy.parkersmidgesnageshgolemsudojatinpmaidsethsegmentjair.avilesmanali-bhosaleelmoselyeechtoombspeterdemartinivincen7transujin0lfdelossantosemmy.byrnefelttripsa-jsooterlluque-twiliokevinburkesegmentafsha-nazim-segsong4youdavid.anusontarangkul.segmentjyim008michaelghsegaishikawakitwjosiahtanya.gupta.segmentsindhusegmentprabhnoor1997chihchun-twiliopmiller-twiliovbatanovsimpixelatedmcullenmeyerneeharikakondipatiarunlalam-segmentmschaszbergershuvrajit9904abhinavsurekavaradarajan-twimmanojblangtwiliojsh-wusethnutetwiliorrivera-segmentsegment-adminbgillantcgilbertmckern_segmentmaneesh.dharma29joetessydominicbarnesmugelstadjalexy12pmuninwhaider_twilioariel.silvestrishraddha-twiliomichelrbrandon.scott-segmentjfehrman.segmentprayansh-twiliodangmai-segmentaaronklishbrianhumphreystwiliormukundanashwitha.bgryanrouleau-segmentfunlutdibaccofauzy.yynlubchencoarubiochavezphillip.thomasjkusa_segmentrollcodemeg1000nainy.agrawalseg-rustybaileyjbandi-twiliosaisagarkappaganthulaforgetfulfellowpooja.patiljoe.ayoub.segmenthmohanram_segbrian.aguirreenyi.asonyefarhan0581tbrennanjparag.pandaharsh.vardhansshaikh_segmentxinghao.huangshupadhyayjohn.lee1100kx-segmentsegment_fandazu70sai-patanjaliemilyjiay.yuea_segmentyli119pooyajbharath.boregowdaigracheva-twiliobenattwiliomarinherodobrin.ganevalfrimpongdharpatelalecjacobs-segmentcjo2yashnit-segmentdltnbrks-segmentachandrashekaranhimanshuphpraguptatw-dgarciaalayvoraaparna.singhalynguyentimmyzsearcylweimersegmentanton-vylushchakazhaotwiliorokatyalkjoerresmsarafvikakumaraditi.raveeshchenchensegmentcomsanket.mishraodoren_segmentjxin_twiliorcheedhallajbasiglio-segmentviveksainaneesegmentpriyanshisabhinav.mehtapreetypakash.gautam07nanotimmyshkprsrivig21ssunejabala.singareddymoyara2arjunbhandageakodankiryrodhilton_twiliocdelaomartinezgbatraspenceratticksegmentseansundareswar.jayakumarhrishi-segmentkalyannistalavaibhavnandabannapplesrishti-nemagsolis_segmentitsarijitraynirai-6bhavanki-segmenthhwsegmentandrew.hallkspachinojcohentwilio2dsolownanette.ranesamigandhiguthriesegmentmiguelpdiaz8mansarikathlynnchris.chanmhodarkar-segmentsandhya16hema-bahirwani-segmentbnakkinapraveenugiriighorelanemery-segmentwlumsegmentnat-gridneedcaffeinekbhargavaram-sgirfan.ali.segmented-twilion-npmaubreysinesethgrid_segmentjibrangseg-leonelsanchessmccoy-twiliodevthaleandwivediaditya_segmentpoojapatilseggaprabhumonusegmentjkilpatrick-segmentdasancheznsolanki-staratitshah.segwongwilliamankit.gupta.unthinkableshazan77darcimmjesswatsonafgan-segmenttwiliochiragfarbod_segmentgrsmithharsh-joshi99anvesh_reddy_1311aleman842abueide-segmentcaseyk09ankigupta92psandquistjagsinghdcp-twilioagerbas-segmentamitsinglaatsegjoy-twilioamanda.majinesh-twilioardev_npmnikumar-segment-newsarthak-twilionupur-twiliovkundnaniprathoresegmentmmilhansegshubhkrishnakvivekabhiramajsinghsegkkolhe-twilioprassinghseg-ajasinghmdkhan-twmahitmfkimbelll0adedjay-savlalaksh25sbommarito-segmentcsmonlaibha_segmentayagrawal7maygupta

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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:cheerio 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:escape-goat AI (phantom-deps): Declared in package.json deps; monorepo shared lib pattern. ai

Versions (showing 22 of 22)

Version Deps Published
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

v1.154.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

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

v1.150.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.149.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.148.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.147.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.146.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

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

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

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

v1.141.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.140.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.139.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.138.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

v1.136.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.135.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

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