← Home

@segment/analytics-browser-actions-upollo

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

Maintainers

harksinghfhalim-segmentcfreeldelossantoshjoonpmceline-segmentpmcanseco-segmentmasiraamillet89cholt002av-segmentaghotikarvikrant-segmentlarryatsegmentscruwys1kyliepedersenjinaparkcdignam-segmentsegmentiojrupasinghelateefatrajulvaderayash-twiliosowjanyasegmentebru.odokryanligonlpediredlabrookstaylorjrnithan-twiliodean-huynhwdbettsn2parkojayakrishnannairrhall-twiliokarimkeshwanityson_segmentjgabe13bgamwellpoojasegmentmaryam.sharifwally.tgsalolivareserikdwchenxiangzhangjusteenmericssonprayansh-segmenttjeremylarkinbsneeddanieljackinssegment-sethsayan-das-injames9446priscilla.giattinlsundrew-thompsonsegment-jsinghmcoulibaliandrius-segmentvalerieernstnithin-bennyainatancincoskondamuriclintz.segreplateroslenin-twiliocsayusoseanhan-segmentnevermore2022gilomermarcelopveric.rognerkdharaiyajon.anderson-at-segment.comstacy.songrexatsegmentnickaguilarbradenbeckerreneewangdan.laskysam.tapialnambavikramkumar19mpriyad25jeremy.parkersmidgesnageshgolemsudojatinpmaidsethsegmentjair.avilesmanali-bhosaleelmoselyeechtoombspeterdemartinivincen7tranmayur-pitalelfdelossantosemmy.byrnefelttripsa-jsooterlluque-twiliokevinburkesegmentafsha-nazim-segsong4youdavid.anusontarangkul.segmentjyim008michaelghsegacharles14aishikawakitwjosiahtanya.gupta.segmentsindhusegmentprabhnoor1997chihchun-twiliopmiller-twiliovbatanovsimpixelatedmcullenmeyerneeharikakondipatieric-hydearunlalam-segmentmschaszbergershuvrajit9904abhinavsurekavaradarajan-twimmanojblangtwiliojsh-wusethnutetwiliorrivera-segmentsegment-adminbgillantcgilbertmckern_segmentmaneesh.dharma29joetessydominicbarnesmugelstadjalexy12lerahulrampmuninwhaider_twilioariel.silvestrishraddha-twiliomichelrbrandon.scott-segmentjfehrman.segmentprayansh-twiliodangmai-segmentaaronklishbrianhumphreystwiliormukundanashwitha.bgryanrouleau-segmentfunlutdibaccofauzy.yynlubchencoarubiochavezphillip.thomasjkusa_segmentrollcodemeg1000nainy.agrawalseg-rustybaileyjbandi-twiliosaisagarkappaganthulaforgetfulfellowdbaik-twilio-segmentpooja.patiljoe.ayoub.segmenthmohanram_segbrian.aguirreenyi.asonyefarhan0581tbrennanjparag.pandaharsh.vardhansshaikh_segmentxinghao.huangshupadhyayjohn.lee1100kx-segmentsegment_fandazu70sai-patanjaliemilyjiay.yuea_segmentyli119pooyajsungju.jinconniechenbharath.boregowdaigracheva-twiliobenattwiliomarinheroankit.gupta.unthinkabledobrin.ganevalfrimpongbrandonheyer-segmentalecjacobs-segmentcjo2yashnit-segmentdltnbrks-segmentachandrashekaranhimanshuphpraguptatw-dgarciaalayvoraaparna.singhalynguyentimmyzsearcylweimersegmentanton-vylushchakazhaotwiliorokatyalkjoerresmsarafvikakumaraditi.raveeshchenchensegmentcomsanket.mishraodoren_segmentjxin_twiliorcheedhallajbasiglio-segmentviveksainaneesegmentpriyanshispreetypakash.gautam07nanotimmyshkprsrivig21ssunejabala.singareddymoyara2arjunbhandageakodankiryrodhilton_twiliocdelaomartinezgbatraspenceratticksegmentseansundareswar.jayakumarvaibhavnandabannapplesrishti-nemagsolis_segmentitsarijitraybhavanki-segmentnanette.ranesamigandhiguthriesegmentmiguelpdiaz8mansarisandhya16hema-bahirwani-segmentbnakkinapraveenugiriighorelanemery-segmentwlumsegmentnat-gridneedcaffeinekbhargavaram-sgirfan.ali.segmentharsh-joshi99ed-twilion-npmaubreysinelight-bringer-blrsethgrid_segmentjibrangseg-leonelsanchessmccoy-twiliodevthaleandwivedipoojapatilseggaprabhumonusegmentehydesegmentpsandquistdcp-twilioagerbas-segmentamitsinglaatsegjoy-twiliosprajapati89amanda.majinesh-twilioardev_npmnikumar-segment-newsarthak-twilionupur-twiliovkundnaniprathoresegmentmmilhansegshubhkrishnakvivekabhirampugupta3ajsinghsegkkolhe-twilioprassinghseg-ajasinghmdkhan-twmahit

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Segment monorepo packages consistently lack provenance; stable false positive for this package family. ai
bogus-package bogus-package AI (bogus-package): Internal scoped @segment package; missing metadata is a known pattern across this monorepo, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Consistent with other @segment scoped packages; not a malice signal here. ai

Versions (showing 49 of 49)

Version Deps Published
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
1.46.0 2 / 0
1.44.0 2 / 0
1.43.0 2 / 0
1.42.0 2 / 0
1.41.0 2 / 0
1.40.0 2 / 0

v1.82.0

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

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

v1.80.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.79.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.78.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.77.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.76.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.75.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.74.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.73.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.72.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.71.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.70.1

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.70.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.69.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.68.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.67.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.66.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.65.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.64.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.63.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.62.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.61.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.60.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.59.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.58.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.57.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.56.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.55.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.54.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.53.0

2 findings
INFO No provenance attestation provenance

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

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

This version was published by a different npm account (forgetfulfellow) than the most recent previously approved version (marinhero) on 2024-07-23, 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.52.0

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

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

INFO Publisher changed: varadarajan-tw → 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 (varadarajan-tw) 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
INFO No provenance attestation provenance

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

INFO Publisher changed: forgetfulfellow → 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 (forgetfulfellow) 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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

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

v1.46.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.44.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.43.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.42.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.41.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.40.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.