← Home

@segment/analytics-browser-actions-google-analytics-4

npm
21
Versions
—
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.segfjahangirwongwilliamankit.gupta.unthinkableshazan77darcimmjesswatsonafgan-segmenttwiliochiraggrsmithharsh-joshi99anvesh_reddy_1311aleman842abueide-segmentcaseyk09ankigupta92psandquistjagsinghdcp-twiliosprajapati89agerbas-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
provenance publisher-changed AI (provenance): Segment org regularly rotates publishers across their analytics packages; new publisher has strong track record. ai
maintainer-change maintainer-added AI (maintainer-change): Segment internal team rotation; consistent with org-wide maintainer management pattern. ai
maintainer-change maintainer-removed AI (maintainer-change): Segment internal team rotation; removal paired with addition is expected for this org. ai
bogus-package bogus-package AI (bogus-package): Scoped @segment package; missing metadata is a known pattern for this package family, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Consistent across all versions of this scoped internal package; not a malice signal. ai

Versions (showing 21 of 21)

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

v1.108.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.107.0

2 findings
HIGH Publisher changed: mdkhan-tw → varadarajan-tw (on 2026-03-17) provenance

This version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.106.0

2 findings
HIGH Publisher changed: mdkhan-tw → varadarajan-tw (on 2026-02-24) provenance

This version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.105.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.99.0

1 finding
LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.95.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.