@posthog/core
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): buildCliEnv() intentionally spreads process.env to forward the parent environment to a child process — standard CLI tool pattern, not exfiltration. Stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @posthog/core is a legitimate scoped package from the PostHog org with 65 versions and SLSA provenance. The Levenshtein match to 'cors' is purely coincidental and not a typosquat. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Missing description is a minor metadata gap for this well-established PostHog SDK package; not a malware indicator. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 1.29.14 | 1 / 4 | |
| 1.29.13 | 1 / 4 | |
| 1.29.12 | 1 / 4 | |
| 1.29.11 | 1 / 4 | |
| 1.29.10 | 1 / 4 | |
| 1.29.9 | 1 / 4 | |
| 1.29.8 | 1 / 4 | |
| 1.29.7 | 1 / 4 | |
| 1.29.6 | 1 / 4 | |
| 1.29.5 | 1 / 4 | |
| 1.29.4 | 1 / 4 | |
| 1.29.3 | 1 / 4 | |
| 1.29.2 | 1 / 4 | |
| 1.29.1 | 1 / 4 | |
| 1.29.0 | 1 / 4 | |
| 1.28.7 | 1 / 4 | |
| 1.28.6 | 1 / 4 | |
| 1.28.5 | 1 / 4 | |
| 1.28.4 | 1 / 4 | |
| 1.28.3 | 1 / 4 | |
| 1.28.2 | 1 / 4 | |
| 1.28.1 | 1 / 4 | |
| 1.28.0 | 1 / 4 | |
| 1.27.9 | 1 / 4 | |
| 1.27.8 | 1 / 4 | |
| 1.27.7 | 1 / 4 | |
| 1.27.6 | 1 / 4 | |
| 1.27.5 | 1 / 4 | |
| 1.27.4 | 1 / 4 | |
| 1.27.3 | 1 / 4 | |
| 1.27.2 | 1 / 4 | |
| 1.27.1 | 1 / 4 | |
| 1.27.0 | 0 / 4 | |
| 1.26.0 | 0 / 4 | |
| 1.25.3 | 0 / 4 | |
| 1.25.2 | 0 / 4 | |
| 1.25.1 | 0 / 4 | |
| 1.25.0 | 0 / 4 | |
| 1.24.6 | 0 / 4 | |
| 1.24.5 | 0 / 4 | |
| 1.24.4 | 1 / 5 | |
| 1.24.3 | 1 / 5 | |
| 1.24.2 | 1 / 5 | |
| 1.6.0 | 1 / 5 | |
| 1.5.7 | 1 / 5 | |
| 1.5.5 | 1 / 5 | |
| 1.5.4 | 1 / 5 | |
| 1.5.3 | 1 / 5 | |
| 1.5.2 | 1 / 4 | |
| 1.5.1 | 1 / 4 | |
| 1.5.0 | 0 / 3 |
v1.29.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.28.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.28.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.28.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.28.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.28.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.28.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.28.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.27.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.27.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.27.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.27.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.27.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.27.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.27.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.24.6
2 findingsPackage name '@posthog/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.24.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.24.4
2 findingsSpreading entire process.env into an object — may capture all secrets 41 | */ 42 | export function buildCliEnv(config: ResolvedPluginConfig): NodeJS.ProcessEnv { > 43 | return { 44 | ...process.env, 45 | RUST_LOG: `posthog_cli=${config.logLevel}`,
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.24.3
2 findingsSpreading entire process.env into an object — may capture all secrets 41 | */ 42 | export function buildCliEnv(config: ResolvedPluginConfig): NodeJS.ProcessEnv { > 43 | return { 44 | ...process.env, 45 | RUST_LOG: `posthog_cli=${config.logLevel}`,
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.24.2
2 findingsSpreading entire process.env into an object — may capture all secrets 41 | */ 42 | export function buildCliEnv(config: ResolvedPluginConfig): NodeJS.ProcessEnv { > 43 | return { 44 | ...process.env, 45 | RUST_LOG: `posthog_cli=${config.logLevel}`,
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
2 findingsThis version was published by a different npm account than previous versions on 2025-11-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.