← Home

@segment/analytics-browser-actions-intercom

npm
23
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
dependencies unvetted-dep:@segment/actions-core AI (dependencies): First-party @segment scoped dependency; stable pattern across all versions of this package. ai
dependencies unvetted-dep:@segment/browser-destination-runtime AI (dependencies): First-party @segment scoped dependency; stable pattern across all versions of this package. ai
maintainer-change maintainer-added AI (maintainer-change): Large Segment org package; team rotation is expected and not indicative of takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): Same rationale — org-level team churn, not a hostile takeover signal. ai
bogus-package bogus-package AI (bogus-package): Scoped monorepo package; missing metadata is typical for internal @segment org packages across all 381 versions. ai
npm-metadata no-description AI (npm-metadata): Consistent across all versions of this monorepo package; not a malware indicator. ai

Versions (showing 23 of 23)

Version Deps Published
1.109.0 3 / 0
1.108.0 3 / 0
1.107.0 3 / 0
1.106.0 3 / 0
1.105.0 3 / 0
1.104.0 3 / 0
1.103.0 3 / 0
1.102.0 3 / 0
1.101.0 3 / 0
1.100.0 3 / 0
1.99.0 3 / 0
1.98.0 3 / 0
1.97.0 3 / 0
1.96.0 3 / 0
1.95.0 3 / 0
1.94.0 3 / 0
1.93.0 3 / 0
1.92.0 3 / 0
1.91.0 3 / 0
1.90.0 3 / 0
1.89.0 3 / 0
1.88.0 3 / 0
1.87.0 3 / 0

v1.109.0

1 finding
LOW No provenance attestation provenance

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

v1.107.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.106.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.105.0

1 finding
LOW No provenance attestation provenance

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

v1.104.0

1 finding
LOW No provenance attestation provenance

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

v1.103.0

1 finding
LOW No provenance attestation provenance

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

v1.102.0

1 finding
LOW No provenance attestation provenance

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

v1.101.0

1 finding
LOW No provenance attestation provenance

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

v1.100.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.99.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.98.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.97.0

1 finding
LOW No provenance attestation provenance

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

v1.96.0

1 finding
LOW No provenance attestation provenance

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

v1.95.0

1 finding
LOW No provenance attestation provenance

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

v1.94.0

1 finding
LOW No provenance attestation provenance

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

v1.93.0

1 finding
LOW No provenance attestation provenance

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

v1.92.0

1 finding
LOW No provenance attestation provenance

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

v1.91.0

1 finding
LOW No provenance attestation provenance

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

v1.90.0

1 finding
LOW No provenance attestation provenance

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

v1.89.0

1 finding
LOW No provenance attestation provenance

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

v1.88.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.87.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.