mixpanel-browser — Greenflagged

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

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:eval-usage	AI (semgrep): eval in vendored requirejs example asset; stable FP for this package.	ai	2026/07/23
source-diff	obfuscated-file:dist/async-modules/mixpanel-recorder-bIS4LMGd.js	AI (source-diff): Minified rrweb recorder bundle, readable code; not obfuscation.	ai	2026/07/10
source-diff	obfuscated-file:dist/rrweb-bundled.js	AI (source-diff): Bundled rollup/swc dist output for rrweb session-replay, not obfuscation.	ai	2026/07/10
source-diff	obfuscated-file:dist/rrweb-compiled.js	AI (source-diff): Compiled rrweb bundle; readable helpers, stable build artifact.	ai	2026/07/10
source-diff	obfuscated-file:dist/mixpanel-with-recorder.js	AI (source-diff): Readable SWC/rollup bundle output, not obfuscation; recurs every build.	ai	2026/07/10
dependencies	unvetted-dep:@mixpanel/rrweb	AI (dependencies): First-party @mixpanel-scoped session-recording dep; legitimate.	ai	2026/07/10
source-diff	obfuscated-file:dist/async-modules/mixpanel-recorder-C0B3sEK2.js	AI (source-diff): Minified rrweb recorder bundle from rollup/swc; stable build artifact for this SDK.	ai	2026/07/10
source-diff	obfuscated-file:dist/async-modules/mixpanel-recorder-C3AW7mPl.js	AI (source-diff): Bundled rrweb session-recording code; minified dist output, not obfuscation.	ai	2026/05/30
source-diff	encoded-string-file:dist/mixpanel.cjs.js	AI (source-diff): CJS bundle with same inlined worker.	ai	2026/05/17
source-diff	encoded-string-file:dist/mixpanel.amd.js	AI (source-diff): AMD bundle with same inlined worker.	ai	2026/05/17
source-diff	encoded-string-file:dist/mixpanel.module.js	AI (source-diff): ESM bundle with same inlined worker.	ai	2026/05/17
source-diff	encoded-string-file:dist/mixpanel.umd.js	AI (source-diff): UMD bundle with same inlined worker.	ai	2026/05/17
source-diff	obfuscated-file:dist/async-modules/mixpanel-recorder-P6SEnnPV.js	AI (source-diff): Bundled/minified dist output for browser SDK; readable code visible in sample.	ai	2026/05/17
source-diff	encoded-string-file:dist/mixpanel-recorder.js	AI (source-diff): Base64-inlined web worker for rrweb canvas recording; standard browser SDK pattern.	ai	2026/05/17
source-diff	encoded-string-file:dist/mixpanel-recorder.min.js	AI (source-diff): Minified variant of same inlined worker code.	ai	2026/05/17
source-diff	encoded-string-file:dist/mixpanel-with-recorder.js	AI (source-diff): Same inlined worker in combined bundle.	ai	2026/05/17
source-diff	encoded-string-file:dist/mixpanel-with-recorder.min.js	AI (source-diff): Minified variant of same inlined worker code.	ai	2026/05/17
phantom-deps	phantom-dep:@types/json-logic-js	AI (phantom-deps): Type-only package; not imported at runtime, stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@mixpanel/rrweb-utils	AI (phantom-deps): Used transitively via rrweb; phantom-dep heuristic fires but this is a known indirect dependency.	ai	2026/04/29

Versions (showing 51 of 84)

View all versions

Version	Deps	Published
2.81.0	5 / 40	2026-07-09
2.80.0	5 / 40	2026-05-28
2.79.0	5 / 40	2026-05-14
2.78.0	5 / 40	2026-04-08
2.76.0	4 / 40	2026-03-18
2.75.0	3 / 40	2026-02-25
2.72.0	2 / 30	2025-11-14
2.71.1	1 / 30	2025-10-30
2.62.0	1 / 26	2025-03-26
2.61.2	1 / 26	2025-03-14
2.61.1	1 / 26	2025-03-11
2.61.0	1 / 26	2025-03-06
2.60.0	1 / 25	2025-02-04
2.59.0	1 / 25	2025-01-23
2.58.0	1 / 25	2024-12-18
2.57.1	1 / 25	2024-12-18
2.56.0	1 / 25	2024-11-08
2.55.1	1 / 25	2024-08-27
2.55.0	1 / 25	2024-08-02
2.54.1	1 / 25	2024-07-30
2.54.0	1 / 25	2024-07-23
2.53.0	1 / 26	2024-06-21
2.52.0	1 / 26	2024-06-07
2.51.0	1 / 26	2024-05-30
2.50.0	1 / 26	2024-04-29
2.49.0	0 / 24	2024-02-06
2.48.1	0 / 24	2023-11-14
2.48.0	0 / 24	2023-11-13
2.47.0	0 / 24	2023-04-28
2.46.0	0 / 24	2023-03-23
2.45.0	0 / 24	2022-02-18
2.43.0	0 / 24	2022-01-06
2.42.1	0 / 24	2021-12-22
2.42.0	0 / 24	2021-11-12
2.41.0	0 / 24	2021-01-28
2.40.1	0 / 24	2021-01-20
2.40.0	0 / 24	2020-12-02
2.39.0	0 / 24	2020-08-18
2.38.0	0 / 24	2020-06-12
2.37.0	0 / 24	2020-05-28
2.36.0	0 / 24	2020-05-07
2.35.0	0 / 21	2020-03-18
2.34.0	0 / 21	2020-01-28
2.33.1	0 / 21	2020-01-17
2.33.0	0 / 21	2020-01-16
2.32.0	0 / 21	2019-12-18
2.31.0	0 / 21	2019-11-20
2.30.1	0 / 21	2019-10-30
2.29.1	0 / 21	2019-08-22
2.29.0	0 / 21	2019-06-07
2.28.0	0 / 21	2019-05-14

v2.81.0

2 findings

HIGH New obfuscated file: dist/async-modules/mixpanel-recorder-C0B3sEK2.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.76.0

6 findings

HIGH Publisher changed: tdumitrescu → jakub.grz (on 2026-03-18) provenance

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

HIGH New obfuscated file: dist/async-modules/mixpanel-recorder-bIS4LMGd.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/mixpanel-with-recorder.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/rrweb-bundled.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/rrweb-compiled.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.75.0

4 findings

HIGH New obfuscated file: dist/mixpanel-with-recorder.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/rrweb-bundled.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/rrweb-compiled.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.72.0

5 findings

HIGH Publisher changed: tdumitrescu → jakub.grz (on 2025-11-14) provenance

This version was published by a different npm account than previous versions on 2025-11-14. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/mixpanel-with-recorder.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/rrweb-bundled.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/rrweb-compiled.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.71.1

4 findings

HIGH Publisher changed: tdumitrescu → jakub.grz (on 2025-10-30) provenance

This version was published by a different npm account than previous versions on 2025-10-30. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/mixpanel-with-recorder.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/rrweb-compiled.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.62.0

1 finding

LOW No provenance attestation provenance

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

v2.61.2

1 finding

LOW No provenance attestation provenance

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

v2.61.1

1 finding

LOW No provenance attestation provenance

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

v2.61.0

1 finding

LOW No provenance attestation provenance

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

v2.60.0

1 finding

LOW No provenance attestation provenance

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

v2.59.0

1 finding

LOW No provenance attestation provenance

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

v2.58.0

1 finding

LOW No provenance attestation provenance

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

v2.57.1

1 finding

LOW No provenance attestation provenance

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

v2.56.0

1 finding

LOW No provenance attestation provenance

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

v2.55.1

1 finding

LOW No provenance attestation provenance

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

v2.55.0

1 finding

LOW No provenance attestation provenance

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

v2.54.1

1 finding

LOW No provenance attestation provenance

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

v2.54.0

1 finding

LOW No provenance attestation provenance

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

v2.53.0

1 finding

LOW No provenance attestation provenance

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

v2.52.0

1 finding

LOW No provenance attestation provenance

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

v2.51.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.

v2.50.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.

v2.49.0

1 finding

LOW No provenance attestation provenance

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

v2.48.1

1 finding

LOW No provenance attestation provenance

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

v2.48.0

1 finding

LOW No provenance attestation provenance

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

v2.47.0

1 finding

LOW No provenance attestation provenance

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

v2.46.0

1 finding

LOW No provenance attestation provenance

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

v2.45.0

1 finding

LOW No provenance attestation provenance

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

v2.43.0

1 finding

LOW No provenance attestation provenance

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

v2.42.1

1 finding

LOW No provenance attestation provenance

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

v2.42.0

1 finding

LOW No provenance attestation provenance

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

v2.41.0

1 finding

LOW No provenance attestation provenance

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

v2.40.1

1 finding

LOW No provenance attestation provenance

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

v2.40.0

1 finding

LOW No provenance attestation provenance

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

v2.39.0

1 finding

LOW No provenance attestation provenance

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

v2.38.0

1 finding

LOW No provenance attestation provenance

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

v2.37.0

1 finding

LOW No provenance attestation provenance

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

v2.36.0

1 finding

LOW No provenance attestation provenance

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

v2.35.0

1 finding

LOW No provenance attestation provenance

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

v2.34.0

1 finding

LOW No provenance attestation provenance

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

v2.33.1

1 finding

LOW No provenance attestation provenance

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

v2.33.0

1 finding

LOW No provenance attestation provenance

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

v2.32.0

1 finding

LOW No provenance attestation provenance

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

v2.31.0

1 finding

LOW No provenance attestation provenance

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

v2.30.1

1 finding

LOW No provenance attestation provenance

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

v2.29.1

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: tdumitrescu → jordanmnunez (on 2019-08-22, known maintainer) provenance

This version was published by a different npm account (jordanmnunez) than the most recent previously approved version (tdumitrescu) on 2019-08-22, but jordanmnunez 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.

v2.29.0

1 finding

LOW No provenance attestation provenance

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

v2.28.0

1 finding

LOW No provenance attestation provenance

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