← Home

@posthog/plugin-utils

npm Repository Homepage
4
Versions
—
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-cdustinbyrnefrankposthogtom-posthogadamleithppeterkirkhamposthogjoshuasnyderhuguespouillot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA attestation; legitimate for PostHog org packages. ai
provenance missing-githead AI (provenance): Artifact of CI/CD publish environment; SLSA attestation provides stronger commit linkage. ai
semgrep semgrep:env-spread AI (semgrep): Intentional env forwarding in a CLI subprocess helper; stable pattern for this build-tool package. ai
bogus-package bogus-package AI (bogus-package): Scoped PostHog utility package; sparse README/keywords are cosmetic, not spam indicators. ai

Versions (showing 4 of 4)

Version Deps Published
1.1.1 1 / 5
1.1.0 1 / 5
1.0.1 1 / 5
0.1.0 1 / 5

v1.1.1

2 findings
HIGH env-spread: src/cli.ts:47 semgrep

Spreading entire process.env into an object — may capture all secrets 45 | */ 46 | export function buildCliEnv(config: ResolvedPluginConfig): NodeJS.ProcessEnv { > 47 | return { 48 | ...process.env, 49 | RUST_LOG: `posthog_cli=${config.logLevel}`,

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

2 findings
HIGH env-spread: src/cli.ts:47 semgrep

Spreading entire process.env into an object — may capture all secrets 45 | */ 46 | export function buildCliEnv(config: ResolvedPluginConfig): NodeJS.ProcessEnv { > 47 | return { 48 | ...process.env, 49 | RUST_LOG: `posthog_cli=${config.logLevel}`,

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

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

HIGH Publisher changed: manoelposthog → GitHub Actions (on 2026-04-01) provenance

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

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