mixpanel-react-native
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
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 GitHub Actions CI publish with SLSA attestation for official Mixpanel SDK; benign. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.5.0 | 4 / 11 | |
| 3.4.0 | 2 / 11 | |
| 3.3.0 | 2 / 11 | |
| 3.2.1 | 2 / 11 | |
| 3.2.0 | 2 / 11 | |
| 3.1.3 | 3 / 10 | |
| 3.0.9 | 2 / 10 | |
| 3.0.8 | 2 / 10 | |
| 3.0.7 | 2 / 10 | |
| 3.0.6 | 2 / 10 | |
| 3.0.5 | 2 / 10 | |
| 3.0.4 | 2 / 10 | |
| 3.0.3 | 2 / 10 |
v3.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jaredcmixpanel) than the most recent previously approved version (zihe.jia) on 2024-09-26, but jaredcmixpanel 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.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.