Remove unused posthog-node dependency - #501
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 947b130 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
posthog-node was declared in packages/core but never imported anywhere. The only PostHog usage (packages/cli analytics provider) talks to the HTTP API via node-fetch directly, and the telemetry that originally motivated the dep was removed in #489. Dropping it eliminates the transitive axios@0.27 (and rusha) supply chain entirely, which also resolves the axios XSRF-TOKEN advisory (CVE-2023-45857) that #497 aimed to address by bumping the package.
psugihara
force-pushed
the
remove-unused-posthog-node
branch
from
July 8, 2026 02:48
82da198 to
947b130
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Alternative to #497. That PR bumps
posthog-node2.x → 4.x to pull in a patchedaxios(CVE-2023-45857, XSRF-TOKEN leak).What this does instead
posthog-nodeis never imported anywhere in the repo:packages/cli/src/util/analytics/providers/Posthog.ts— talks to the PostHog HTTP API vianode-fetchdirectly, not the SDK.So rather than upgrade a dead dependency, this removes it. Regenerating the lockfile drops
posthog-node, its transitiveaxios@0.27.2+follow-redirects@1.15.3, andrushaentirely — eliminating the vulnerable axios supply chain completely instead of trading 0.27 for 1.7.Notes
yarn buildpasses clean.