mixpanel — Greenflagged

A simple server-side API for mixpanel

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

mixpanel-devtdumitrescump_jthongrahul-mixpanelketanmixpanelsonya-park-mpmsiebert-mixpaneljakub.grzjaredcmixpanel

Keywords

mixpanelanalyticsapistats

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): Transition from individual (carlsverre) to Mixpanel team accounts (mixpanel-dev, tdumitrescu, etc.) under the official mixpanel GitHub org is a legitimate organizational handoff, not a hijack.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Original maintainer carlsverre removed as part of legitimate org transition; no evidence of compromise.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): https-proxy-agent is a well-known legitimate package for proxy support; benign addition to a server-side SDK.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher changed from carlsverre to the official mixpanel org account in 2015, matching the GitHub repo URL. Legitimate organizational transfer; stable for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): Mixpanel org account added as maintainer in 2015, consistent with official ownership transfer. No risk signal for this package.	ai	2026/04/24
dependencies	unvetted-dep:json-logic-js	AI (dependencies): json-logic-js is a legitimate, widely-used library; its inclusion in the Mixpanel SDK is consistent with feature-flag/cohort-targeting functionality.	ai	2026/04/24

Versions (showing 51 of 53)

View all versions

Version	Deps	Published
0.22.0	2 / 2	2026-05-04
0.21.0	2 / 8	2026-04-10
0.20.0	2 / 8	2026-01-13
0.19.1	1 / 6	2025-11-14
0.19.0	1 / 4	2025-11-12
0.18.1	1 / 3	2025-03-12
0.18.0	1 / 3	2023-09-12
0.17.0	1 / 3	2022-08-11
0.16.0	1 / 3	2022-06-02
0.15.0	1 / 3	2022-05-20
0.14.0	1 / 3	2021-10-29
0.13.0	1 / 3	2020-09-04
0.12.0	1 / 3	2020-09-01
0.11.0	1 / 3	2019-11-26
0.10.3	1 / 3	2019-10-09
0.10.2	1 / 3	2019-03-26
0.10.1	1 / 3	2018-12-04
0.10.0	1 / 3	2018-11-13
0.9.2	1 / 3	2018-05-22
0.9.1	1 / 3	2018-04-12
0.9.0	1 / 3	2018-02-09
0.8.0	1 / 3	2017-11-28
0.7.0	1 / 3	2017-04-07
0.6.0	0 / 2	2017-01-04
0.5.0	0 / 2	2016-09-15
0.4.1	0 / 2	2016-09-09
0.4.0	0 / 2	2016-02-09
0.3.2	0 / 2	2015-12-11
0.3.1	0 / 2	2015-08-12
0.3.0	0 / 2	2015-08-06
0.2.1	0 / 2	2015-05-12
0.2.0	0 / 2	2015-04-15
0.1.1	0 / 2	2015-03-27
0.1.0	0 / 2	2015-03-20
0.0.20	0 / 2	2014-05-12
0.0.19	0 / 2	2014-04-04
0.0.18	0 / 2	2013-08-23
0.0.17	0 / 2	2013-08-12
0.0.16	0 / 2	2013-06-30
0.0.15	0 / 2	2013-05-25
0.0.14	0 / 2	2013-03-28
0.0.13	0 / 2	2013-03-26
0.0.12	0 / 2	2013-01-24
0.0.11	0 / 2	2013-01-12
0.0.10	0 / 2	2012-11-26
0.0.9	0 / 2	2012-11-16
0.0.8	0 / 2	2012-10-24
0.0.7	0 / 2	2012-09-06
0.0.6	0 / 0	2012-08-31
0.0.5	0 / 0	2011-09-27
0.0.4	0 / 0	2011-06-08

v0.22.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: msiebert-mixpanel → tdumitrescu (on 2026-05-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.

v0.21.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.20.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.19.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.19.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.18.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.18.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (mp_jthong, jordanmnunez, mixpanel-dev, tdumitrescu, jbwyme, zihe.jia). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2023-09-12) provenance

This version was published by a different npm account than previous versions on 2023-09-12. 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.17.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (jordanmnunez, ryanhirsch, mixpanel-dev, tdumitrescu, jbwyme, zihe.jia). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2022-08-11) provenance

This version was published by a different npm account than previous versions on 2022-08-11. 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.16.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (jordanmnunez, ryanhirsch, mixpanel-dev, tdumitrescu, jbwyme, zihe.jia). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2022-06-02) provenance

This version was published by a different npm account than previous versions on 2022-06-02. 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.15.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (jordanmnunez, ryanhirsch, mixpanel-dev, tdumitrescu, jbwyme, zihe.jia). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2022-05-20) provenance

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

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (jordanmnunez, ryanhirsch, mixpanel-dev, tdumitrescu, jbwyme, zihe.jia). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2021-10-29) provenance

This version was published by a different npm account than previous versions on 2021-10-29. 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.13.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (apurcell, jbwyme, jordanmnunez, mixpanel-dev, nojvek, patedit, tdumitrescu). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2020-09-04) provenance

This version was published by a different npm account than previous versions on 2020-09-04. 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.12.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (apurcell, jbwyme, jordanmnunez, mixpanel-dev, nojvek, patedit, tdumitrescu). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2020-09-01) provenance

This version was published by a different npm account than previous versions on 2020-09-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.11.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (apurcell, jbwyme, jordanmnunez, mixpanel-dev, nojvek, patedit, tdumitrescu). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2019-11-26) provenance

This version was published by a different npm account than previous versions on 2019-11-26. 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.10.3

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (apurcell, jbwyme, jordanmnunez, mixpanel-dev, nojvek, patedit, tdumitrescu). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2019-10-09) provenance

This version was published by a different npm account than previous versions on 2019-10-09. 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.10.2

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (apurcell, evnp, jlack, jordanmnunez, mduan, mixpanel-dev, nojvek, tdumitrescu, zakj). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2019-03-26) provenance

This version was published by a different npm account than previous versions on 2019-03-26. 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.10.1

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (apurcell, evnp, jlack, jordanmnunez, mduan, mixpanel-dev, nojvek, tdumitrescu, zakj). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2018-12-04) provenance

This version was published by a different npm account than previous versions on 2018-12-04. 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.10.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (apurcell, evnp, jlack, jordanmnunez, mduan, mixpanel-dev, nojvek, tdumitrescu, zakj). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2018-11-13) provenance

This version was published by a different npm account than previous versions on 2018-11-13. 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.9.2

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (apurcell, evnp, mduan, mixpanel-dev, nojvek, tdumitrescu, zakj). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2018-05-22) provenance

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

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (apurcell, evnp, mduan, mixpanel-dev, nojvek, tdumitrescu, zakj). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2018-04-12) provenance

This version was published by a different npm account than previous versions on 2018-04-12. 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.9.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (apurcell, mixpanel-dev, nojvek, tdumitrescu, zakj). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2018-02-09) provenance

This version was published by a different npm account than previous versions on 2018-02-09. 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.8.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (apurcell, zakj, tdumitrescu, mixpanel-dev). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2017-11-28) provenance

This version was published by a different npm account than previous versions on 2017-11-28. 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.7.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (carlsverre) were replaced by new maintainers (jbwyme, mixpanel-dev, tdumitrescu, zakj). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: carlsverre → tdumitrescu (on 2017-04-07) provenance

This version was published by a different npm account than previous versions on 2017-04-07. 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

2 findings

HIGH Publisher changed: carlsverre → tdumitrescu (on 2017-01-04) provenance

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

2 findings

HIGH Publisher changed: carlsverre → tdumitrescu (on 2016-09-15) provenance

This version was published by a different npm account than previous versions on 2016-09-15. 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.4.1

2 findings

HIGH Publisher changed: carlsverre → tdumitrescu (on 2016-09-09) provenance

This version was published by a different npm account than previous versions on 2016-09-09. 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.4.0

2 findings

HIGH Publisher changed: carlsverre → mixpanel (on 2016-02-09) provenance

This version was published by a different npm account than previous versions on 2016-02-09. 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.3.2

2 findings

HIGH Publisher changed: carlsverre → mixpanel (on 2015-12-11) provenance

This version was published by a different npm account than previous versions on 2015-12-11. 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.3.1

2 findings

HIGH Publisher changed: carlsverre → mixpanel (on 2015-08-12) provenance

This version was published by a different npm account than previous versions on 2015-08-12. 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.3.0

2 findings

HIGH Publisher changed: carlsverre → mixpanel (on 2015-08-06) provenance

This version was published by a different npm account than previous versions on 2015-08-06. 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.2.1

2 findings

HIGH Publisher changed: carlsverre → mixpanel (on 2015-05-12) provenance

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

2 findings

HIGH Publisher changed: carlsverre → mixpanel (on 2015-04-15) provenance

This version was published by a different npm account than previous versions on 2015-04-15. 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.1.1

2 findings

HIGH Publisher changed: carlsverre → mixpanel (on 2015-03-27) provenance

This version was published by a different npm account than previous versions on 2015-03-27. 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.1.0

2 findings

HIGH Publisher changed: carlsverre → mixpanel (on 2015-03-20) provenance

This version was published by a different npm account than previous versions on 2015-03-20. 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.0.20

1 finding

LOW No provenance attestation provenance

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

v0.0.19

1 finding

LOW No provenance attestation provenance

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

v0.0.18

1 finding

LOW No provenance attestation provenance

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

v0.0.17

1 finding

LOW No provenance attestation provenance

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

v0.0.16

1 finding

LOW No provenance attestation provenance

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

v0.0.15

1 finding

LOW No provenance attestation provenance

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

v0.0.14

1 finding

LOW No provenance attestation provenance

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

v0.0.13

1 finding

LOW No provenance attestation provenance

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

v0.0.12

1 finding

LOW No provenance attestation provenance

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

v0.0.11

1 finding

LOW No provenance attestation provenance

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

v0.0.10

1 finding

LOW No provenance attestation provenance

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

v0.0.9

1 finding

LOW No provenance attestation provenance

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

v0.0.8

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

1 finding

LOW No provenance attestation provenance

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

v0.0.6

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

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

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.