← Home

@segment/analytics-browser-actions-ripe

npm
51
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, so a manually published version cannot be tied back to a reviewed commit.

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-twiliovbatanovsimpixelatedmcullenmeyerneeharikakondipatieric-hydearunlalam-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.halljcohentwilio2dsolownanette.ranesamigandhiguthriesegmentmiguelpdiaz8mansarisandhya16hema-bahirwani-segmentbnakkinapraveenugiriighorelanemery-segmentwlumsegmentnat-gridneedcaffeinekbhargavaram-sgirfan.ali.segmented-twilion-npmaubreysinesethgrid_segmentjibrangseg-leonelsanchessmccoy-twiliodevthaleandwivedipoojapatilseggaprabhumonusegmentatitshah.segwongwilliamankit.gupta.unthinkabletwiliochiraggrsmithharsh-joshi99ehydesegmentabueide-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
maintainer-change maintainer-added AI (maintainer-change): Segment org package with large team; maintainer rotation is expected across 348 versions. ai
maintainer-change maintainer-removed AI (maintainer-change): Paired with maintainer-added in a large org; consistent with internal team changes, not takeover. ai
dependencies unvetted-dep:@segment/actions-core AI (dependencies): Internal @segment ecosystem dependency; stable pattern across all versions of this package. ai
dependencies unvetted-dep:@segment/browser-destination-runtime AI (dependencies): Internal @segment ecosystem dependency; stable pattern across all versions of this package. ai
npm-metadata no-description AI (npm-metadata): Monorepo-published Segment action package; missing description is a consistent pattern across the suite, not a malware signal. ai
bogus-package bogus-package AI (bogus-package): Internal Segment monorepo package; missing metadata is a consistent pattern across all versions, not a spam indicator. ai

Versions (showing 51 of 57)

View all versions
Version Deps Published
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
1.88.0 2 / 0
1.87.0 2 / 0
1.86.0 2 / 0
1.85.0 2 / 0
1.84.0 2 / 0
1.83.0 2 / 0
1.82.0 2 / 0
1.81.0 2 / 0
1.80.0 2 / 0
1.79.0 2 / 0
1.78.0 2 / 0
1.77.0 2 / 0
1.76.0 2 / 0
1.75.0 2 / 0
1.74.0 2 / 0
1.73.0 2 / 0
1.72.0 2 / 0
1.71.0 2 / 0
1.70.1 2 / 0
1.70.0 2 / 0
1.69.0 2 / 0
1.68.0 2 / 0
1.67.0 2 / 0
1.66.0 2 / 0
1.65.0 2 / 0
1.64.0 2 / 0
1.63.0 2 / 0
1.62.0 2 / 0
1.61.0 2 / 0
1.60.0 2 / 0
1.59.0 2 / 0
1.58.0 2 / 0
1.57.0 2 / 0
1.56.0 2 / 0
1.55.0 2 / 0
1.54.0 2 / 0
1.53.0 2 / 0
1.52.0 2 / 0
1.51.0 2 / 0
1.50.0 2 / 0
1.48.0 2 / 0
1.47.0 2 / 0

v1.82.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: forgetfulfellow → varadarajan-tw (on 2025-04-29, known maintainer) provenance

This version was published by a different npm account (varadarajan-tw) than the most recent previously approved version (forgetfulfellow) on 2025-04-29, 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.81.0

1 finding
LOW No provenance attestation provenance

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

v1.80.0

1 finding
LOW No provenance attestation provenance

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

v1.79.0

1 finding
LOW No provenance attestation provenance

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

v1.78.0

1 finding
LOW No provenance attestation provenance

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

v1.77.0

1 finding
LOW No provenance attestation provenance

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

v1.76.0

1 finding
LOW No provenance attestation provenance

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

v1.75.0

1 finding
LOW No provenance attestation provenance

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

v1.74.0

1 finding
LOW No provenance attestation provenance

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

v1.73.0

1 finding
LOW No provenance attestation provenance

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

v1.72.0

1 finding
LOW No provenance attestation provenance

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

v1.71.0

1 finding
LOW No provenance attestation provenance

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

v1.70.1

1 finding
LOW No provenance attestation provenance

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

v1.70.0

1 finding
LOW No provenance attestation provenance

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

v1.69.0

1 finding
LOW No provenance attestation provenance

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

v1.68.0

1 finding
LOW No provenance attestation provenance

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

v1.67.0

1 finding
LOW No provenance attestation provenance

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

v1.66.0

1 finding
LOW No provenance attestation provenance

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

v1.65.0

1 finding
LOW No provenance attestation provenance

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

v1.64.0

1 finding
LOW No provenance attestation provenance

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

v1.63.0

1 finding
LOW No provenance attestation provenance

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

v1.62.0

1 finding
LOW No provenance attestation provenance

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

v1.61.0

1 finding
LOW No provenance attestation provenance

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

v1.60.0

1 finding
LOW No provenance attestation provenance

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

v1.59.0

1 finding
LOW No provenance attestation provenance

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

v1.58.0

1 finding
LOW No provenance attestation provenance

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

v1.57.0

1 finding
LOW No provenance attestation provenance

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

v1.56.0

1 finding
LOW No provenance attestation provenance

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

v1.55.0

1 finding
LOW No provenance attestation provenance

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

v1.54.0

1 finding
LOW No provenance attestation provenance

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

v1.53.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.52.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: marinhero → forgetfulfellow (on 2024-07-09, known maintainer) provenance

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.51.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: joe.ayoub.segment → marinhero (on 2024-07-03, known maintainer) provenance

This version was published by a different npm account (marinhero) than the most recent previously approved version (joe.ayoub.segment) 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.50.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: varadarajan-tw → joe.ayoub.segment (on 2024-07-02, known maintainer) provenance

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.48.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: forgetfulfellow → varadarajan-tw (on 2024-07-02, known maintainer) provenance

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.47.0

1 finding
LOW No provenance attestation provenance

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