@sigmacomputing/react-embed-sdk

React JavaScript SDK to interact with Sigma Computing's Embed API

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jfrantyktruongdonhcdmaxseidenjosherichsigma-nathan-healeycaseyjsigmapat-haimbaughdmadelynyuchristinasivadheeraj2kevinphampearce-sigmajmhainpballaidinkarkhattarbelaklausazule-luxwtgjxjnathansigmahiranmayabenjixddbronnikanandnarayananeranatsigmadyoung_nccezimanyi-sigmajhu_sigmarjsigmakiel2rwoollenanjinlmansa_pabbarajuhuy-sigmapriyanshi13yi-sigmabrett_b_at_sigmamooneronicholaschandlerdiego-sigmarudysigmasharvilnsinanunanabhijit_sigmaaaron-sigmarounaksalim95robinpillenikhil_0929ncurraultreitmrmaximus-sigmaray.chen.sigmaasadakramhaoxu-sigmabohan_sigmaajvedatiwessigmamathughesbradleyxu02srivatsa-pjadefleishhackerpeternanderssonpurvilmehtaryankwongtifncgreyboshshiller8586liz425aileensigmamatei_the_sigmanautgary-sigmamatt-bierman-sigmaestellakaruniajschererererjishakamboolcawthornesmoircolindolesekulachiashnaryaangelafanbhavanapkotemontefernsvc-prd-cursor-npmcurtiscastroobashawswvoodasbrovmanvoidd7justineyuanacholmesmiguelsigmamjones-sigmafoxhatleojohn.yorkemjustian-sigmadanikalandsgarrettmackmrskdweidner-sigmatana-sigmaganesh24dapwuangel-sigmaangelafan1sigmaseppywenxuan5andyleokunalgadgilmaxzmorrisoneeshakurodedbronnik2wren.warburgjhannan13margotmerrillsvc-prd-yarn-npmgjerianjosephgoznpmsamirapateljoshb-sigmalylesigamdrewfb_sigmamcowger-at-sigmacolinmparkerseanking-sigmawilliamdolsenmarwanmattartao-sigmaeltong11mya-bridgeforthdouganceybenharrissigmamhogrefegeorgebonvaniesigmajonathan-cook-sigmavincenzoizzoyingchoumimevborejessicazlijsmn-houjleeeekojipereiratristinejeremietexsigmarazmpccismeandrew.tran07sahilsalim99louisshyersborissigmayinpengsigryan-sigmamicalazaleachristophermourimirandabillawalaevelynsjafiiyashsvisharmadhyeysigmaayman-sigmaadityasigmacomputingalyssatsunoalexisjohnsonnatboltonjcheung-sigmasvc-prod-winfra-npmalison.laibendyshen-sigmarohan322wangyvonnesvc-prod-winfra-gcpggezerjeffreychinrileycrahenvandit-sigmading-harrisonnischo22jialeijinmadisonchamberlainjlgjlgvarynyifeng-sigmaczhang_sigmacomputingaarshinovapengbeijmschumanasingh888gsharoyalinusmtbrandon.dixonpunnalshawn-lindelvalle84nsunkadtheoschao.sigmamorriswanshubhangi.srivastavalwangsfericbannatyne-sigmahannahsigmaarangasaifanfan-sigmajonathanzhang53daisywangphillipwhite99ekene-tcscrewtaylorscmessercguyatsigmamunteanuichalden-sigmaliamnormsimingualexbibasamhv0eansari-sigmaric-sigma-computingdavidmax-sigmaratnashivsankruthkota0929

Keywords

embedsdksigmareact

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Move to Sigma org service account (svc-prd-*); legitimate publish-infra migration.	ai	2026/07/11
maintainer-change	maintainer-removed	AI (maintainer-change): Paired with new maintainer add; normal team turnover for this org.	ai	2026/07/11
provenance	missing-githead	AI (provenance): No material source diff vs prior approved version; benign publish env variance.	ai	2026/07/11
maintainer-change	maintainer-added	AI (maintainer-change): Bulk addition of org teammates consistent with Sigma's internal team, not compromise.	ai	2026/07/11
source-diff	source-size-tripled	AI (source-diff): Build output growth from tsup bundling, no malicious payload evidence.	ai	2026/07/11

Versions (showing 23 of 23)

Version	Deps	Published
0.7.1	1 / 5	2026-05-01
0.7.0	1 / 5	2025-02-19
0.6.0	1 / 5	2025-01-28
0.5.2	1 / 5	2024-10-29
0.5.1	1 / 5	2024-10-28
0.5.0	1 / 5	2024-09-24
0.4.0	1 / 5	2024-09-18
0.3.3	1 / 5	2024-09-13
0.3.2	1 / 5	2024-08-06
0.3.1	1 / 5	2024-08-01
0.3.0	1 / 5	2024-08-01
0.2.11	1 / 5	2024-07-29
0.2.10	1 / 5	2024-07-12
0.2.8	1 / 4	2024-06-12
0.2.7	1 / 4	2024-06-12
0.2.6	1 / 4	2024-06-12
0.2.5	1 / 4	2024-06-11
0.2.4	1 / 4	2024-06-10
0.2.3	1 / 4	2024-06-06
0.2.2	1 / 4	2024-06-04
0.2.1	1 / 4	2024-05-23
0.2.0	1 / 3	2024-03-17
0.1.0	1 / 3	2024-03-17

v0.7.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: svc-prd-yarn-npm.

HIGH Publisher changed: pearce-sigma → svc-prd-yarn-npm (on 2026-05-01) provenance

This version was published by a different npm account than previous versions on 2026-05-01. 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.

v0.6.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pearce-sigma.

LOW No provenance attestation provenance

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

INFO Publisher changed: hiranmaya → pearce-sigma (on 2025-01-28, known maintainer) provenance

This version was published by a different npm account (pearce-sigma) than the most recent previously approved version (hiranmaya) on 2025-01-28, but pearce-sigma 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.

v0.5.2

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pearce-sigma.

LOW No provenance attestation provenance

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

INFO Publisher changed: hiranmaya → pearce-sigma (on 2024-10-29, known maintainer) provenance

This version was published by a different npm account (pearce-sigma) than the most recent previously approved version (hiranmaya) on 2024-10-29, but pearce-sigma 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.

v0.5.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hiranmaya.

LOW No provenance attestation provenance

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

v0.5.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pearce-sigma.

LOW No provenance attestation provenance

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

INFO Publisher changed: hiranmaya → pearce-sigma (on 2024-09-24, known maintainer) provenance

This version was published by a different npm account (pearce-sigma) than the most recent previously approved version (hiranmaya) on 2024-09-24, but pearce-sigma 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.

v0.4.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pearce-sigma.

LOW No provenance attestation provenance

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

INFO Publisher changed: hiranmaya → pearce-sigma (on 2024-09-18, known maintainer) provenance

This version was published by a different npm account (pearce-sigma) than the most recent previously approved version (hiranmaya) on 2024-09-18, but pearce-sigma 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.

v0.3.3

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pearce-sigma.

LOW No provenance attestation provenance

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

INFO Publisher changed: hiranmaya → pearce-sigma (on 2024-09-13, known maintainer) provenance

This version was published by a different npm account (pearce-sigma) than the most recent previously approved version (hiranmaya) on 2024-09-13, but pearce-sigma 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.

v0.3.2

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pearce-sigma.

LOW No provenance attestation provenance

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

INFO Publisher changed: hiranmaya → pearce-sigma (on 2024-08-06, known maintainer) provenance

This version was published by a different npm account (pearce-sigma) than the most recent previously approved version (hiranmaya) on 2024-08-06, but pearce-sigma 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.

v0.3.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pearce-sigma.

LOW No provenance attestation provenance

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

INFO Publisher changed: hiranmaya → pearce-sigma (on 2024-08-01, known maintainer) provenance

This version was published by a different npm account (pearce-sigma) than the most recent previously approved version (hiranmaya) on 2024-08-01, but pearce-sigma 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.

v0.3.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pearce-sigma.

LOW No provenance attestation provenance

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

INFO Publisher changed: hiranmaya → pearce-sigma (on 2024-08-01, known maintainer) provenance

This version was published by a different npm account (pearce-sigma) than the most recent previously approved version (hiranmaya) on 2024-08-01, but pearce-sigma 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.

v0.2.11

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pearce-sigma.

LOW No provenance attestation provenance

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

INFO Publisher changed: hiranmaya → pearce-sigma (on 2024-07-29, known maintainer) provenance

This version was published by a different npm account (pearce-sigma) than the most recent previously approved version (hiranmaya) on 2024-07-29, but pearce-sigma 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.

v0.2.10

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hiranmaya.

LOW No provenance attestation provenance

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

v0.2.8

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hiranmaya.

LOW No provenance attestation provenance

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

v0.2.7

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hiranmaya.

LOW No provenance attestation provenance

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

v0.2.6

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hiranmaya.

LOW No provenance attestation provenance

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

v0.2.5

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hiranmaya.

LOW No provenance attestation provenance

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

v0.2.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hiranmaya.

LOW No provenance attestation provenance

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

v0.2.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hiranmaya.

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

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.

v0.2.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.

v0.1.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.