← Home

@posthog/nextjs-config

npm Repository Homepage

NextJS configuration helper for Posthog 🦔

31
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

watilotwixesfuziontechmariusandraben-posthogtimglrafael_posthogfraserhoppermanoelposthogrobbie-cdustinbyrnefeliperalmeidalucasheriquesfrankposthogtom-posthogadamleithpcat-phsarahxsanderspeterkirkhamposthogioannisjjoshuasnyderhuguespouillot

Keywords

posthognextjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): New maintainers are within PostHog org (frankposthog, tom-posthog); normal team changes. ai
maintainer-change maintainer-removed AI (maintainer-change): david-posthog removed; normal PostHog team turnover. ai
semgrep semgrep:child-process-spawn AI (semgrep): Spawns declared dep posthog-cli; stable pattern for this package. ai
semgrep semgrep:child-process-import AI (semgrep): CLI wrapper package; spawning posthog-cli is its core purpose. ai
semgrep semgrep:env-spread AI (semgrep): Passes process.env to spawned posthog-cli child process; standard subprocess pattern. ai
provenance publisher-changed AI (provenance): Legitimate migration from personal npm account to GitHub Actions CI/CD publishing with SLSA provenance. ai
phantom-deps phantom-dep:@posthog/cli AI (phantom-deps): @posthog/cli is a same-org tooling dep; phantom-dep false positive stable for this package. ai

Versions (showing 31 of 133)

Version Deps Published
1.7.1 4 / 9
1.7.0 4 / 9
1.6.4 4 / 9
1.6.3 4 / 9
1.6.2 4 / 9
1.6.1 4 / 9
1.6.0 4 / 9
1.5.2 4 / 9
1.5.0 4 / 9
1.4.2 3 / 9
1.4.1 3 / 9
1.4.0 3 / 8
1.3.10 3 / 8
1.3.9 3 / 8
1.3.8 3 / 8
1.3.7 3 / 8
1.3.6 3 / 8
1.3.5 3 / 8
1.3.4 3 / 8
1.3.3 3 / 8
1.3.2 3 / 8
1.3.1 2 / 8
1.3.0 2 / 8
1.2.1 2 / 8
1.2.0 2 / 8
1.1.2 1 / 7
1.1.1 1 / 7
1.1.0 1 / 5
1.0.2 1 / 2
1.0.1 1 / 2
1.0.0 1 / 2

v1.7.1

2 findings
HIGH Publisher changed: timgl → GitHub Actions (on 2025-12-15) provenance

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.7.0

2 findings
HIGH Publisher changed: timgl → GitHub Actions (on 2025-12-13) provenance

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.4

2 findings
HIGH Publisher changed: timgl → GitHub Actions (on 2025-12-04) provenance

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.3

2 findings
HIGH Publisher changed: timgl → GitHub Actions (on 2025-12-03) provenance

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.2

2 findings
HIGH Publisher changed: timgl → GitHub Actions (on 2025-12-01) provenance

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.1

2 findings
HIGH Publisher changed: timgl → GitHub Actions (on 2025-11-28) provenance

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

INFO Has SLSA provenance attestation provenance

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 finding
LOW No provenance attestation provenance

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

v1.5.2

2 findings
HIGH Publisher changed: timgl → huguespouillot (on 2025-11-24) provenance

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

LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.2

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.10

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.

v1.3.9

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.

v1.3.8

1 finding
LOW No provenance attestation provenance

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

v1.3.7

1 finding
LOW No provenance attestation provenance

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

v1.3.6

1 finding
LOW No provenance attestation provenance

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

v1.3.5

1 finding
LOW No provenance attestation provenance

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

v1.3.4

1 finding
LOW No provenance attestation provenance

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

v1.3.3

1 finding
LOW No provenance attestation provenance

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

v1.3.2

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

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

v1.0.2

3 findings
HIGH env-spread: lib/index.cjs:104 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/PostHog/posthog-js-lite/blob/09266715d8ca1d4089761d7045cd8963b77f1cc4/lib/index.cjs#L104 102 | } 103 | // Add env variables > 104 | const envVars = { 105 | ...process.env, 106 | POSTHOG_CLI_TOKEN: this.posthogOptions.personalApiKey,

HIGH env-spread: lib/index.mjs:95 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/PostHog/posthog-js-lite/blob/09266715d8ca1d4089761d7045cd8963b77f1cc4/lib/index.mjs#L95 93 | } 94 | // Add env variables > 95 | const envVars = { 96 | ...process.env, 97 | POSTHOG_CLI_TOKEN: this.posthogOptions.personalApiKey,

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.

v1.0.1

3 findings
HIGH env-spread: lib/index.cjs:64 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/PostHog/posthog-js-lite/blob/a164b8b0d2d1bd109db3ea3cf57d0801517bcc2f/lib/index.cjs#L64 62 | } 63 | // Add env variables > 64 | const envVars = { 65 | ...process.env, 66 | POSTHOG_CLI_TOKEN: this.posthogOptions.personalApiKey,

HIGH env-spread: lib/index.mjs:56 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/PostHog/posthog-js-lite/blob/a164b8b0d2d1bd109db3ea3cf57d0801517bcc2f/lib/index.mjs#L56 54 | } 55 | // Add env variables > 56 | const envVars = { 57 | ...process.env, 58 | POSTHOG_CLI_TOKEN: this.posthogOptions.personalApiKey,

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.

v1.0.0

3 findings
HIGH env-spread: lib/index.cjs:64 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/PostHog/posthog-js-lite/blob/ad2d114856417bce8052933091f9735d1e1a94a8/lib/index.cjs#L64 62 | } 63 | // Add env variables > 64 | const envVars = { 65 | ...process.env, 66 | POSTHOG_CLI_TOKEN: this.posthogOptions.personalApiKey,

HIGH env-spread: lib/index.mjs:56 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/PostHog/posthog-js-lite/blob/ad2d114856417bce8052933091f9735d1e1a94a8/lib/index.mjs#L56 54 | } 55 | // Add env variables > 56 | const envVars = { 57 | ...process.env, 58 | POSTHOG_CLI_TOKEN: this.posthogOptions.personalApiKey,

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.